[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M750J2B6XPAPE2P0EM0RC58N":3,"skill-same:01M750J2B6XPAPE2P0EM0RC58N":47},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":29,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M750J2B6XPAPE2P0EM0RC58N","fundraising-stage-selector",null,"Use when a founder is deciding whether and how to raise. Triggers on \"am I pre-seed or seed\", \"how much should I raise\", \"what stage am I\", \"what valuation can I get\", \"should I raise now or wait\", \"is my round too big\". Sets the round, amount, and valuation envelope that every later step depends on.","SkillMedev\u002Fskills","SkillMedev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F298078254?v=4","01M74ZSGTQ918CB0VXW4EG3RMX","SkillMe","01M74ZSGVBT497NA95CBT8JTY4",25,"MIT","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ffundraising-stage-selector\u002FSKILL.md",[],[],"2026-11-11 17:59:37",false,"---\nname: fundraising-stage-selector\ndescription: Use when a founder is deciding whether and how to raise. Triggers on \"am I pre-seed or seed\", \"how much should I raise\", \"what stage am I\", \"what valuation can I get\", \"should I raise now or wait\", \"is my round too big\". Sets the round, amount, and valuation envelope that every later step depends on.\n---\n\n# Fundraising Stage Selector\n\nEvery later step - deck, targeting, terms - is wrong if the stage is wrong. The\nmost common founder error is raising at the stage they wish they were at, not\nthe one their evidence supports. This skill fixes the stage first.\n\n## When to use this skill\n\nReach for it before writing a deck or emailing an investor, whenever the\nfounder asks how much to raise, what valuation is realistic, or whether to raise\nat all yet. It produces the envelope; everything downstream is calibrated to it.\n\n## Read the stage off evidence, not ambition\n\nPlace the company by what is *proven*, not what is hoped:\n\n- **Pre-seed**: a team and an insight, maybe a prototype or design partners. You\n  are selling the founder and the bet. Typical raise $250k-$1.5M.\n- **Seed**: a shipped product and the first signal of pull - early revenue,\n  retention, or week-over-week usage growth. Typical raise $1.5M-$4M.\n- **Series A**: a working engine. Repeatable acquisition, real retention, and a\n  metric that scales (often ~$1M+ ARR for SaaS, with strong growth\u002Fretention).\n  Typical raise $6M-$15M.\n\nIf the evidence straddles two stages, you are at the lower one. Investors price\nthe floor of your story, not the ceiling.\n\n## Size the raise from the milestone, not the market\n\nDo not raise \"as much as you can.\" Raise the amount that buys the *next\nfundable milestone* plus margin:\n\n1. Name the milestone the next round requires (e.g. \"$1M ARR at 120% NRR\").\n2. Estimate monthly burn to get there and the months it takes.\n3. Raise milestone-cost x 1.5 (18-24 months of runway, never under 12).\n4. Sanity-check dilution: a healthy round sells 15-25%. If your target amount\n   forces >25% at a realistic valuation, the amount is too big or the valuation\n   too low - fix one.\n\n## Valuation envelope\n\nTriangulate, never anchor on a single hope:\n\n- **Comparables**: what companies with your traction raised recently, in your\n  geography and sector.\n- **Dilution math**: amount ÷ target dilution = post-money. ($2M for 20% =>\n  $10M post.)\n- **Instrument**: pre-seed\u002Fseed usually a SAFE with a valuation cap; priced\n  rounds start at seed\u002FA. Pair with [[safe-vs-priced-round]].\n\nThe number you can *defend* beats the number you can *dream*. An overpriced\nround you barely fill creates a down-round trap next time.\n\n## Should you raise at all?\n\nPush back before pulling forward. Don't raise if: the milestone is reachable on\nrevenue, the story has no proof and no clock, or dilution buys less than a clear\nstep-change. Bootstrapping a quarter to add proof often beats raising weak.\n\n## Anti-patterns\n\n- Pricing on TAM instead of traction.\n- A round so large it sets a Series A bar you cannot clear in 24 months.\n- Raising on \"everyone is raising\" with no milestone to point the cash at.\n\n## Deliverable\n\nA one-page raise thesis: stage (with the evidence that fixes it), amount, the\nnamed milestone it funds, months of runway, target dilution, and a defensible\nvaluation range with its comparables. Hand this to [[fundraise-readiness-audit]]\nbefore going out.\n","# Fundraising Stage Selector\n\nEvery later step - deck, targeting, terms - is wrong if the stage is wrong. The\nmost common founder error is raising at the stage they wish they were at, not\nthe one their evidence supports. This skill fixes the stage first.\n\n## When to use this skill\n\nReach for it before writing a deck or emailing an investor, whenever the\nfounder asks how much to raise, what valuation is realistic, or whether to raise\nat all yet. It produces the envelope; everything downstream is calibrated to it.\n\n## Read the stage off evidence, not ambition\n\nPlace the company by what is *proven*, not what is hoped:\n\n- **Pre-seed**: a team and an insight, maybe a prototype or design partners. You\n  are selling the founder and the bet. Typical raise $250k-$1.5M.\n- **Seed**: a shipped product and the first signal of pull - early revenue,\n  retention, or week-over-week usage growth. Typical raise $1.5M-$4M.\n- **Series A**: a working engine. Repeatable acquisition, real retention, and a\n  metric that scales (often ~$1M+ ARR for SaaS, with strong growth\u002Fretention).\n  Typical raise $6M-$15M.\n\nIf the evidence straddles two stages, you are at the lower one. Investors price\nthe floor of your story, not the ceiling.\n\n## Size the raise from the milestone, not the market\n\nDo not raise \"as much as you can.\" Raise the amount that buys the *next\nfundable milestone* plus margin:\n\n1. Name the milestone the next round requires (e.g. \"$1M ARR at 120% NRR\").\n2. Estimate monthly burn to get there and the months it takes.\n3. Raise milestone-cost x 1.5 (18-24 months of runway, never under 12).\n4. Sanity-check dilution: a healthy round sells 15-25%. If your target amount\n   forces >25% at a realistic valuation, the amount is too big or the valuation\n   too low - fix one.\n\n## Valuation envelope\n\nTriangulate, never anchor on a single hope:\n\n- **Comparables**: what companies with your traction raised recently, in your\n  geography and sector.\n- **Dilution math**: amount ÷ target dilution = post-money. ($2M for 20% =>\n  $10M post.)\n- **Instrument**: pre-seed\u002Fseed usually a SAFE with a valuation cap; priced\n  rounds start at seed\u002FA. Pair with [[safe-vs-priced-round]].\n\nThe number you can *defend* beats the number you can *dream*. An overpriced\nround you barely fill creates a down-round trap next time.\n\n## Should you raise at all?\n\nPush back before pulling forward. Don't raise if: the milestone is reachable on\nrevenue, the story has no proof and no clock, or dilution buys less than a clear\nstep-change. Bootstrapping a quarter to add proof often beats raising weak.\n\n## Anti-patterns\n\n- Pricing on TAM instead of traction.\n- A round so large it sets a Series A bar you cannot clear in 24 months.\n- Raising on \"everyone is raising\" with no milestone to point the cash at.\n\n## Deliverable\n\nA one-page raise thesis: stage (with the evidence that fixes it), amount, the\nnamed milestone it funds, months of runway, target dilution, and a defensible\nvaluation range with its comparables. Hand this to [[fundraise-readiness-audit]]\nbefore going out.\n",{"name":5,"description":7},"main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Ffundraising-stage-selector",3,"https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills","https:\u002F\u002Fskillme.dev","https:\u002F\u002Fgithub.com\u002FSkillMedev","MCP-native catalog of Claude Agent Skills. Browse, recommend, install, and auto-apply skills in chat. Open source, every skill free and clonable on GitHub.","2026-10-14 03:19:31",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add SkillMedev\u002Fskills --skill fundraising-stage-selector",{"tool":39,"command":40},"bunx","bunx skills add SkillMedev\u002Fskills --skill fundraising-stage-selector",{"tool":42,"command":43},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill fundraising-stage-selector","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ffundraising-stage-selector\u002FSKILL.md",true,[],[48,58,65,72,79,86],{"skillNo":49,"name":50,"nameZh":51,"description":52,"descriptionZh":53,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":57},"01M75271B256DF3FX2VG5VRYEE","zone-2-cardio-plan","有氧运动计划","Use when someone asks to build a steady-state cardio plan, train an aerobic base or Zone 2, structure easy or endurance weekly cardio, train by heart-rate zones, or improve resting heart rate, VO2, or endurance. Builds a heart-rate-zone aerobic training block with session structure, modality choice, and progression. General fitness guidance, not medical advice. Do NOT use to design a strength or lifting program (use Strength Training Plan), high-intensity interval conditioning, HIIT, or circuits (use Conditioning & HIIT Program), or a mobility\u002Fflexibility routine (use Mobility Routine).","当有人要求制定稳态有氧训练计划、进行有氧基础训练或达到第二区间、安排轻松或耐力型的每周有氧训练、按心率区间训练，或提高静息心率、最大摄氧量或耐力时，可以使用此方案。该方案构建了一个包含训练计划结构、训练方式选择和进度安排的心率区间有氧训练模块。本方案仅提供一般健身指导，不构成医疗建议。请勿用于设计力量或举重训练计划（请使用力量训练计划）、高强度间歇训练 (HIIT) 或循环训练（请使用体能训练和 HIIT 计划），或灵活性\u002F柔韧性训练（请使用灵活性训练计划）。","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzone-2-cardio-plan\u002FSKILL.md",[],[],"2026-11-11 18:27:18",{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":57},"01M7526VP1QBBKYBE17S1WR86Y","youtube-script-writer","Writes retention-engineered long-form YouTube scripts on a hook\u002Fbody\u002Fpayoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says \"script my next video\", \"my retention graph dies at the start\", \"tighten this draft\", or \"outline a video on X\". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-writer\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":57},"01M7526P2T0WKMHDXS4Q58237T","win-back-campaign","Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says \"our users went quiet\", \"design a win-back campaign\", \"how do I re-engage lapsed customers\", \"should we email people who haven't logged in for months\", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwin-back-campaign\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":57},"01M7526HF2RCDJ50P93WRZRHVV","wikipedia-style","Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks \"write this like a Wikipedia article\", \"draft a Wikipedia page for this company or person\", \"make this neutral and encyclopedic\", or \"why does my article draft keep getting rejected\". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwikipedia-style\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":57},"01M7526D43CTGRKGKNQ2GB0KVX","whitepapers","Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks \"write a whitepaper on this topic\", \"turn our research into a lead-gen asset\", \"make this credible enough for executives\", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwhitepapers\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":57},"01M75268423Y3K50SY5WC2NX2G","white-space-analysis","Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks \"where are the gaps in this market\", \"what's underserved here\", \"where should we play next\", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwhite-space-analysis\u002FSKILL.md",[],[]]