[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MCCKCVTW749DFN573WHD7":3,"skill-same:01M71MCCKCVTW749DFN573WHD7":89},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M71MCCKCVTW749DFN573WHD7","board-deck-builder",null,"Use when assembling a quarterly board or investor update deck or report: executive summary, metrics table, financials, per-function sections, bad-news delivery and asks. Pulls C-suite perspectives into one narrative and never invents numbers.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fboard-deck-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\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","deck builder","deck","board","builder","table","suite","update","delivery","advisor","communication","leadership","perspectives","narrative","when","writing","executive summary","claude-skills","investor update","never","2026-11-10 10:56:23",false,"---\nname: board-deck-builder\ndescription: \"Use when assembling a quarterly board or investor update deck or report: executive summary, metrics table, financials, per-function sections, bad-news delivery and asks. Pulls C-suite perspectives into one narrative and never invents numbers.\"\ntags: [\"leadership\",\"finance\",\"writing\",\"fundraising\",\"communication\"]\ntools: []\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002Falirezarezvani\u002Fclaude-skills\nsource_path: \"c-level-advisor\u002Fskills\u002Fboard-deck-builder\"\nsource_commit: 19392f7a08264ed00486a251f5b2098321771f94\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,"tags":44,"tools":47,"source":48,"license":14,"description":7,"source_path":49,"source_commit":50},[30,45,34,46,29],"finance","fundraising",[],"https:\u002F\u002Fgithub.com\u002Falirezarezvani\u002Fclaude-skills","c-level-advisor\u002Fskills\u002Fboard-deck-builder","19392f7a08264ed00486a251f5b2098321771f94","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fboard-deck-builder",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add monoes\u002Fmonomind --skill board-deck-builder",{"tool":66,"command":67},"bunx","bunx skills add monoes\u002Fmonomind --skill board-deck-builder",{"tool":69,"command":70},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill board-deck-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fboard-deck-builder\u002FSKILL.md",true,[74,79,85],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",1072,{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fdeck-frameworks.md","REFERENCE","参考文档",6952,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fboard-deck-builder\u002Freferences\u002Fdeck-frameworks.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"templates\u002Fboard-deck-template.md",5885,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fboard-deck-builder\u002Ftemplates\u002Fboard-deck-template.md",[90,119,153,180,205,232],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":118},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":136,"publishedAt":118},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[126,131],{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[34,137,138,102,139,140,33,141,107,142,143,144,145,146,147,148,149,150,151,152],"writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":94,"licenseFileUrl":157,"sourceHtmlUrl":158,"categories":159,"keywords":163,"publishedAt":118},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[160],{"categoryNo":161,"categoryName":162,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000031","产品经理",[146,164,165,166,167,105,168,33,169,170,171,145,172,173,174,175,176,177,178,179],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":94,"licenseFileUrl":184,"sourceHtmlUrl":185,"categories":186,"keywords":190,"publishedAt":118},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[187],{"categoryNo":188,"categoryName":189,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000033","数据分析师",[107,146,191,192,193,194,105,178,33,195,196,197,198,171,199,200,201,202,203,204],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":217,"publishedAt":118},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[211,214],{"categoryNo":212,"categoryName":213,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":215,"categoryName":216,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000023","Skill与智能体开发",[218,219,220,221,193,222,223,224,225,106,226,227,228,107,110,199,229,230,231,201],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":236,"categories":237,"keywords":239,"publishedAt":118},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[238],{"categoryNo":215,"categoryName":216,"taxonomyType":129,"taxonomyTypeDesc":130},[220,240,241,242,243,244,245,193,246,247,142,248,249,30,110,199,250,251,201,252],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","recovery","operations","systems"]