[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD20HMJC8E93WTGYWNNG9Y":3,"skill-same:01M6AD20HMJC8E93WTGYWNNG9Y":95},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M6AD20HMJC8E93WTGYWNNG9Y","team-capacity-planning",null,"Plan resource capacity — workload analysis and utilization forecasting. Use when heading into quarterly planning, the team feels overallocated and you need the numbers, deciding whether to hire or deprioritize, or stress-testing whether upcoming projects fit the people you have.","Significant-Gravitas\u002Fskills-catalog","Significant-Gravitas","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F130738209?v=4","01M6AC83EPDGBFN19MWYRREJD0","AutoGPT","01M6ACEY98TKHDWJH0B93PHNMG",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fteam-capacity-planning\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fteam-capacity-planning\u002FSKILL.md",[],[20,21,22,23,24,25,26,27],"capacity","planning","team capacity planning","testing","github","workload","https","plugins","2026-11-10 10:12:30",false,"---\nname: team-capacity-planning\ndescription: Plan resource capacity — workload analysis and utilization forecasting. Use when heading into quarterly planning, the team feels overallocated and you need the numbers, deciding whether to hire or deprioritize, or stress-testing whether upcoming projects fit the people you have.\nargument-hint: \u003Cteam or project scope>\nlicense: Apache-2.0\nmetadata:\n  author: Anthropic\n  source: anthropics\u002Fknowledge-work-plugins\u002Foperations\u002Fskills\u002Fcapacity-plan\n  source_url: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002F8f8779a1681ea2f8dc697a6b3063d5e3e7f7460c\u002Foperations\u002Fskills\u002Fcapacity-plan\u002FSKILL.md\n  upstream-commit: 8f8779a1681ea2f8dc697a6b3063d5e3e7f7460c\n  original-name: capacity-plan\n  packaged-by: AutoGPT\n  packaged-on: '2026-09-25'\n---\n\n> Packaging adaptation by AutoGPT, 2026-09-25. Original authorship and licence are retained. Changes are limited to the recorded name, metadata and local references; see ATTRIBUTION.md in this package.\n\n\n# \u002Fcapacity-plan\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](references\u002FCONNECTORS.md).\n\nAnalyze team capacity and plan resource allocation.\n\n## Usage\n\n```\n\u002Fcapacity-plan $ARGUMENTS\n```\n\n## What I Need From You\n\n- **Team size and roles**: Who do you have?\n- **Current workload**: What are they working on? (Upload from project tracker or describe)\n- **Upcoming work**: What's coming next quarter?\n- **Constraints**: Budget, hiring timeline, skill requirements\n\n## Planning Dimensions\n\n### People\n- Available headcount and skills\n- Current allocation and utilization\n- Planned hires and timeline\n- Contractor and vendor capacity\n\n### Budget\n- Operating budget by category\n- Project-specific budgets\n- Variance tracking\n- Forecast vs. actual\n\n### Time\n- Project timelines and dependencies\n- Critical path analysis\n- Buffer and contingency planning\n- Deadline management\n\n## Utilization Targets\n\n| Role Type | Target Utilization | Notes |\n|-----------|-------------------|-------|\n| IC \u002F Specialist | 75-80% | Leave room for reactive work and growth |\n| Manager | 60-70% | Management overhead, meetings, 1:1s |\n| On-call \u002F Support | 50-60% | Interrupt-driven work is unpredictable |\n\n## Common Pitfalls\n\n- Planning to 100% utilization (no buffer for surprises)\n- Ignoring meeting load and context-switching costs\n- Not accounting for vacation, holidays, and sick time\n- Treating all hours as equal (creative work ≠ admin work)\n\n## Output\n\n```markdown\n## Capacity Plan: [Team\u002FProject]\n**Period:** [Date range] | **Team Size:** [X]\n\n### Current Utilization\n| Person\u002FRole | Capacity | Allocated | Available | Utilization |\n|-------------|----------|-----------|-----------|-------------|\n| [Name\u002FRole] | [hrs\u002Fwk] | [hrs\u002Fwk] | [hrs\u002Fwk] | [X]% |\n\n### Capacity Summary\n- **Total capacity**: [X] hours\u002Fweek\n- **Currently allocated**: [X] hours\u002Fweek ([X]%)\n- **Available**: [X] hours\u002Fweek ([X]%)\n- **Overallocated**: [X people above 100%]\n\n### Upcoming Demand\n| Project\u002FInitiative | Start | End | Resources Needed | Gap |\n|--------------------|-------|-----|-----------------|-----|\n| [Project] | [Date] | [Date] | [X FTEs] | [Covered\u002FGap] |\n\n### Bottlenecks\n- [Skill or role that's oversubscribed]\n- [Time period with a crunch]\n\n### Recommendations\n1. [Hire \u002F Contract \u002F Reprioritize \u002F Delay]\n2. [Specific action]\n\n### Scenarios\n| Scenario | Outcome |\n|----------|---------|\n| Do nothing | [What happens] |\n| Hire [X] | [What changes] |\n| Deprioritize [Y] | [What frees up] |\n```\n\n## If Connectors Available\n\nIf **~~project tracker** is connected:\n- Pull current workload and ticket assignments automatically\n- Show upcoming sprint or quarter commitments per person\n\nIf **~~calendar** is connected:\n- Factor in PTO, holidays, and recurring meeting load\n- Calculate actual available hours per person\n\n## Tips\n\n1. **Include all work** — BAU, projects, support, meetings. People aren't 100% available for project work.\n2. **Plan for buffer** — Target 80% utilization. 100% means no room for surprises.\n3. **Update regularly** — Capacity plans go stale fast. Review monthly.\n","> Packaging adaptation by AutoGPT, 2026-09-25. Original authorship and licence are retained. Changes are limited to the recorded name, metadata and local references; see ATTRIBUTION.md in this package.\n\n\n# \u002Fcapacity-plan\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](references\u002FCONNECTORS.md).\n\nAnalyze team capacity and plan resource allocation.\n\n## Usage\n\n```\n\u002Fcapacity-plan $ARGUMENTS\n```\n\n## What I Need From You\n\n- **Team size and roles**: Who do you have?\n- **Current workload**: What are they working on? (Upload from project tracker or describe)\n- **Upcoming work**: What's coming next quarter?\n- **Constraints**: Budget, hiring timeline, skill requirements\n\n## Planning Dimensions\n\n### People\n- Available headcount and skills\n- Current allocation and utilization\n- Planned hires and timeline\n- Contractor and vendor capacity\n\n### Budget\n- Operating budget by category\n- Project-specific budgets\n- Variance tracking\n- Forecast vs. actual\n\n### Time\n- Project timelines and dependencies\n- Critical path analysis\n- Buffer and contingency planning\n- Deadline management\n\n## Utilization Targets\n\n| Role Type | Target Utilization | Notes |\n|-----------|-------------------|-------|\n| IC \u002F Specialist | 75-80% | Leave room for reactive work and growth |\n| Manager | 60-70% | Management overhead, meetings, 1:1s |\n| On-call \u002F Support | 50-60% | Interrupt-driven work is unpredictable |\n\n## Common Pitfalls\n\n- Planning to 100% utilization (no buffer for surprises)\n- Ignoring meeting load and context-switching costs\n- Not accounting for vacation, holidays, and sick time\n- Treating all hours as equal (creative work ≠ admin work)\n\n## Output\n\n```markdown\n## Capacity Plan: [Team\u002FProject]\n**Period:** [Date range] | **Team Size:** [X]\n\n### Current Utilization\n| Person\u002FRole | Capacity | Allocated | Available | Utilization |\n|-------------|----------|-----------|-----------|-------------|\n| [Name\u002FRole] | [hrs\u002Fwk] | [hrs\u002Fwk] | [hrs\u002Fwk] | [X]% |\n\n### Capacity Summary\n- **Total capacity**: [X] hours\u002Fweek\n- **Currently allocated**: [X] hours\u002Fweek ([X]%)\n- **Available**: [X] hours\u002Fweek ([X]%)\n- **Overallocated**: [X people above 100%]\n\n### Upcoming Demand\n| Project\u002FInitiative | Start | End | Resources Needed | Gap |\n|--------------------|-------|-----|-----------------|-----|\n| [Project] | [Date] | [Date] | [X FTEs] | [Covered\u002FGap] |\n\n### Bottlenecks\n- [Skill or role that's oversubscribed]\n- [Time period with a crunch]\n\n### Recommendations\n1. [Hire \u002F Contract \u002F Reprioritize \u002F Delay]\n2. [Specific action]\n\n### Scenarios\n| Scenario | Outcome |\n|----------|---------|\n| Do nothing | [What happens] |\n| Hire [X] | [What changes] |\n| Deprioritize [Y] | [What frees up] |\n```\n\n## If Connectors Available\n\nIf **~~project tracker** is connected:\n- Pull current workload and ticket assignments automatically\n- Show upcoming sprint or quarter commitments per person\n\nIf **~~calendar** is connected:\n- Factor in PTO, holidays, and recurring meeting load\n- Calculate actual available hours per person\n\n## Tips\n\n1. **Include all work** — BAU, projects, support, meetings. People aren't 100% available for project work.\n2. **Plan for buffer** — Target 80% utilization. 100% means no room for surprises.\n3. **Update regularly** — Capacity plans go stale fast. Review monthly.\n",{"name":5,"license":15,"metadata":33,"description":7,"argument-hint":40},{"author":34,"source":35,"source_url":36,"packaged-by":12,"packaged-on":37,"original-name":38,"upstream-commit":39},"Anthropic","anthropics\u002Fknowledge-work-plugins\u002Foperations\u002Fskills\u002Fcapacity-plan","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002F8f8779a1681ea2f8dc697a6b3063d5e3e7f7460c\u002Foperations\u002Fskills\u002Fcapacity-plan\u002FSKILL.md","2026-09-25","capacity-plan","8f8779a1681ea2f8dc697a6b3063d5e3e7f7460c","\u003Cteam or project scope>","main","7ed3b73314d5186120e8d4006febfd7e1c92cf08","skills\u002Fteam-capacity-planning",0,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas","agpt.co","2026-11-10 22:38:50",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Significant-Gravitas\u002Fskills-catalog --skill team-capacity-planning",{"tool":55,"command":56},"bunx","bunx skills add Significant-Gravitas\u002Fskills-catalog --skill team-capacity-planning",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Significant-Gravitas\u002Fskills-catalog --skill team-capacity-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fteam-capacity-planning\u002FSKILL.md",true,[63,69,73,77,81,85,89],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"ATTRIBUTION.md","REFERENCE","参考文档",1665,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fteam-capacity-planning\u002FATTRIBUTION.md",{"path":70,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":16},"LICENSE","许可证",11358,{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Falgorithm-patterns.md",6214,"https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fperformance-optimization\u002Freferences\u002Falgorithm-patterns.md",{"path":78,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002FCONNECTORS.md",1566,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fteam-capacity-planning\u002Freferences\u002FCONNECTORS.md",{"path":82,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fpython-patterns.md",7021,"https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fperformance-optimization\u002Freferences\u002Fpython-patterns.md",{"path":86,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Ftypescript-patterns.md",10003,"https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fperformance-optimization\u002Freferences\u002Ftypescript-patterns.md",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fprofile-python.sh","SCRIPT","脚本",5139,"https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fperformance-optimization\u002Fscripts\u002Fprofile-python.sh",[96,107,135,145,159,177],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":28},"01M6AD3S89TGF74S7MK4K5CGC7","workplace-memory-management","Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory\u002F directory for the full knowledge base.","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fworkplace-memory-management\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fworkplace-memory-management\u002FSKILL.md",[],[104,105,27,26,24,106],"workplace memory management","memory","directory",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":128,"publishedAt":28},"01M6AD3F5X5DYW1BABD49BQKP8","website-seo-audit","Audit a website, investigate its real search opportunities, and deliver a short data-backed report on the few changes most likely to grow organic traffic that converts.","MIT","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-seo-audit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-seo-audit\u002FSKILL.md",[115,120,123],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":121,"categoryName":122,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[129,130,131,24,27,26,132,133,134],"website seo audit","audit","website","search","report","plugin",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":28},"01M6AD32RYMK03P50DM0T184NJ","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[143,144,26,24],"verification before completion","verification",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":149,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":28},"01M6AD2WSQG7BGPXA7XP4DFZX8","vendor-evaluation","Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-evaluation\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-evaluation\u002FSKILL.md",[],[153,154,27,26,155,156,157,24,158],"vendor evaluation","negotiation","assessment","risk assessment","cost analysis","review",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":163,"sourceHtmlUrl":164,"categories":165,"keywords":172,"publishedAt":28},"01M6AD2RBT6004C07RZRDSTA52","vendor-contract-status","Check the status of existing agreements with a vendor across all connected systems — CLM, CRM, email, and document storage — with gap analysis and upcoming deadlines. Use when onboarding or renewing a vendor, when you need a consolidated view of what's signed and what's missing (MSA, DPA, SOW), or when checking for approaching expirations and surviving obligations.","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-contract-status\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-contract-status\u002FSKILL.md",[166,169],{"categoryNo":167,"categoryName":168,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":170,"categoryName":171,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000037","律师与法务",[173,174,24,175,27,176,26],"vendor contract status","status","storage","onboarding",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":181,"sourceHtmlUrl":182,"categories":183,"keywords":187,"publishedAt":28},"01M6AD2KPNXN5CNS3CA4FRWT97","user-cohort-analysis","Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fuser-cohort-analysis\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fuser-cohort-analysis\u002FSKILL.md",[184],{"categoryNo":185,"categoryName":186,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000033","数据分析师",[188,189,26,24],"user cohort analysis","analytics"]