[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QAZCAD5VGA998H42WV7SC9":3,"skill-same:01M6QAZCAD5VGA998H42WV7SC9":74},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":14,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6QAZCAD5VGA998H42WV7SC9","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.","Tashima-Tarsh\u002FDisha6.6","Tashima-Tarsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269906498?v=4","01M6PBH98X03XERH0HFT4PFB1P","NITISH KUMAR","01M6PBH9DA0M6KM3Z12P848F0K",0,"MIT","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fboard-deck-builder\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"board deck builder","board","deck","builder","deck builder","delivery","mistakes","suite","updates","reviews","narrative","investor update","bad","fundraising","update","structure","perspectives","common","template","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---\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","# 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":44,"description":7},{"author":45,"domain":46,"updated":47,"version":48,"category":49,"frameworks":50},"Alireza Rezvani","board-governance",1772668800000,"1.0.0","c-level","deck-frameworks, board-deck-template","main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Fboard-deck-builder","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6","https:\u002F\u002Fdisha6.6.thenitishkr.in\u002F","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh","www.thenitishkr","thenitishkr | AI • Cyber-security • Research\r\n","2026-11-08 03:33:25",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill board-deck-builder",{"tool":66,"command":67},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill board-deck-builder",{"tool":69,"command":70},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill board-deck-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fboard-deck-builder\u002FSKILL.md",true,[],[75,107,132,158,183,206],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":86,"publishedAt":39},"01M6QRD07D4TGNDK6VJ4EHF8BV","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","get","age","trigger","URL","for","browsing","request","youtube transcripts",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":39},"01M6QRCJ3112VYPA97YG7KGMC2","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[114,115,116,117,91,118,119,120,121,122,123,124,125,126,127,128,129,130,131,103],"twitter","x twitter growth","growth","research","content","engineering","plan","web search","competitors","analyze","engine","write","strategy","use","platform","grow","posting","competitive",{"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":6,"sourceHtmlUrl":136,"categories":137,"keywords":141,"publishedAt":39},"01M6QRBN3EHQNJY42RERP7A149","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[138],{"categoryNo":139,"categoryName":140,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000023","Skill与智能体开发",[142,125,143,144,145,146,147,148,127,149,150,51,151,34,152,153,154,155,156,157],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":39},"01M6QRB6G8P33PNGAF9Y69EJ9T","wrap-up","Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says \"wrap up\", \"close this out\", \"what do I own now\", \"give me the summary\", \"recap the agent\", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained .\u002Fmy-agent\u002Fagent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[165,166,167,168,169,170,171,172,173,127,174,98,175,176,177,178,179,180,181,182],"wrap up","up","wrap","gemini","deployment","run","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":190,"publishedAt":39},"01M6QRA5AYC1RBFZ39GTWGS3N8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[189],{"categoryNo":139,"categoryName":140,"taxonomyType":84,"taxonomyTypeDesc":85},[191,192,22,193,194,144,170,195,196,197,198,199,125,200,97,201,202,203,204,205],"workflow","workflow builder","design","workflows","code","orchestrate","pipeline","loop","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":212,"publishedAt":39},"01M6QR7QMCZESKQA0ERW1E657M","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[213,214,215,216,217,218,219,220,221,198,222,223,224,225,226,227,99,228,229,182],"review","weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","scanner","conversation","back","project","sprint","cadence"]