[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD2RBT6004C07RZRDSTA52":3,"skill-same:01M6AD2RBT6004C07RZRDSTA52":86},{"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":29,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6AD2RBT6004C07RZRDSTA52","vendor-contract-status",null,"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.","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\u002Fvendor-contract-status\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-contract-status\u002FSKILL.md",[19,24],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":27,"taxonomyTypeDesc":28},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[30,31,32,33,34,35,36],"status","vendor contract status","github","storage","onboarding","https","plugins","2026-11-10 10:12:30",false,"---\nname: vendor-contract-status\ndescription: 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.\nargument-hint: '[vendor name]'\nlicense: Apache-2.0\nmetadata:\n  author: Anthropic and upstream contributors\n  source: anthropics\u002Fknowledge-work-plugins\u002Flegal\u002Fskills\u002Fvendor-check\n  source_url: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002F1c7187c4fc17feefa6cde39517f12dae1249e6c4\u002Flegal\u002Fskills\u002Fvendor-check\u002FSKILL.md\n  upstream-commit: 1c7187c4fc17feefa6cde39517f12dae1249e6c4\n  original-name: vendor-check\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 file references; see ATTRIBUTION.md in this skill package.\n\n\n# \u002Fvendor-check -- Vendor Agreement Status\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](references\u002FCONNECTORS.md).\n\nCheck the status of existing agreements with a vendor across all connected systems. Provides a consolidated view of the legal relationship.\n\n**Important**: This command assists with legal workflows but does not provide legal advice. Agreement status reports should be verified against original documents by qualified legal professionals.\n\n## Invocation\n\n```\n\u002Fvendor-check [vendor name]\n```\n\nIf no vendor name is provided, prompt the user to specify which vendor to check.\n\n## Workflow\n\n### Step 1: Identify the Vendor\n\nAccept the vendor name from the user. Handle common variations:\n- Full legal name vs. trade name (e.g., \"Alphabet Inc.\" vs. \"Google\")\n- Abbreviations (e.g., \"AWS\" vs. \"Amazon Web Services\")\n- Parent\u002Fsubsidiary relationships\n\nAsk the user to clarify if the vendor name is ambiguous.\n\n### Step 2: Search Connected Systems\n\nSearch for the vendor across all available connected systems, in priority order:\n\n#### CLM (Contract Lifecycle Management) -- If Connected\nSearch for all contracts involving the vendor:\n- Active agreements\n- Expired agreements (last 3 years)\n- Agreements in negotiation or pending signature\n- Amendments and addenda\n\n#### CRM -- If Connected\nSearch for the vendor\u002Faccount record:\n- Account status and relationship type\n- Associated opportunities or deals\n- Contact information for vendor's legal\u002Fcontracts team\n\n#### Email -- If Connected\nSearch for recent relevant correspondence:\n- Contract-related emails (last 6 months)\n- NDA or agreement attachments\n- Negotiation threads\n\n#### Documents (e.g., Box, Egnyte, SharePoint) -- If Connected\nSearch for:\n- Executed agreements\n- Redlines and drafts\n- Due diligence materials\n\n#### Chat (e.g., Slack, Teams) -- If Connected\nSearch for recent mentions:\n- Contract requests involving this vendor\n- Legal questions about the vendor\n- Relevant team discussions (last 3 months)\n\n### Step 3: Compile Agreement Status\n\nFor each agreement found, report:\n\n| Field | Details |\n|-------|---------|\n| **Agreement Type** | NDA, MSA, SOW, DPA, SLA, License Agreement, etc. |\n| **Status** | Active, Expired, In Negotiation, Pending Signature |\n| **Effective Date** | When the agreement started |\n| **Expiration Date** | When it expires or renews |\n| **Auto-Renewal** | Yes\u002FNo, with renewal term and notice period |\n| **Key Terms** | Liability cap, governing law, termination provisions |\n| **Amendments** | Any amendments or addenda on file |\n\n### Step 4: Gap Analysis\n\nIdentify what agreements exist and what might be missing:\n\n```\n## Agreement Coverage\n\n[CHECK] NDA -- [status]\n[CHECK\u002FMISSING] MSA -- [status or \"Not found\"]\n[CHECK\u002FMISSING] DPA -- [status or \"Not found\"]\n[CHECK\u002FMISSING] SOW(s) -- [status or \"Not found\"]\n[CHECK\u002FMISSING] SLA -- [status or \"Not found\"]\n[CHECK\u002FMISSING] Insurance Certificate -- [status or \"Not found\"]\n```\n\nFlag any gaps that may be needed based on the relationship type (e.g., if there is an MSA but no DPA and the vendor handles personal data).\n\n### Step 5: Generate Report\n\nOutput a consolidated report:\n\n```\n## Vendor Agreement Status: [Vendor Name]\n\n**Search Date**: [today's date]\n**Sources Checked**: [list of systems searched]\n**Sources Unavailable**: [list of systems not connected, if any]\n\n## Relationship Overview\n\n**Vendor**: [full legal name]\n**Relationship Type**: [vendor\u002Fpartner\u002Fcustomer\u002Fetc.]\n**CRM Status**: [if available]\n\n## Agreement Summary\n\n### [Agreement Type 1] -- [Status]\n- **Effective**: [date]\n- **Expires**: [date] ([auto-renews \u002F does not auto-renew])\n- **Key Terms**: [summary of material terms]\n- **Location**: [where the executed copy is stored]\n\n### [Agreement Type 2] -- [Status]\n[etc.]\n\n## Gap Analysis\n\n[What's in place vs. what may be needed]\n\n## Upcoming Actions\n\n- [Any approaching expirations or renewal deadlines]\n- [Required agreements not yet in place]\n- [Amendments or updates that may be needed]\n\n## Notes\n\n[Any relevant context from email\u002Fchat searches]\n```\n\n### Step 6: Handle Missing Sources\n\nIf key systems are not connected via MCP:\n\n- **No CLM**: Note that no CLM is connected. Suggest the user check their CLM manually. Report what was found in other systems.\n- **No CRM**: Skip CRM context. Note the gap.\n- **No Email**: Note that email was not searched. Suggest the user search their email for \"[vendor name] agreement\" or \"[vendor name] NDA\".\n- **No Documents**: Note that document storage was not searched.\n\nAlways clearly state which sources were checked and which were not, so the user knows the completeness of the report.\n\n## Notes\n\n- If no agreements are found in any connected system, report that clearly and ask the user if they have agreements stored elsewhere\n- For vendor groups (e.g., a vendor with multiple subsidiaries), ask whether the user wants to check a specific entity or the entire group\n- Flag any agreements that are expired but may still have surviving obligations (confidentiality, indemnification, etc.)\n- If an agreement is approaching expiration (within 90 days), highlight this prominently\n","> Packaging adaptation by AutoGPT, 2026-09-25. Original authorship and licence are retained. Changes are limited to the recorded name, metadata and file references; see ATTRIBUTION.md in this skill package.\n\n\n# \u002Fvendor-check -- Vendor Agreement Status\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](references\u002FCONNECTORS.md).\n\nCheck the status of existing agreements with a vendor across all connected systems. Provides a consolidated view of the legal relationship.\n\n**Important**: This command assists with legal workflows but does not provide legal advice. Agreement status reports should be verified against original documents by qualified legal professionals.\n\n## Invocation\n\n```\n\u002Fvendor-check [vendor name]\n```\n\nIf no vendor name is provided, prompt the user to specify which vendor to check.\n\n## Workflow\n\n### Step 1: Identify the Vendor\n\nAccept the vendor name from the user. Handle common variations:\n- Full legal name vs. trade name (e.g., \"Alphabet Inc.\" vs. \"Google\")\n- Abbreviations (e.g., \"AWS\" vs. \"Amazon Web Services\")\n- Parent\u002Fsubsidiary relationships\n\nAsk the user to clarify if the vendor name is ambiguous.\n\n### Step 2: Search Connected Systems\n\nSearch for the vendor across all available connected systems, in priority order:\n\n#### CLM (Contract Lifecycle Management) -- If Connected\nSearch for all contracts involving the vendor:\n- Active agreements\n- Expired agreements (last 3 years)\n- Agreements in negotiation or pending signature\n- Amendments and addenda\n\n#### CRM -- If Connected\nSearch for the vendor\u002Faccount record:\n- Account status and relationship type\n- Associated opportunities or deals\n- Contact information for vendor's legal\u002Fcontracts team\n\n#### Email -- If Connected\nSearch for recent relevant correspondence:\n- Contract-related emails (last 6 months)\n- NDA or agreement attachments\n- Negotiation threads\n\n#### Documents (e.g., Box, Egnyte, SharePoint) -- If Connected\nSearch for:\n- Executed agreements\n- Redlines and drafts\n- Due diligence materials\n\n#### Chat (e.g., Slack, Teams) -- If Connected\nSearch for recent mentions:\n- Contract requests involving this vendor\n- Legal questions about the vendor\n- Relevant team discussions (last 3 months)\n\n### Step 3: Compile Agreement Status\n\nFor each agreement found, report:\n\n| Field | Details |\n|-------|---------|\n| **Agreement Type** | NDA, MSA, SOW, DPA, SLA, License Agreement, etc. |\n| **Status** | Active, Expired, In Negotiation, Pending Signature |\n| **Effective Date** | When the agreement started |\n| **Expiration Date** | When it expires or renews |\n| **Auto-Renewal** | Yes\u002FNo, with renewal term and notice period |\n| **Key Terms** | Liability cap, governing law, termination provisions |\n| **Amendments** | Any amendments or addenda on file |\n\n### Step 4: Gap Analysis\n\nIdentify what agreements exist and what might be missing:\n\n```\n## Agreement Coverage\n\n[CHECK] NDA -- [status]\n[CHECK\u002FMISSING] MSA -- [status or \"Not found\"]\n[CHECK\u002FMISSING] DPA -- [status or \"Not found\"]\n[CHECK\u002FMISSING] SOW(s) -- [status or \"Not found\"]\n[CHECK\u002FMISSING] SLA -- [status or \"Not found\"]\n[CHECK\u002FMISSING] Insurance Certificate -- [status or \"Not found\"]\n```\n\nFlag any gaps that may be needed based on the relationship type (e.g., if there is an MSA but no DPA and the vendor handles personal data).\n\n### Step 5: Generate Report\n\nOutput a consolidated report:\n\n```\n## Vendor Agreement Status: [Vendor Name]\n\n**Search Date**: [today's date]\n**Sources Checked**: [list of systems searched]\n**Sources Unavailable**: [list of systems not connected, if any]\n\n## Relationship Overview\n\n**Vendor**: [full legal name]\n**Relationship Type**: [vendor\u002Fpartner\u002Fcustomer\u002Fetc.]\n**CRM Status**: [if available]\n\n## Agreement Summary\n\n### [Agreement Type 1] -- [Status]\n- **Effective**: [date]\n- **Expires**: [date] ([auto-renews \u002F does not auto-renew])\n- **Key Terms**: [summary of material terms]\n- **Location**: [where the executed copy is stored]\n\n### [Agreement Type 2] -- [Status]\n[etc.]\n\n## Gap Analysis\n\n[What's in place vs. what may be needed]\n\n## Upcoming Actions\n\n- [Any approaching expirations or renewal deadlines]\n- [Required agreements not yet in place]\n- [Amendments or updates that may be needed]\n\n## Notes\n\n[Any relevant context from email\u002Fchat searches]\n```\n\n### Step 6: Handle Missing Sources\n\nIf key systems are not connected via MCP:\n\n- **No CLM**: Note that no CLM is connected. Suggest the user check their CLM manually. Report what was found in other systems.\n- **No CRM**: Skip CRM context. Note the gap.\n- **No Email**: Note that email was not searched. Suggest the user search their email for \"[vendor name] agreement\" or \"[vendor name] NDA\".\n- **No Documents**: Note that document storage was not searched.\n\nAlways clearly state which sources were checked and which were not, so the user knows the completeness of the report.\n\n## Notes\n\n- If no agreements are found in any connected system, report that clearly and ask the user if they have agreements stored elsewhere\n- For vendor groups (e.g., a vendor with multiple subsidiaries), ask whether the user wants to check a specific entity or the entire group\n- Flag any agreements that are expired but may still have surviving obligations (confidentiality, indemnification, etc.)\n- If an agreement is approaching expiration (within 90 days), highlight this prominently\n",{"name":5,"license":15,"metadata":42,"description":7,"argument-hint":49},{"author":43,"source":44,"source_url":45,"packaged-by":12,"packaged-on":46,"original-name":47,"upstream-commit":48},"Anthropic and upstream contributors","anthropics\u002Fknowledge-work-plugins\u002Flegal\u002Fskills\u002Fvendor-check","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002F1c7187c4fc17feefa6cde39517f12dae1249e6c4\u002Flegal\u002Fskills\u002Fvendor-check\u002FSKILL.md","2026-09-25","vendor-check","1c7187c4fc17feefa6cde39517f12dae1249e6c4","[vendor name]","main","7ed3b73314d5186120e8d4006febfd7e1c92cf08","skills\u002Fvendor-contract-status",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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add Significant-Gravitas\u002Fskills-catalog --skill vendor-contract-status",{"tool":64,"command":65},"bunx","bunx skills add Significant-Gravitas\u002Fskills-catalog --skill vendor-contract-status",{"tool":67,"command":68},"pnpm","pnpm dlx skills add Significant-Gravitas\u002Fskills-catalog --skill vendor-contract-status","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-contract-status\u002FSKILL.md",true,[72,78,82],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"ATTRIBUTION.md","REFERENCE","参考文档",4817,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-contract-status\u002FATTRIBUTION.md",{"path":79,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":16},"LICENSE","许可证",11358,{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002FCONNECTORS.md",1545,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-contract-status\u002Freferences\u002FCONNECTORS.md",[87,98,122,132,146,159],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":37},"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",[],[95,96,36,35,32,97],"workplace memory management","memory","directory",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":115,"publishedAt":37},"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",[106,109,112],{"categoryNo":107,"categoryName":108,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":110,"categoryName":111,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":113,"categoryName":114,"taxonomyType":27,"taxonomyTypeDesc":28},"01JBSEEDCAT000000000000035","市场营销",[116,117,118,36,35,119,120,121,32],"website seo audit","audit","website","search","report","plugin",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":37},"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",[],[130,131,35,32],"verification before completion","verification",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":37},"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",[],[140,141,36,35,142,143,144,32,145],"vendor evaluation","negotiation","assessment","risk assessment","cost analysis","review",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":150,"sourceHtmlUrl":151,"categories":152,"keywords":156,"publishedAt":37},"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",[153],{"categoryNo":154,"categoryName":155,"taxonomyType":27,"taxonomyTypeDesc":28},"01JBSEEDCAT000000000000033","数据分析师",[157,158,32,35],"user cohort analysis","analytics",{"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":166,"publishedAt":37},"01M6AD20HMJC8E93WTGYWNNG9Y","team-capacity-planning","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.","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",[],[167,168,169,36,32,170,35,171],"capacity","planning","team capacity planning","workload","testing"]