[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71N5PC5P14887ZKGC7BD7RT":3,"skill-same:01M71N5PC5P14887ZKGC7BD7RT":77},{"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":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M71N5PC5P14887ZKGC7BD7RT","investor-materials",null,"Use when creating or updating pitch decks, one-pagers, investor memos, accelerator applications, financial models or use-of-funds tables. Enforces one source of truth so every fundraising document agrees on metrics, raise size and milestones.","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\u002Finvestor-materials\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Finvestor-materials\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"investor materials","materials","metrics","tables","source","finance","https","raise","models","github","size","one","when","document","pitch","use","writing","milestones","applications","fundraising","2026-11-10 10:56:23",false,"---\nname: investor-materials\ndescription: \"Use when creating or updating pitch decks, one-pagers, investor memos, accelerator applications, financial models or use-of-funds tables. Enforces one source of truth so every fundraising document agrees on metrics, raise size and milestones.\"\ntags: [\"finance\",\"writing\",\"fundraising\"]\ntools: []\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002Faffaan-m\u002FECC\nsource_path: \"skills\u002Finvestor-materials\"\nsource_commit: bf70150eb2df8070024e5bdf08e4aa08959e2735\n---\n# Investor Materials\n\nBuild investor-facing materials that are consistent, credible, and easy to defend.\n\n## When to Activate\n\n- creating or revising a pitch deck\n- writing an investor memo or one-pager\n- building a financial model, milestone plan, or use-of-funds table\n- answering accelerator or incubator application questions\n- aligning multiple fundraising docs around one source of truth\n\n## Golden Rule\n\nAll investor materials must agree with each other.\n\nCreate or confirm a single source of truth before writing:\n- traction metrics\n- pricing and revenue assumptions\n- raise size and instrument\n- use of funds\n- team bios and titles\n- milestones and timelines\n\nIf conflicting numbers appear, stop and resolve them before drafting.\n\n## Core Workflow\n\n1. inventory the canonical facts\n2. identify missing assumptions\n3. choose the asset type\n4. draft the asset with explicit logic\n5. cross-check every number against the source of truth\n\n## Asset Guidance\n\n### Pitch Deck\nRecommended flow:\n1. company + wedge\n2. problem\n3. solution\n4. product \u002F demo\n5. market\n6. business model\n7. traction\n8. team\n9. competition \u002F differentiation\n10. ask\n11. use of funds \u002F milestones\n12. appendix\n\nIf the user wants a web-native deck, pair this skill with `frontend-slides`.\n\n### One-Pager \u002F Memo\n- state what the company does in one clean sentence\n- show why now\n- include traction and proof points early\n- make the ask precise\n- keep claims easy to verify\n\n### Financial Model\nInclude:\n- explicit assumptions\n- bear \u002F base \u002F bull cases when useful\n- clean layer-by-layer revenue logic\n- milestone-linked spending\n- sensitivity analysis where the decision hinges on assumptions\n\n### Accelerator Applications\n- answer the exact question asked\n- prioritize traction, insight, and team advantage\n- avoid puffery\n- keep internal metrics consistent with the deck and model\n\n## Red Flags to Avoid\n\n- unverifiable claims\n- fuzzy market sizing without assumptions\n- inconsistent team roles or titles\n- revenue math that does not sum cleanly\n- inflated certainty where assumptions are fragile\n\n## Quality Gate\n\nBefore delivering:\n- every number matches the current source of truth\n- use of funds and revenue layers sum correctly\n- assumptions are visible, not buried\n- the story is clear without hype language\n- the final asset is defensible in a partner meeting\n","# Investor Materials\n\nBuild investor-facing materials that are consistent, credible, and easy to defend.\n\n## When to Activate\n\n- creating or revising a pitch deck\n- writing an investor memo or one-pager\n- building a financial model, milestone plan, or use-of-funds table\n- answering accelerator or incubator application questions\n- aligning multiple fundraising docs around one source of truth\n\n## Golden Rule\n\nAll investor materials must agree with each other.\n\nCreate or confirm a single source of truth before writing:\n- traction metrics\n- pricing and revenue assumptions\n- raise size and instrument\n- use of funds\n- team bios and titles\n- milestones and timelines\n\nIf conflicting numbers appear, stop and resolve them before drafting.\n\n## Core Workflow\n\n1. inventory the canonical facts\n2. identify missing assumptions\n3. choose the asset type\n4. draft the asset with explicit logic\n5. cross-check every number against the source of truth\n\n## Asset Guidance\n\n### Pitch Deck\nRecommended flow:\n1. company + wedge\n2. problem\n3. solution\n4. product \u002F demo\n5. market\n6. business model\n7. traction\n8. team\n9. competition \u002F differentiation\n10. ask\n11. use of funds \u002F milestones\n12. appendix\n\nIf the user wants a web-native deck, pair this skill with `frontend-slides`.\n\n### One-Pager \u002F Memo\n- state what the company does in one clean sentence\n- show why now\n- include traction and proof points early\n- make the ask precise\n- keep claims easy to verify\n\n### Financial Model\nInclude:\n- explicit assumptions\n- bear \u002F base \u002F bull cases when useful\n- clean layer-by-layer revenue logic\n- milestone-linked spending\n- sensitivity analysis where the decision hinges on assumptions\n\n### Accelerator Applications\n- answer the exact question asked\n- prioritize traction, insight, and team advantage\n- avoid puffery\n- keep internal metrics consistent with the deck and model\n\n## Red Flags to Avoid\n\n- unverifiable claims\n- fuzzy market sizing without assumptions\n- inconsistent team roles or titles\n- revenue math that does not sum cleanly\n- inflated certainty where assumptions are fragile\n\n## Quality Gate\n\nBefore delivering:\n- every number matches the current source of truth\n- use of funds and revenue layers sum correctly\n- assumptions are visible, not buried\n- the story is clear without hype language\n- the final asset is defensible in a partner meeting\n",{"name":5,"tags":44,"tools":45,"source":46,"license":14,"description":7,"source_path":47,"source_commit":48},[24,35,38],[],"https:\u002F\u002Fgithub.com\u002Faffaan-m\u002FECC","skills\u002Finvestor-materials","bf70150eb2df8070024e5bdf08e4aa08959e2735","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Finvestor-materials",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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add monoes\u002Fmonomind --skill investor-materials",{"tool":64,"command":65},"bunx","bunx skills add monoes\u002Fmonomind --skill investor-materials",{"tool":67,"command":68},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill investor-materials","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Finvestor-materials\u002FSKILL.md",true,[72],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",1071,[78,107,141,165,188,215],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":106},"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",[],[86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105],"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":124,"publishedAt":106},"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",[114,119],{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[35,125,126,90,127,128,31,129,95,130,131,132,133,134,135,136,137,138,139,140],"writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":151,"publishedAt":106},"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",[148],{"categoryNo":149,"categoryName":150,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000031","产品经理",[134,152,153,154,155,93,156,31,157,158,159,133,160,161,162,21,163,164,34,32],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","feature","problem statement",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":169,"sourceHtmlUrl":170,"categories":171,"keywords":175,"publishedAt":106},"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",[172],{"categoryNo":173,"categoryName":174,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000033","数据分析师",[95,134,176,177,178,179,93,34,31,180,181,182,183,159,28,184,25,185,186,187],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","sql","syntax","plugins","data",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":200,"publishedAt":106},"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",[194,197],{"categoryNo":195,"categoryName":196,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":198,"categoryName":199,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000023","Skill与智能体开发",[201,202,203,204,178,205,206,207,208,94,209,210,211,95,98,28,212,213,214,25],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":222,"publishedAt":106},"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",[221],{"categoryNo":198,"categoryName":199,"taxonomyType":117,"taxonomyTypeDesc":118},[203,223,224,225,226,227,228,178,229,230,130,231,232,233,98,28,234,235,25,236],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]