[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M750X8AP5SWYXWH7K1BRC9QQ":3,"skill-same:01M750X8AP5SWYXWH7K1BRC9QQ":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},"01M750X8AP5SWYXWH7K1BRC9QQ","launch-email-sequence",null,"Builds the open-cart email launch for a paid course - a 2-3 week pre-launch runway that seeds the problem, a day-by-day cart-open sequence of 6-8 emails over 5-7 days, honest deadline mechanics for the last-48-hours surge, and clicker\u002Fnon-opener segmentation. Use when a creator says \"write my launch emails\", \"plan my open cart sequence\", \"how many emails should I send during launch\", or \"how do I close the cart without fake scarcity\". Do NOT use for always-on welcome or nurture automations - use email-drip-builder instead - or for the regular newsletter between launches - use email-newsletter-pro instead.","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\u002Flaunch-email-sequence\u002FSKILL.md",[],[],"2026-11-11 18:11:01",false,"---\nname: launch-email-sequence\ndescription: Builds the open-cart email launch for a paid course - a 2-3 week pre-launch runway that seeds the problem, a day-by-day cart-open sequence of 6-8 emails over 5-7 days, honest deadline mechanics for the last-48-hours surge, and clicker\u002Fnon-opener segmentation. Use when a creator says \"write my launch emails\", \"plan my open cart sequence\", \"how many emails should I send during launch\", or \"how do I close the cart without fake scarcity\". Do NOT use for always-on welcome or nurture automations - use email-drip-builder instead - or for the regular newsletter between launches - use email-newsletter-pro instead.\n---\n\n# Launch Email Sequence\n\nAn open-cart launch lives or dies on two things most creators get backward: the selling happens mostly before the cart opens, and 40 to 50 percent of sales land in the last 48 hours no matter how good the early emails are. Creators who skip the runway launch to a cold list, and creators who go quiet near the deadline - afraid of \"too many emails\" - leave half the revenue unsent. This skill builds both halves: the 2-3 week runway that seeds the problem, and the day-by-day cart sequence that serves the deadline instead of faking one.\n\nThis skill runs after course-outline-architect (the transformation statement is the campaign's spine) and in lockstep with course-sales-page - every email quotes that page's promise, value stack, and guarantee word-for-word, because a mismatch between email and page is where trust dies at the moment of purchase.\n\nWorked example throughout: Dana, 8,000-subscriber list, launching \"Notion OS for Consultants\" at $297.\n\n## Operating procedure\n\n### Step 1: Collect the inputs\n\n1. List size, recent open and click rates. Label estimates as estimates.\n2. The transformation statement and module milestones from course-outline-architect.\n3. The sales page URL, value stack, and guarantee wording from course-sales-page.\n4. Cart window (default 6 days) and the real reason the deadline exists (Step 5 requires one).\n5. Proof assets: results, screenshots, early-student wins.\n\nSet expectations with the math: a well-run launch to a warm list converts 1 to 2 percent of the list. Dana at 8,000 subscribers plans on roughly 120 sales at $297 - about $35,600 - and treats anything from 80 to 160 as normal variance, not success or failure.\n\n### Step 2: Build the pre-launch runway (2-3 weeks, no selling)\n\nThree weekly value emails (or two weeks if the list is very warm) that make the problem vivid and the mechanism credible before anything is for sale. Each teaches something genuinely useful and seeds one launch theme:\n\n- Runway 1 - name the problem. Dana: \"The 5-hour tax: where a consultant's week actually goes.\" Teaches a time audit; seeds the before state.\n- Runway 2 - shift the belief. \"Why another productivity app won't fix it (and what will).\" Teaches that tools without a system fail; seeds the mechanism.\n- Runway 3 - show the after + open loop. \"Inside the system that onboards a client in under a day.\" A real walkthrough; ends with \"next week I'm opening something for you.\"\n\nReplies to runway emails are the objection mine for the cart emails and for course-sales-page's FAQ. Read every one.\n\n### Step 3: Write the cart-open sequence - 6-8 emails over 5-7 days\n\nDana runs 7 emails over a 6-day window (Tuesday open, Sunday midnight close). The day-by-day spine, with Dana's subject lines:\n\n```\nDay 1  OPEN        \"Doors open: Notion OS for Consultants\"\n       The full offer: transformation, stack ($1,688 value, $297),\n       30-day action-based guarantee, deadline stated plainly.\nDay 2  PROOF       \"How Priya cut client onboarding from 3 days to 4 hours\"\n       One story told end to end: before, the system, the numbers after.\nDay 3  OBJECTIONS  \"But I'm not a Notion person\"\n       Dismantle the top two objections (skill, time). Cite the 5-12\n       minute lessons and the 20-minute module-1 quick win.\nDay 4  FAQ         \"Your questions about Notion OS, answered\"\n       Real questions from runway replies, answered honestly -\n       including who should NOT buy.\nDay 5  VALUE\u002FBONUS \"The 12 templates alone are worth the price\"\n       Spotlight one stack element deeply. Deadline reminder.\nDay 6am CLOSE 1    \"Closes tonight: last call for Notion OS\"\n       Recap offer + guarantee. Why the deadline is real.\nDay 6pm CLOSE 2    \"3 hours left (then the bonuses go away)\"\n       Short, plain, one link. Sent 3-4 hours before close.\n```\n\nEvery email: one idea, one call to action, the same URL. Stack and guarantee wording identical to course-sales-page.\n\n### Step 4: Serve the last 48 hours honestly\n\nExpect 40 to 50 percent of sales in the final 48 hours - for Dana, roughly 50-60 of her ~120 sales on days 5 and 6. This is deadline behavior, not failure of the early emails, so plan for it instead of panicking into hype:\n\n- Schedule 3 of the 7 emails inside the final 48 hours. Silence here is the single most expensive mistake in launching.\n- The deadline must be mechanically real: the price rises, the bonuses expire, or the cart actually closes. Dana's: the automations mini-course and the templates' rebrand license leave the offer at close, and the cart closes until the next cohort.\n- Never fabricate scarcity - no fake countdown resets, no \"3 spots left\" on a digital product with infinite spots. One discovered lie forfeits the list's trust for every future launch.\n- Close-day emails are short and calm. Urgency comes from the clock, not from exclamation marks.\n\n### Step 5: Segment - clickers vs non-openers\n\nFrom day 3 onward, split:\n\n- Clicked but didn't buy (hottest segment): they get the objection, FAQ, and both close emails; on close day, optionally a personal-toned \"anything holding you back? reply and ask me\" email.\n- Opened, never clicked: standard sequence continues.\n- Didn't open the last 3 emails: resend day 1 and day 6 with new subject lines only (\"Doors open\" becomes \"This is what I've been building for you\"). Do not resend to people who opened - that trains ignoring.\n- Purchased: remove from the launch flow immediately and hand to community-engagement-playbook's onboarding ritual. Nothing burns goodwill like selling someone what they bought yesterday.\n\n### Step 6: Close out and hand off\n\nWithin 48 hours of close: record sales by day (verify the last-48-hours share), revenue, unsubscribes (under 1 percent of list across a launch is healthy; over 2 percent means the runway was too thin for the volume), and the top three objections that survived. Buyers flow to community-engagement-playbook. If the next launch should be webinar-driven, take the numbers to webinar-funnel-builder; to convert this campaign into an always-on funnel, email-drip-builder.\n\n## Deliverable\n\nThe full campaign calendar: 2-3 runway emails and 6-8 cart emails, each with subject line, one-sentence job, send day and time, the segmentation rules from day 3 onward, the stated real deadline mechanic, and the close-out metric sheet - with offer wording matched to course-sales-page.\n\n## Do NOT\n\n- Do not skip the runway and open the cart cold. The runway is where the sale actually happens; the cart emails just collect it.\n- Do not go quiet in the final 48 hours to avoid \"annoying people.\" That is where 40-50 percent of revenue lives; the unsubscribes are people who were never buying.\n- Do not fake scarcity or reset deadlines. One honest deadline outsells a decade of countdown timers that lie.\n- Do not put three ideas and three links in one email. One idea, one CTA, every time.\n- Do not keep emailing buyers the launch sequence. Purchase removes them instantly.\n- Do not let email copy drift from the sales page - quote the promise, the $1,688-for-$297 stack, and the guarantee identically.\n\n## Quality bar\n\n- Runway of 2-3 genuinely useful emails precedes the cart; each seeds one launch theme.\n- 6-8 cart emails over 5-7 days, covering open, proof, objections, FAQ, and a two-email close, with 3 emails inside the final 48 hours.\n- The deadline names its real mechanism; no manufactured scarcity anywhere.\n- Segmentation rules written down: clickers, non-openers (subject-line-only resends), and buyer removal.\n- Projected sales stated up front from the 1-2 percent benchmark, so the result is judged against a number set before launch.\n\n## Escalation and routing\n\nEvergreen or trigger-based automation: email-drip-builder. The between-launches newsletter that keeps the list warm for the next runway: email-newsletter-pro. A live-webinar pitch layer on top of this sequence: webinar-funnel-builder. Email marketing is regulated (CAN-SPAM, GDPR and kin) - keep working unsubscribe links and honest subject lines; if list practices are in doubt, get compliance advice. This is not legal advice.\n","# Launch Email Sequence\n\nAn open-cart launch lives or dies on two things most creators get backward: the selling happens mostly before the cart opens, and 40 to 50 percent of sales land in the last 48 hours no matter how good the early emails are. Creators who skip the runway launch to a cold list, and creators who go quiet near the deadline - afraid of \"too many emails\" - leave half the revenue unsent. This skill builds both halves: the 2-3 week runway that seeds the problem, and the day-by-day cart sequence that serves the deadline instead of faking one.\n\nThis skill runs after course-outline-architect (the transformation statement is the campaign's spine) and in lockstep with course-sales-page - every email quotes that page's promise, value stack, and guarantee word-for-word, because a mismatch between email and page is where trust dies at the moment of purchase.\n\nWorked example throughout: Dana, 8,000-subscriber list, launching \"Notion OS for Consultants\" at $297.\n\n## Operating procedure\n\n### Step 1: Collect the inputs\n\n1. List size, recent open and click rates. Label estimates as estimates.\n2. The transformation statement and module milestones from course-outline-architect.\n3. The sales page URL, value stack, and guarantee wording from course-sales-page.\n4. Cart window (default 6 days) and the real reason the deadline exists (Step 5 requires one).\n5. Proof assets: results, screenshots, early-student wins.\n\nSet expectations with the math: a well-run launch to a warm list converts 1 to 2 percent of the list. Dana at 8,000 subscribers plans on roughly 120 sales at $297 - about $35,600 - and treats anything from 80 to 160 as normal variance, not success or failure.\n\n### Step 2: Build the pre-launch runway (2-3 weeks, no selling)\n\nThree weekly value emails (or two weeks if the list is very warm) that make the problem vivid and the mechanism credible before anything is for sale. Each teaches something genuinely useful and seeds one launch theme:\n\n- Runway 1 - name the problem. Dana: \"The 5-hour tax: where a consultant's week actually goes.\" Teaches a time audit; seeds the before state.\n- Runway 2 - shift the belief. \"Why another productivity app won't fix it (and what will).\" Teaches that tools without a system fail; seeds the mechanism.\n- Runway 3 - show the after + open loop. \"Inside the system that onboards a client in under a day.\" A real walkthrough; ends with \"next week I'm opening something for you.\"\n\nReplies to runway emails are the objection mine for the cart emails and for course-sales-page's FAQ. Read every one.\n\n### Step 3: Write the cart-open sequence - 6-8 emails over 5-7 days\n\nDana runs 7 emails over a 6-day window (Tuesday open, Sunday midnight close). The day-by-day spine, with Dana's subject lines:\n\n```\nDay 1  OPEN        \"Doors open: Notion OS for Consultants\"\n       The full offer: transformation, stack ($1,688 value, $297),\n       30-day action-based guarantee, deadline stated plainly.\nDay 2  PROOF       \"How Priya cut client onboarding from 3 days to 4 hours\"\n       One story told end to end: before, the system, the numbers after.\nDay 3  OBJECTIONS  \"But I'm not a Notion person\"\n       Dismantle the top two objections (skill, time). Cite the 5-12\n       minute lessons and the 20-minute module-1 quick win.\nDay 4  FAQ         \"Your questions about Notion OS, answered\"\n       Real questions from runway replies, answered honestly -\n       including who should NOT buy.\nDay 5  VALUE\u002FBONUS \"The 12 templates alone are worth the price\"\n       Spotlight one stack element deeply. Deadline reminder.\nDay 6am CLOSE 1    \"Closes tonight: last call for Notion OS\"\n       Recap offer + guarantee. Why the deadline is real.\nDay 6pm CLOSE 2    \"3 hours left (then the bonuses go away)\"\n       Short, plain, one link. Sent 3-4 hours before close.\n```\n\nEvery email: one idea, one call to action, the same URL. Stack and guarantee wording identical to course-sales-page.\n\n### Step 4: Serve the last 48 hours honestly\n\nExpect 40 to 50 percent of sales in the final 48 hours - for Dana, roughly 50-60 of her ~120 sales on days 5 and 6. This is deadline behavior, not failure of the early emails, so plan for it instead of panicking into hype:\n\n- Schedule 3 of the 7 emails inside the final 48 hours. Silence here is the single most expensive mistake in launching.\n- The deadline must be mechanically real: the price rises, the bonuses expire, or the cart actually closes. Dana's: the automations mini-course and the templates' rebrand license leave the offer at close, and the cart closes until the next cohort.\n- Never fabricate scarcity - no fake countdown resets, no \"3 spots left\" on a digital product with infinite spots. One discovered lie forfeits the list's trust for every future launch.\n- Close-day emails are short and calm. Urgency comes from the clock, not from exclamation marks.\n\n### Step 5: Segment - clickers vs non-openers\n\nFrom day 3 onward, split:\n\n- Clicked but didn't buy (hottest segment): they get the objection, FAQ, and both close emails; on close day, optionally a personal-toned \"anything holding you back? reply and ask me\" email.\n- Opened, never clicked: standard sequence continues.\n- Didn't open the last 3 emails: resend day 1 and day 6 with new subject lines only (\"Doors open\" becomes \"This is what I've been building for you\"). Do not resend to people who opened - that trains ignoring.\n- Purchased: remove from the launch flow immediately and hand to community-engagement-playbook's onboarding ritual. Nothing burns goodwill like selling someone what they bought yesterday.\n\n### Step 6: Close out and hand off\n\nWithin 48 hours of close: record sales by day (verify the last-48-hours share), revenue, unsubscribes (under 1 percent of list across a launch is healthy; over 2 percent means the runway was too thin for the volume), and the top three objections that survived. Buyers flow to community-engagement-playbook. If the next launch should be webinar-driven, take the numbers to webinar-funnel-builder; to convert this campaign into an always-on funnel, email-drip-builder.\n\n## Deliverable\n\nThe full campaign calendar: 2-3 runway emails and 6-8 cart emails, each with subject line, one-sentence job, send day and time, the segmentation rules from day 3 onward, the stated real deadline mechanic, and the close-out metric sheet - with offer wording matched to course-sales-page.\n\n## Do NOT\n\n- Do not skip the runway and open the cart cold. The runway is where the sale actually happens; the cart emails just collect it.\n- Do not go quiet in the final 48 hours to avoid \"annoying people.\" That is where 40-50 percent of revenue lives; the unsubscribes are people who were never buying.\n- Do not fake scarcity or reset deadlines. One honest deadline outsells a decade of countdown timers that lie.\n- Do not put three ideas and three links in one email. One idea, one CTA, every time.\n- Do not keep emailing buyers the launch sequence. Purchase removes them instantly.\n- Do not let email copy drift from the sales page - quote the promise, the $1,688-for-$297 stack, and the guarantee identically.\n\n## Quality bar\n\n- Runway of 2-3 genuinely useful emails precedes the cart; each seeds one launch theme.\n- 6-8 cart emails over 5-7 days, covering open, proof, objections, FAQ, and a two-email close, with 3 emails inside the final 48 hours.\n- The deadline names its real mechanism; no manufactured scarcity anywhere.\n- Segmentation rules written down: clickers, non-openers (subject-line-only resends), and buyer removal.\n- Projected sales stated up front from the 1-2 percent benchmark, so the result is judged against a number set before launch.\n\n## Escalation and routing\n\nEvergreen or trigger-based automation: email-drip-builder. The between-launches newsletter that keeps the list warm for the next runway: email-newsletter-pro. A live-webinar pitch layer on top of this sequence: webinar-funnel-builder. Email marketing is regulated (CAN-SPAM, GDPR and kin) - keep working unsubscribe links and honest subject lines; if list practices are in doubt, get compliance advice. This is not legal advice.\n",{"name":5,"description":7},"main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Flaunch-email-sequence",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 launch-email-sequence",{"tool":39,"command":40},"bunx","bunx skills add SkillMedev\u002Fskills --skill launch-email-sequence",{"tool":42,"command":43},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill launch-email-sequence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Flaunch-email-sequence\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",[],[]]