[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7504CS2D5XG2T42GRKXV48Z":3,"skill-same:01M7504CS2D5XG2T42GRKXV48Z":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},"01M7504CS2D5XG2T42GRKXV48Z","community-engagement-playbook",null,"Builds the student community system for a paid course - platform choice by where students already are, an introduce-yourself onboarding ritual, a weekly cadence of office hours, wins threads, and accountability checks, a hard creator-time budget, and scheduled testimonial-harvest moments. Use when a course creator says \"my students aren't finishing the course\", \"should I use Circle or Slack or Discord\", \"how do I keep my community active without it eating my week\", or \"how do I get testimonials from students\". Do NOT use for running the testimonial conversation itself - use testimonial-capture-interview 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\u002Fcommunity-engagement-playbook\u002FSKILL.md",[],[],"2026-11-11 17:59:50",false,"---\nname: community-engagement-playbook\ndescription: Builds the student community system for a paid course - platform choice by where students already are, an introduce-yourself onboarding ritual, a weekly cadence of office hours, wins threads, and accountability checks, a hard creator-time budget, and scheduled testimonial-harvest moments. Use when a course creator says \"my students aren't finishing the course\", \"should I use Circle or Slack or Discord\", \"how do I keep my community active without it eating my week\", or \"how do I get testimonials from students\". Do NOT use for running the testimonial conversation itself - use testimonial-capture-interview instead.\n---\n\n# Community Engagement Playbook\n\nA course community exists for exactly two outputs: completion and testimonials. Students who feel seen finish, finished students get results, and results become the proof that sells the next cohort. The costly mistake is treating community as a feature to bolt on - an empty Slack nobody posts in signals a dead course louder than no community at all, and an unbudgeted community quietly consumes the creator's production time until the next launch slips.\n\nThis skill runs after launch-email-sequence hands over the buyers, operates against the completion target set by course-outline-architect, and feeds its testimonial harvest back to course-sales-page's proof section. That loop - community to testimonials to sales page - is what makes the second launch outperform the first.\n\nWorked example throughout: Dana, who just closed the \"Notion OS for Consultants\" launch ($297) with roughly 120 students from her 8,000-subscriber list, budgeting 5 hours a week for community.\n\n## Operating procedure\n\n### Step 1: Collect the inputs\n\n1. Student count and where the audience already hangs out (check where they replied from during the launch; ask 5 buyers directly if unknown).\n2. The course's quick-win moment and module milestones from course-outline-architect.\n3. The creator's honest weekly hours available. Default and hard cap: 5.\n4. Course length and the completion target - this pack designs for 35 percent or better against the 10 to 15 percent industry average.\n\n### Step 2: Choose the platform - where students already are beats features\n\nRank candidates by one question: which platform are these students already opening daily? A feature-rich community platform they must remember to visit loses to a mediocre one already in their dock. Decision rules:\n\n- Students live in Slack for work (Dana's consultants do): Slack or a Slack-adjacent tool wins, features be damned.\n- Audience is creators\u002Fgamers already on Discord: Discord.\n- Buying a dedicated tool (Circle, Skool, and kin) is right only when the cohort is large enough to sustain its own gravity - under roughly 50 active students, a dedicated platform usually reads as empty.\n- Never more than one platform. Splitting 120 students across two places produces two ghost towns.\n\nDana picks Slack: her consultants are in it all day, and an empty-feeling Circle space would cost more momentum than Slack's weaker course features.\n\n### Step 3: Run the onboarding ritual\n\nThe first 48 hours after purchase decide whether a student ever posts. Buyers arrive from launch-email-sequence into: a welcome email, an introduce-yourself prompt, and a first-action nudge pointing at the module-1 quick win (Dana's: the working dashboard in 20 minutes).\n\nThe introduce-yourself template - structured prompts get 3-4x the responses of \"say hi!\":\n\n```\nWelcome! Copy this, fill it in, post it in #introductions:\n\n1. Name + what kind of consulting you do\n2. Your current setup, honestly (how many tools? paper? chaos?)\n3. The ONE thing you want working by the end of this course\n4. Something you're good at that has nothing to do with work\n\nDana's example:\n1. Dana - productivity consulting for solo consultants\n2. Recovering 6-tool juggler: Notion, Trello, Docs, Sheets, Calendly, Airtable\n3. Client onboarding in under a day, every time\n4. I can identify most birds in New England by song\n```\n\nThe creator (or a student moderator, later) replies to every introduction within 24 hours during launch month. Question 4 is not filler - it is what other students reply to, and peer replies, not creator replies, are what make a community self-sustaining.\n\n### Step 4: Install the weekly cadence\n\nThree recurring beats, same day and time every week, so students stop wondering whether anything is happening:\n\n- **Office hours** - 45 minutes live, weekly during the cohort's first 8 weeks, biweekly after. Collect questions in a thread beforehand so silence can't kill the session; record and post every one.\n- **Wins thread** - Monday: \"What's one thing that worked this week - however small?\" The creator seeds it with a student win spotted during the week. This thread is also the testimonial radar (Step 6).\n- **Accountability check** - Thursday: \"Which lesson are you on, and what's the one action you'll finish by Sunday?\" This maps directly to the one-action-per-lesson design from course-outline-architect, and its silent students are the churn early-warning list.\n\n### Step 5: Enforce the creator-time budget - 5 hours a week, capped\n\nCommunity effort past about 5 hours a week cannibalizes course improvement and the next launch. Dana's allocation:\n\n```\nOffice hours (run + prep)         1.5 hrs\nReplies, batched 2x\u002Fday 30 min    1.0 hr   (never ambient all-day checking)\nCadence posts + win-spotting      1.0 hr\nTestimonial harvest + DMs         0.5 hr\nSlack (buffer \u002F member care)      1.0 hr\n                          Total   5.0 hrs\n```\n\nLeverage tactics, in deployment order: (1) batch replies to two windows a day - ambient checking is how 5 hours becomes 20; (2) turn every question answered twice into a pinned FAQ post; (3) at month two, invite 2-3 of the most active students to be moderators with a real perk (free next course, or a lifetime license); (4) let non-urgent threads sit 24 hours - peer answers appearing before creator answers is the health signal, not a failure.\n\n### Step 6: Harvest testimonials at the moments they occur\n\nTestimonials are perishable - enthusiasm peaks at the moment of a win and decays within days. Watch four harvest moments:\n\n1. The module-1 quick win (Dana's 20-minute dashboard) - first-impression quotes.\n2. The mid-course milestone (Dana's Module 4: a client portal live for a real client) - concrete-result quotes.\n3. Course completion - transformation-story quotes.\n4. Any unprompted wins-thread post with a number in it (\"saved 4 hours this week\") - the strongest of all.\n\nAt each moment, act within 48 hours: a short DM - \"That win you posted is exactly what future students need to hear. Up for a 15-minute chat about it?\" - then route the conversation itself to testimonial-capture-interview, which owns the questions, consent, and formats. Deliver finished testimonials to course-sales-page's proof section before the next launch. Target from a 120-student cohort: 10-15 usable testimonials, of which 3-5 carry specific numbers.\n\n## Deliverable\n\nA one-page community operating plan: the platform decision with its reasoning, the onboarding ritual with the introduce-yourself template, the three-beat weekly cadence with days and times, the 5-hour time budget with allocations and leverage tactics, and the four testimonial-harvest moments with the DM script and the testimonial-capture-interview handoff.\n\n## Do NOT\n\n- Do not pick a platform for its features over its ambient presence in students' lives. The best platform is the one already open.\n- Do not launch a community with no cadence and hope conversation emerges. Empty communities actively damage the course's perceived value.\n- Do not let community time float uncapped. Past 5 hours a week it is eating the next launch.\n- Do not answer every question instantly and forever. Creator omnipresence trains dependence and prevents the peer-to-peer culture that makes the community durable.\n- Do not wait until launch prep to ask for testimonials. Months-old enthusiasm produces vague praise; harvest within 48 hours of the win.\n- Do not run the testimonial interview ad hoc in DMs - route it to testimonial-capture-interview so consent and specifics are captured properly.\n\n## Quality bar\n\n- One platform, chosen by where students already are, with the reasoning written down.\n- Every new student gets the structured introduce-yourself prompt and a reply within 24 hours during launch month.\n- Three weekly beats scheduled at fixed times; office hours never cancelled silently.\n- The time budget totals 5 hours or less and names at least two leverage tactics in use.\n- All four harvest moments have an owner and the 48-hour DM rule; testimonials with numbers flow to course-sales-page before the next launch.\n- Completion is tracked against the 35 percent target, with the accountability thread as the early-warning system.\n\n## Escalation and routing\n\nThe testimonial conversation, consent, and formats: testimonial-capture-interview. Structural fixes when completion lags despite an active community (lessons too long, milestones unclear): course-outline-architect. Quizzes that give the accountability check teeth: quiz-generator. Turning community proof into the next campaign: course-sales-page and launch-email-sequence.\n","# Community Engagement Playbook\n\nA course community exists for exactly two outputs: completion and testimonials. Students who feel seen finish, finished students get results, and results become the proof that sells the next cohort. The costly mistake is treating community as a feature to bolt on - an empty Slack nobody posts in signals a dead course louder than no community at all, and an unbudgeted community quietly consumes the creator's production time until the next launch slips.\n\nThis skill runs after launch-email-sequence hands over the buyers, operates against the completion target set by course-outline-architect, and feeds its testimonial harvest back to course-sales-page's proof section. That loop - community to testimonials to sales page - is what makes the second launch outperform the first.\n\nWorked example throughout: Dana, who just closed the \"Notion OS for Consultants\" launch ($297) with roughly 120 students from her 8,000-subscriber list, budgeting 5 hours a week for community.\n\n## Operating procedure\n\n### Step 1: Collect the inputs\n\n1. Student count and where the audience already hangs out (check where they replied from during the launch; ask 5 buyers directly if unknown).\n2. The course's quick-win moment and module milestones from course-outline-architect.\n3. The creator's honest weekly hours available. Default and hard cap: 5.\n4. Course length and the completion target - this pack designs for 35 percent or better against the 10 to 15 percent industry average.\n\n### Step 2: Choose the platform - where students already are beats features\n\nRank candidates by one question: which platform are these students already opening daily? A feature-rich community platform they must remember to visit loses to a mediocre one already in their dock. Decision rules:\n\n- Students live in Slack for work (Dana's consultants do): Slack or a Slack-adjacent tool wins, features be damned.\n- Audience is creators\u002Fgamers already on Discord: Discord.\n- Buying a dedicated tool (Circle, Skool, and kin) is right only when the cohort is large enough to sustain its own gravity - under roughly 50 active students, a dedicated platform usually reads as empty.\n- Never more than one platform. Splitting 120 students across two places produces two ghost towns.\n\nDana picks Slack: her consultants are in it all day, and an empty-feeling Circle space would cost more momentum than Slack's weaker course features.\n\n### Step 3: Run the onboarding ritual\n\nThe first 48 hours after purchase decide whether a student ever posts. Buyers arrive from launch-email-sequence into: a welcome email, an introduce-yourself prompt, and a first-action nudge pointing at the module-1 quick win (Dana's: the working dashboard in 20 minutes).\n\nThe introduce-yourself template - structured prompts get 3-4x the responses of \"say hi!\":\n\n```\nWelcome! Copy this, fill it in, post it in #introductions:\n\n1. Name + what kind of consulting you do\n2. Your current setup, honestly (how many tools? paper? chaos?)\n3. The ONE thing you want working by the end of this course\n4. Something you're good at that has nothing to do with work\n\nDana's example:\n1. Dana - productivity consulting for solo consultants\n2. Recovering 6-tool juggler: Notion, Trello, Docs, Sheets, Calendly, Airtable\n3. Client onboarding in under a day, every time\n4. I can identify most birds in New England by song\n```\n\nThe creator (or a student moderator, later) replies to every introduction within 24 hours during launch month. Question 4 is not filler - it is what other students reply to, and peer replies, not creator replies, are what make a community self-sustaining.\n\n### Step 4: Install the weekly cadence\n\nThree recurring beats, same day and time every week, so students stop wondering whether anything is happening:\n\n- **Office hours** - 45 minutes live, weekly during the cohort's first 8 weeks, biweekly after. Collect questions in a thread beforehand so silence can't kill the session; record and post every one.\n- **Wins thread** - Monday: \"What's one thing that worked this week - however small?\" The creator seeds it with a student win spotted during the week. This thread is also the testimonial radar (Step 6).\n- **Accountability check** - Thursday: \"Which lesson are you on, and what's the one action you'll finish by Sunday?\" This maps directly to the one-action-per-lesson design from course-outline-architect, and its silent students are the churn early-warning list.\n\n### Step 5: Enforce the creator-time budget - 5 hours a week, capped\n\nCommunity effort past about 5 hours a week cannibalizes course improvement and the next launch. Dana's allocation:\n\n```\nOffice hours (run + prep)         1.5 hrs\nReplies, batched 2x\u002Fday 30 min    1.0 hr   (never ambient all-day checking)\nCadence posts + win-spotting      1.0 hr\nTestimonial harvest + DMs         0.5 hr\nSlack (buffer \u002F member care)      1.0 hr\n                          Total   5.0 hrs\n```\n\nLeverage tactics, in deployment order: (1) batch replies to two windows a day - ambient checking is how 5 hours becomes 20; (2) turn every question answered twice into a pinned FAQ post; (3) at month two, invite 2-3 of the most active students to be moderators with a real perk (free next course, or a lifetime license); (4) let non-urgent threads sit 24 hours - peer answers appearing before creator answers is the health signal, not a failure.\n\n### Step 6: Harvest testimonials at the moments they occur\n\nTestimonials are perishable - enthusiasm peaks at the moment of a win and decays within days. Watch four harvest moments:\n\n1. The module-1 quick win (Dana's 20-minute dashboard) - first-impression quotes.\n2. The mid-course milestone (Dana's Module 4: a client portal live for a real client) - concrete-result quotes.\n3. Course completion - transformation-story quotes.\n4. Any unprompted wins-thread post with a number in it (\"saved 4 hours this week\") - the strongest of all.\n\nAt each moment, act within 48 hours: a short DM - \"That win you posted is exactly what future students need to hear. Up for a 15-minute chat about it?\" - then route the conversation itself to testimonial-capture-interview, which owns the questions, consent, and formats. Deliver finished testimonials to course-sales-page's proof section before the next launch. Target from a 120-student cohort: 10-15 usable testimonials, of which 3-5 carry specific numbers.\n\n## Deliverable\n\nA one-page community operating plan: the platform decision with its reasoning, the onboarding ritual with the introduce-yourself template, the three-beat weekly cadence with days and times, the 5-hour time budget with allocations and leverage tactics, and the four testimonial-harvest moments with the DM script and the testimonial-capture-interview handoff.\n\n## Do NOT\n\n- Do not pick a platform for its features over its ambient presence in students' lives. The best platform is the one already open.\n- Do not launch a community with no cadence and hope conversation emerges. Empty communities actively damage the course's perceived value.\n- Do not let community time float uncapped. Past 5 hours a week it is eating the next launch.\n- Do not answer every question instantly and forever. Creator omnipresence trains dependence and prevents the peer-to-peer culture that makes the community durable.\n- Do not wait until launch prep to ask for testimonials. Months-old enthusiasm produces vague praise; harvest within 48 hours of the win.\n- Do not run the testimonial interview ad hoc in DMs - route it to testimonial-capture-interview so consent and specifics are captured properly.\n\n## Quality bar\n\n- One platform, chosen by where students already are, with the reasoning written down.\n- Every new student gets the structured introduce-yourself prompt and a reply within 24 hours during launch month.\n- Three weekly beats scheduled at fixed times; office hours never cancelled silently.\n- The time budget totals 5 hours or less and names at least two leverage tactics in use.\n- All four harvest moments have an owner and the 48-hour DM rule; testimonials with numbers flow to course-sales-page before the next launch.\n- Completion is tracked against the 35 percent target, with the accountability thread as the early-warning system.\n\n## Escalation and routing\n\nThe testimonial conversation, consent, and formats: testimonial-capture-interview. Structural fixes when completion lags despite an active community (lessons too long, milestones unclear): course-outline-architect. Quizzes that give the accountability check teeth: quiz-generator. Turning community proof into the next campaign: course-sales-page and launch-email-sequence.\n",{"name":5,"description":7},"main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Fcommunity-engagement-playbook",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 community-engagement-playbook",{"tool":39,"command":40},"bunx","bunx skills add SkillMedev\u002Fskills --skill community-engagement-playbook",{"tool":42,"command":43},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill community-engagement-playbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity-engagement-playbook\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",[],[]]