[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACFFWEBM8KA39THQF2RAJA":3,"skill-same:01M6ACFFWEBM8KA39THQF2RAJA":101},{"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":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M6ACFFWEBM8KA39THQF2RAJA","board-deck-builder",null,"Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes.","Significant-Gravitas\u002Fskills-catalog","Significant-Gravitas","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F130738209?v=4","01M6AC83EPDGBFN19MWYRREJD0","AutoGPT","01M6ACEY98TKHDWJH0B93PHNMG",2,"MIT","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fboard-deck-builder\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fboard-deck-builder\u002FSKILL.md",[],[20,21,22,23,24],"board deck builder","github","governance","update","framework","2026-11-10 10:12:30",false,"---\nname: board-deck-builder\ndescription: Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: board-governance\n  updated: '2026-03-05'\n  frameworks: deck-frameworks, board-deck-template\n  source: alirezarezvani\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fboard-deck-builder\n  source_url: https:\u002F\u002Fgithub.com\u002Falirezarezvani\u002Fclaude-skills\u002Fblob\u002F19392f7a08264ed00486a251f5b2098321771f94\u002Fc-level-advisor\u002Fskills\u002Fboard-deck-builder\u002FSKILL.md\n  upstream-commit: 19392f7a08264ed00486a251f5b2098321771f94\n  original-name: board-deck-builder\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# Board Deck Builder\n\nBuild board decks that tell a story — not just show data. Every section has an owner, a narrative, and a \"so what.\"\n\n## Keywords\nboard deck, investor update, board meeting, board pack, investor relations, quarterly review, board presentation, fundraising deck, investor deck, board narrative, QBR, quarterly business review\n\n## Quick Start\n\nAsk for a board deck in natural language, naming cadence and stage:\n\n> \"Build a quarterly board deck — we're Series A.\"\n> \"Draft a fundraising board deck for a seed-stage company.\"\n\nProvide available metrics. The builder fills gaps with explicit placeholders — never invents numbers.\n\n## Deck Structure (Standard Order)\n\nEvery section follows: **Headline → Data → Narrative → Ask\u002FNext**\n\n### 1. Executive Summary (CEO)\n**3 sentences. No more.**\n- Sentence 1: State of the business (where we are)\n- Sentence 2: Biggest thing that happened this period\n- Sentence 3: Where we're going next quarter\n\n*Bad:* \"We had a good quarter with lots of progress across all areas.\"\n*Good:* \"We closed Q3 at $2.4M ARR (+22% QoQ), signed our largest enterprise contract, and enter Q4 with 14-month runway. The strategic shift to mid-market is working — ACV up 40% and sales cycle down 3 weeks. Q4 priority: close the $3M Series A and hit $2.8M ARR.\"\n\n### 2. Key Metrics Dashboard (COO)\n**6-8 metrics max. Use a table.**\n\n| Metric | This Period | Last Period | Target | Status |\n|--------|-------------|-------------|--------|--------|\n| ARR | $2.4M | $1.97M | $2.3M | ✅ |\n| MoM growth | 8.1% | 7.2% | 7.5% | ✅ |\n| Burn multiple | 1.8x | 2.1x | \u003C2x | ✅ |\n| NRR | 112% | 108% | >110% | ✅ |\n| CAC payback | 11 months | 14 months | \u003C12 months | ✅ |\n| Headcount | 24 | 21 | 25 | ? |\n\nPick metrics the board actually tracks. Swap out anything they've said they don't care about.\n\n### 3. Financial Update (CFO)\n- P&L summary: Revenue, COGS, Gross margin, OpEx, Net burn\n- Cash position and runway (months)\n- Burn multiple trend (3-quarter view)\n- Variance to plan (what was different and why)\n- Forecast update for next quarter\n\n**One sentence on each variance.** Boards hate \"revenue was below target\" with no explanation. Say why.\n\n### 4. Revenue & Pipeline (CRO)\n- ARR waterfall: starting → new → expansion → churn → ending\n- NRR and logo churn rates\n- Pipeline by stage (in $, not just count)\n- Forecast: next quarter with confidence level\n- Top 3 deals: name\u002Famount\u002Fclose date\u002Frisk\n\n**The forecast must have a confidence level.** \"We expect $2.8M\" is weak. \"High confidence $2.6M, upside to $2.9M if two late-stage deals close\" is useful.\n\n### 5. Product Update (CPO)\n- Shipped this quarter: 3-5 bullets, user impact for each\n- Shipping next quarter: 3-5 bullets with target dates\n- PMF signal: NPS trend, DAU\u002FMAU ratio, feature adoption\n- One key learning from customer research\n\n**No feature lists.** Only features with evidence of user impact.\n\n### 6. Growth & Marketing (CMO)\n- CAC by channel (table)\n- Pipeline contribution by channel ($)\n- Brand\u002Fawareness metrics relevant to stage (traffic, share of voice)\n- What's working, what's being cut, what's being tested\n\n### 7. Engineering & Technical (CTO)\n- Delivery velocity trend (last 4 quarters)\n- Tech debt ratio and plan\n- Infrastructure: uptime, incidents, cost trend\n- Security posture (one line, flag anything pending)\n\n**Keep this short unless there's a material issue.** Boards don't need sprint details.\n\n### 8. Team & People (CHRO)\n- Headcount: actual vs plan\n- Hiring: offers out, pipeline, time-to-fill trend\n- Attrition: regrettable vs non-regrettable\n- Engagement: last survey score, trend\n- Key hires this quarter, key open roles\n\n### 9. Risk & Security (CISO)\n- Security posture: status of critical controls\n- Compliance: certifications in progress, deadlines\n- Incidents this quarter (if any): impact, resolution, prevention\n- Top 3 risks and mitigation status\n\n### 10. Strategic Outlook (CEO)\n- Next quarter priorities: 3-5 items, ranked\n- Key decisions needed from the board\n- Asks: budget, introductions, advice, votes\n\n**The \"asks\" slide is the most important.** Be specific. \"We'd like 3 warm introductions to CFOs at Series B companies\" beats \"any help would be appreciated.\"\n\n### 11. Appendix\n- Detailed financial model\n- Full pipeline data\n- Cohort retention charts\n- Customer case studies\n- Detailed headcount breakdown\n\n---\n\n## Narrative Framework\n\nBoards see 10+ decks per quarter. Yours needs a through-line.\n\n**The 4-Act Structure:**\n1. **Where we said we'd be** (last quarter's targets)\n2. **Where we actually are** (honest assessment)\n3. **Why the gap exists** (one cause per variance, not excuses)\n4. **What we're doing about it** (specific, dated actions)\n\nThis works for good news AND bad news. It's credible because it acknowledges reality.\n\n**Opening frame:** Start with the one thing that matters most — the board should know the key message by slide 3, not slide 30.\n\n---\n\n## Delivering Bad News\n\nNever bury it. Boards find out eventually. Finding out late makes it worse.\n\n**Framework:**\n1. **State it plainly** — \"We missed Q3 ARR target by $300K (12% gap)\"\n2. **Own the cause** — \"Primary driver was longer-than-expected sales cycle in enterprise segment\"\n3. **Show you understand it** — \"We analyzed 8 lost\u002Fstalled deals; the pattern is X\"\n4. **Present the fix** — \"We've made 3 changes: [specific, dated changes]\"\n5. **Update the forecast** — \"Revised Q4 target is $2.6M; here's the bottom-up build\"\n\n**What NOT to do:**\n- Don't lead with good news to soften bad news — boards notice and distrust the framing\n- Don't explain without owning — \"market conditions\" is not a cause, it's a context\n- Don't present a fix without data behind it\n- Don't show a revised forecast without showing your assumptions\n\n---\n\n## Common Board Deck Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Too many slides (>25) | Cut ruthlessly — if you can't explain it in the room, the slide is wrong |\n| Metrics without targets | Every metric needs a target and a status |\n| No narrative | Data without story forces boards to draw their own conclusions |\n| Burying bad news | Lead with it, own it, fix it |\n| Vague asks | Specific, actionable, person-assigned asks only |\n| No variance explanation | Every gap from target needs one-sentence cause |\n| Stale appendix | Appendix is only useful if it's current |\n| Designing for the reader, not the room | Decks are presented — they must work spoken aloud |\n\n---\n\n## Cadence Notes\n\n**Quarterly (standard):** Full deck, all sections, 20-30 slides. Sent 48 hours in advance.\n**Monthly (for early-stage):** Condensed — metrics dashboard, financials, pipeline, top risks. 8-12 slides.\n**Fundraising:** Opens with market\u002Fvision, closes with ask. See `references\u002Fdeck-frameworks.md` for Sequoia format.\n\n## References\n- `references\u002Fdeck-frameworks.md` — SaaS board pack format, Sequoia structure, investor tailoring\n- `templates\u002Fboard-deck-template.md` — fill-in template for complete board decks\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# Board Deck Builder\n\nBuild board decks that tell a story — not just show data. Every section has an owner, a narrative, and a \"so what.\"\n\n## Keywords\nboard deck, investor update, board meeting, board pack, investor relations, quarterly review, board presentation, fundraising deck, investor deck, board narrative, QBR, quarterly business review\n\n## Quick Start\n\nAsk for a board deck in natural language, naming cadence and stage:\n\n> \"Build a quarterly board deck — we're Series A.\"\n> \"Draft a fundraising board deck for a seed-stage company.\"\n\nProvide available metrics. The builder fills gaps with explicit placeholders — never invents numbers.\n\n## Deck Structure (Standard Order)\n\nEvery section follows: **Headline → Data → Narrative → Ask\u002FNext**\n\n### 1. Executive Summary (CEO)\n**3 sentences. No more.**\n- Sentence 1: State of the business (where we are)\n- Sentence 2: Biggest thing that happened this period\n- Sentence 3: Where we're going next quarter\n\n*Bad:* \"We had a good quarter with lots of progress across all areas.\"\n*Good:* \"We closed Q3 at $2.4M ARR (+22% QoQ), signed our largest enterprise contract, and enter Q4 with 14-month runway. The strategic shift to mid-market is working — ACV up 40% and sales cycle down 3 weeks. Q4 priority: close the $3M Series A and hit $2.8M ARR.\"\n\n### 2. Key Metrics Dashboard (COO)\n**6-8 metrics max. Use a table.**\n\n| Metric | This Period | Last Period | Target | Status |\n|--------|-------------|-------------|--------|--------|\n| ARR | $2.4M | $1.97M | $2.3M | ✅ |\n| MoM growth | 8.1% | 7.2% | 7.5% | ✅ |\n| Burn multiple | 1.8x | 2.1x | \u003C2x | ✅ |\n| NRR | 112% | 108% | >110% | ✅ |\n| CAC payback | 11 months | 14 months | \u003C12 months | ✅ |\n| Headcount | 24 | 21 | 25 | ? |\n\nPick metrics the board actually tracks. Swap out anything they've said they don't care about.\n\n### 3. Financial Update (CFO)\n- P&L summary: Revenue, COGS, Gross margin, OpEx, Net burn\n- Cash position and runway (months)\n- Burn multiple trend (3-quarter view)\n- Variance to plan (what was different and why)\n- Forecast update for next quarter\n\n**One sentence on each variance.** Boards hate \"revenue was below target\" with no explanation. Say why.\n\n### 4. Revenue & Pipeline (CRO)\n- ARR waterfall: starting → new → expansion → churn → ending\n- NRR and logo churn rates\n- Pipeline by stage (in $, not just count)\n- Forecast: next quarter with confidence level\n- Top 3 deals: name\u002Famount\u002Fclose date\u002Frisk\n\n**The forecast must have a confidence level.** \"We expect $2.8M\" is weak. \"High confidence $2.6M, upside to $2.9M if two late-stage deals close\" is useful.\n\n### 5. Product Update (CPO)\n- Shipped this quarter: 3-5 bullets, user impact for each\n- Shipping next quarter: 3-5 bullets with target dates\n- PMF signal: NPS trend, DAU\u002FMAU ratio, feature adoption\n- One key learning from customer research\n\n**No feature lists.** Only features with evidence of user impact.\n\n### 6. Growth & Marketing (CMO)\n- CAC by channel (table)\n- Pipeline contribution by channel ($)\n- Brand\u002Fawareness metrics relevant to stage (traffic, share of voice)\n- What's working, what's being cut, what's being tested\n\n### 7. Engineering & Technical (CTO)\n- Delivery velocity trend (last 4 quarters)\n- Tech debt ratio and plan\n- Infrastructure: uptime, incidents, cost trend\n- Security posture (one line, flag anything pending)\n\n**Keep this short unless there's a material issue.** Boards don't need sprint details.\n\n### 8. Team & People (CHRO)\n- Headcount: actual vs plan\n- Hiring: offers out, pipeline, time-to-fill trend\n- Attrition: regrettable vs non-regrettable\n- Engagement: last survey score, trend\n- Key hires this quarter, key open roles\n\n### 9. Risk & Security (CISO)\n- Security posture: status of critical controls\n- Compliance: certifications in progress, deadlines\n- Incidents this quarter (if any): impact, resolution, prevention\n- Top 3 risks and mitigation status\n\n### 10. Strategic Outlook (CEO)\n- Next quarter priorities: 3-5 items, ranked\n- Key decisions needed from the board\n- Asks: budget, introductions, advice, votes\n\n**The \"asks\" slide is the most important.** Be specific. \"We'd like 3 warm introductions to CFOs at Series B companies\" beats \"any help would be appreciated.\"\n\n### 11. Appendix\n- Detailed financial model\n- Full pipeline data\n- Cohort retention charts\n- Customer case studies\n- Detailed headcount breakdown\n\n---\n\n## Narrative Framework\n\nBoards see 10+ decks per quarter. Yours needs a through-line.\n\n**The 4-Act Structure:**\n1. **Where we said we'd be** (last quarter's targets)\n2. **Where we actually are** (honest assessment)\n3. **Why the gap exists** (one cause per variance, not excuses)\n4. **What we're doing about it** (specific, dated actions)\n\nThis works for good news AND bad news. It's credible because it acknowledges reality.\n\n**Opening frame:** Start with the one thing that matters most — the board should know the key message by slide 3, not slide 30.\n\n---\n\n## Delivering Bad News\n\nNever bury it. Boards find out eventually. Finding out late makes it worse.\n\n**Framework:**\n1. **State it plainly** — \"We missed Q3 ARR target by $300K (12% gap)\"\n2. **Own the cause** — \"Primary driver was longer-than-expected sales cycle in enterprise segment\"\n3. **Show you understand it** — \"We analyzed 8 lost\u002Fstalled deals; the pattern is X\"\n4. **Present the fix** — \"We've made 3 changes: [specific, dated changes]\"\n5. **Update the forecast** — \"Revised Q4 target is $2.6M; here's the bottom-up build\"\n\n**What NOT to do:**\n- Don't lead with good news to soften bad news — boards notice and distrust the framing\n- Don't explain without owning — \"market conditions\" is not a cause, it's a context\n- Don't present a fix without data behind it\n- Don't show a revised forecast without showing your assumptions\n\n---\n\n## Common Board Deck Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Too many slides (>25) | Cut ruthlessly — if you can't explain it in the room, the slide is wrong |\n| Metrics without targets | Every metric needs a target and a status |\n| No narrative | Data without story forces boards to draw their own conclusions |\n| Burying bad news | Lead with it, own it, fix it |\n| Vague asks | Specific, actionable, person-assigned asks only |\n| No variance explanation | Every gap from target needs one-sentence cause |\n| Stale appendix | Appendix is only useful if it's current |\n| Designing for the reader, not the room | Decks are presented — they must work spoken aloud |\n\n---\n\n## Cadence Notes\n\n**Quarterly (standard):** Full deck, all sections, 20-30 slides. Sent 48 hours in advance.\n**Monthly (for early-stage):** Condensed — metrics dashboard, financials, pipeline, top risks. 8-12 slides.\n**Fundraising:** Opens with market\u002Fvision, closes with ask. See `references\u002Fdeck-frameworks.md` for Sequoia format.\n\n## References\n- `references\u002Fdeck-frameworks.md` — SaaS board pack format, Sequoia structure, investor tailoring\n- `templates\u002Fboard-deck-template.md` — fill-in template for complete board decks\n",{"name":5,"license":15,"metadata":30,"description":7},{"author":31,"domain":32,"source":33,"updated":34,"version":35,"category":36,"frameworks":37,"source_url":38,"packaged-by":12,"packaged-on":39,"original-name":5,"upstream-commit":40},"Alireza Rezvani","board-governance","alirezarezvani\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fboard-deck-builder","2026-03-05","1.0.0","c-level","deck-frameworks, board-deck-template","https:\u002F\u002Fgithub.com\u002Falirezarezvani\u002Fclaude-skills\u002Fblob\u002F19392f7a08264ed00486a251f5b2098321771f94\u002Fc-level-advisor\u002Fskills\u002Fboard-deck-builder\u002FSKILL.md","2026-09-25","19392f7a08264ed00486a251f5b2098321771f94","main","7ed3b73314d5186120e8d4006febfd7e1c92cf08","skills\u002Fboard-deck-builder",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 board-deck-builder",{"tool":55,"command":56},"bunx","bunx skills add Significant-Gravitas\u002Fskills-catalog --skill board-deck-builder",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Significant-Gravitas\u002Fskills-catalog --skill board-deck-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fboard-deck-builder\u002FSKILL.md",true,[63,69,73,77,81,85,89,93,97],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"ATTRIBUTION.md","REFERENCE","参考文档",2238,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fboard-deck-builder\u002FATTRIBUTION.md",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"evals\u002Feval.yaml",2663,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-sdk-for-net\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fazsdk-common-prepare-release-plan\u002Fevals\u002Feval.yaml",{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":75,"sourceHtmlUrl":76},"evals\u002Fschedule-risk.eval.yaml",3207,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-sdk-for-net\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fazsdk-common-prepare-release-plan\u002Fevals\u002Fschedule-risk.eval.yaml",{"path":78,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":79,"sourceHtmlUrl":80},"evals\u002Ftrigger.eval.yaml",3228,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-sdk-for-net\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fazsdk-common-prepare-release-plan\u002Fevals\u002Ftrigger.eval.yaml",{"path":82,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":83,"sourceHtmlUrl":84},"fixtures\u002Ftspconfig.yaml",489,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-sdk-for-net\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fazsdk-common-prepare-release-plan\u002Ffixtures\u002Ftspconfig.yaml",{"path":86,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":16},"LICENSE","许可证",1072,{"path":90,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fdeck-frameworks.md",6952,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fboard-deck-builder\u002Freferences\u002Fdeck-frameworks.md",{"path":94,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Frelease-plan-details.md",2625,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-sdk-for-net\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fazsdk-common-prepare-release-plan\u002Freferences\u002Frelease-plan-details.md",{"path":98,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":99,"sourceHtmlUrl":100},"templates\u002Fboard-deck-template.md",5885,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fboard-deck-builder\u002Ftemplates\u002Fboard-deck-template.md",[102,116,143,153,167,185],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":25},"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.","Apache-2.0","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",[],[111,112,113,114,21,115],"workplace memory management","memory","plugins","https","directory",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":136,"publishedAt":25},"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.","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",[123,128,131],{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":129,"categoryName":130,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[137,138,139,21,113,114,140,141,142],"website seo audit","audit","website","search","report","plugin",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":147,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":25},"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",[],[151,152,114,21],"verification before completion","verification",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":157,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":25},"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",[],[161,162,113,114,163,164,165,21,166],"vendor evaluation","negotiation","assessment","risk assessment","cost analysis","review",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":171,"sourceHtmlUrl":172,"categories":173,"keywords":180,"publishedAt":25},"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",[174,177],{"categoryNo":175,"categoryName":176,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":178,"categoryName":179,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000037","律师与法务",[181,182,21,183,113,184,114],"vendor contract status","status","storage","onboarding",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":189,"sourceHtmlUrl":190,"categories":191,"keywords":195,"publishedAt":25},"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",[192],{"categoryNo":193,"categoryName":194,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000033","数据分析师",[196,197,114,21],"user cohort analysis","analytics"]