[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M750ZB05HVTEN876G0B7DRM8":3,"skill-same:01M750ZB05HVTEN876G0B7DRM8":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},"01M750ZB05HVTEN876G0B7DRM8","local-referral-engine",null,"Builds referral flow and local partnerships for a local service business - the ask-after-five-star-moment rule, two-sided referral incentive design, complementary-trade partnerships, and neighborhood-domination tactics like job-site signage and just-worked-on-your-street cards. Use when an owner asks \"how do I get more word-of-mouth\", \"should I pay customers for referrals\", \"how do I partner with other trades\", or \"how do I get more jobs in the same neighborhood\". Do NOT use for gym referral and affiliate programs - use referral-and-affiliate-system instead. Do NOT use for formal B2B partnership deals - use partnership-strategy 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\u002Flocal-referral-engine\u002FSKILL.md",[],[],"2026-11-11 18:11:01",false,"---\nname: local-referral-engine\ndescription: Builds referral flow and local partnerships for a local service business - the ask-after-five-star-moment rule, two-sided referral incentive design, complementary-trade partnerships, and neighborhood-domination tactics like job-site signage and just-worked-on-your-street cards. Use when an owner asks \"how do I get more word-of-mouth\", \"should I pay customers for referrals\", \"how do I partner with other trades\", or \"how do I get more jobs in the same neighborhood\". Do NOT use for gym referral and affiliate programs - use referral-and-affiliate-system instead. Do NOT use for formal B2B partnership deals - use partnership-strategy instead.\n---\n\n# Local Referral Engine\n\nReferrals are the best customers a local service business gets: near-zero\nacquisition cost, pre-sold trust, and higher close rates than any paid\nchannel. The costly mistake this skill prevents is leaving referrals passive -\n\"we get word of mouth\" - instead of building the three systems that\nmanufacture them: a timed ask, a two-sided incentive, and a partner network.\nRun local-unit-economics first to see the prize: Summit Plumbing (4 techs,\n$450 average ticket, $75,000 a month) pays about $119 to acquire a paid-lead\ncustomer, so every referred customer is roughly $119 of margin that paid\nchannels never touch.\n\n## Operating procedure\n\n### Step 1: Ask at the five-star moment - and only then\n\nThe ask-after-five-star-moment rule: the referral ask fires when a customer\nhas just expressed delight - a five-star review posted (review-engine detects\nexactly this), an effusive thank-you at job completion, a \"you saved us\"\ntext. Never ask a merely-satisfied customer; a referral is the customer\nspending social capital with a friend, and they only spend it at an\nemotional peak. This is the concrete handoff from review-engine: every\nfive-star review triggers the referral SMS within a day or two.\n\n```\nReferral ask SMS (1-2 days after a five-star moment):\n\"Hi [FILL: name], [FILL: owner\u002Ftech] from Summit Plumbing - thanks\nagain for the kind words! Small favor: most of our work comes from\nneighbors recommending us. If a friend ever needs a plumber, send\nthem our way - and as a thank-you, you'll both get $50 off your\nnext service. Just have them mention your name.\"\n```\n\n### Step 2: Design the incentive two-sided\n\nTwo-sided beats one-sided: reward the referrer and discount the friend. A\none-sided reward makes the recommendation feel like a commission (\"is he\nrecommending them for the fifty bucks?\"); two-sided lets the referrer open\nwith a gift (\"use these guys, you'll get $50 off\"), which preserves the\nsocial framing that makes referrals work. Summit's design: $50 service\ncredit to the referrer, $50 off the friend's first job. Against a $450\naverage ticket at 55 percent margin, a $100 total incentive still lands the\ncustomer far below the $119 paid CAC - and the referred customer closes\nbetter and refers onward. Size the incentive at roughly 10-25 percent of\naverage ticket total across both sides. Keep redemption dead simple: \"have\nthem mention your name,\" tracked in a spreadsheet - no codes, no portal.\n\n### Step 3: Build complementary-trade partnerships\n\nTrades see each other's future customers constantly: the electrician spots\nthe corroded water heater, the GC needs a plumber on every remodel, and the\nplumber sees breaker panels. Build a bench of 3-5 non-competing partners -\nfor Summit: an electrician, a GC, an HVAC company, a restoration company.\nRules that keep it alive:\n\n- Reciprocity is the currency. Track referrals given and received per\n  partner each quarter; a partner who receives five and sends zero gets a\n  friendly conversation, then gets dropped.\n- Refer only businesses you would let into your own house - their bad job\n  becomes your bad review.\n- Money between trades: a flat thank-you referral fee ($25-50) or pure\n  reciprocity both work; keep it simple and consistent. Check local\n  licensing rules - some jurisdictions and trades restrict paid referrals.\n- Make the intro warm: the partner texts the customer your name, not just\n  the reverse. A warm handoff closes at multiples of a cold mention.\n- These relationships also earn the real local links local-seo-playbook\n  wants - a \"trusted partners\" mention on each other's sites is prominence\n  that money cannot buy cleanly.\n\n### Step 4: Dominate the neighborhood around every job\n\nEvery job is a beachhead; density is the goal, because five jobs on one\nstreet cuts drive time and makes the brand ambient.\n\n- Job-site signage: a small yard sign during multi-day jobs, with\n  permission (\"mind if we leave this up while we work?\"). A truck wrapped\n  with the name and number is signage that never comes down.\n- \"We just worked on your street\" cards: after each job, the tech drops\n  cards at the 10-15 nearest doors. Script on the card: \"We just fixed a\n  water heater for one of your neighbors on [FILL: street]. If your\n  plumbing ever acts up, we're already in the neighborhood - $25 off for\n  [FILL: street] residents this month.\" Neighbor proof plus a local-only\n  offer outperforms any cold flyer.\n- Neighborhood groups: when a customer offers to post in the neighborhood\n  Facebook group or on Nextdoor, say yes and make it easy - a\n  recommendation there is a referral to three hundred neighbors at once.\n\n### Step 5: Track referral share monthly\n\nLog every new customer's source at booking (\"How did you hear about us?\" is\nmandatory, not optional). Track referral plus partner share of new\ncustomers monthly and feed the repeat\u002Freferral rate into\nlocal-unit-economics. Healthy mature share for a residential trade: 30-50\npercent of new customers from referral, partner, and neighborhood sources.\nBelow 15 percent after six months of running this engine means the asks are\nnot actually firing - audit whether the five-star trigger is being executed,\nnot whether customers \"just don't refer.\"\n\n## Inputs to elicit\n\nCollect: current referral share of new customers (label the usual guess as\na guess - booking-source logging is step zero), average ticket and margin\n(from local-unit-economics), review flow (is review-engine live - this\nskill's trigger depends on it), candidate partner trades already known, and\njobs per month per neighborhood. Defaults: $50\u002F$50 two-sided credit, cards\nat 10-15 doors per job, 3-5 partners.\n\n## Concrete thresholds\n\n- Ask timing: within 1-2 days of a five-star moment; never cold, never in\n  the same message as the review ask (one ask per message, always).\n- Incentive: two-sided, totaling 10-25 percent of average ticket; credits\n  beat cash for repeat-visit trades because they guarantee a next booking.\n- Partners: 3-5 active; reciprocity reviewed quarterly; give-receive\n  imbalance beyond 3:1 for two quarters means drop or renegotiate.\n- Neighborhood cards: 10-15 doors per completed job, same day.\n- Referral share target: 30-50 percent of new customers within a year;\n  under 15 percent after six months means the trigger is not firing.\n\n## Worked artifact: Summit's referral math\n\n```\nProgram: $50 credit to referrer + $50 off friend's first job\nFive-star moments\u002Fmo (from review-engine, at its 12\u002Fmo target\n  plus in-person delight):            ~18 asks sent\nReferrals landed (25% of asks):       ~4-5 new customers\u002Fmo\nPartner bench (electrician, GC, HVAC, restoration):\n  referrals received:                 ~4\u002Fmo   given: ~5\u002Fmo (healthy)\nStreet cards: ~55 jobs\u002Fmo x 12 doors = ~660 cards -> ~3 jobs\u002Fmo\nNew referred\u002Fpartner\u002Fneighbor customers: ~11-12\u002Fmo of ~35 new\n  customers = ~32% referral share  (target band: 30-50%)\nCost check: ~$100 incentive per referred customer vs $119 paid CAC,\nwith a customer who closes better and refers onward. Verdict: scale.\n```\n\n## Deliverable\n\nA referral operating system on one page: the five-star-trigger ask SMS with\nfields filled, the two-sided incentive spec and its tracking sheet, a\npartner bench list with the reciprocity ledger, the street-card copy and\ndrop routine, and the monthly referral-share line that feeds\nlocal-unit-economics.\n\n## Do NOT\n\n- Do not ask merely-satisfied customers for referrals; a lukewarm referral\n  spends trust the customer does not have, and the silence teaches staff\n  the program \"doesn't work.\"\n- Do not run one-sided incentives; paying the referrer while the friend\n  pays full price converts a recommendation into a commission.\n- Do not reward referrals for leaving reviews or blend the two asks -\n  review incentives violate platform policy (review-engine owns that\n  boundary); referral incentives are fine, so keep the programs separate.\n- Do not partner with a trade you have not seen work; their callback\n  becomes your one-star review.\n- Do not canvass streets cold with generic flyers; the card works because\n  of the neighbor-proof line, which requires an actual nearby job.\n\n## Quality bar\n\n- Every ask traces to a logged five-star moment; no cold blasts.\n- Both sides of the incentive are stated in every ask message.\n- The partner ledger shows given and received per partner per quarter.\n- Booking staff log a source for 100 percent of new customers - the share\n  number is only as real as the logging.\n\n## Escalation and routing\n\nCheck local licensing and consumer rules before paying inter-trade referral\nfees - some trades and jurisdictions restrict them; this is not legal\nadvice. Route the five-star detection and review asks to review-engine,\npartner-site links into local-seo-playbook, gym-specific referral programs\nto referral-and-affiliate-system, and the monthly referral-share and\nincentive-cost math into local-unit-economics to confirm the program stays\ncheaper than paid acquisition.\n","# Local Referral Engine\n\nReferrals are the best customers a local service business gets: near-zero\nacquisition cost, pre-sold trust, and higher close rates than any paid\nchannel. The costly mistake this skill prevents is leaving referrals passive -\n\"we get word of mouth\" - instead of building the three systems that\nmanufacture them: a timed ask, a two-sided incentive, and a partner network.\nRun local-unit-economics first to see the prize: Summit Plumbing (4 techs,\n$450 average ticket, $75,000 a month) pays about $119 to acquire a paid-lead\ncustomer, so every referred customer is roughly $119 of margin that paid\nchannels never touch.\n\n## Operating procedure\n\n### Step 1: Ask at the five-star moment - and only then\n\nThe ask-after-five-star-moment rule: the referral ask fires when a customer\nhas just expressed delight - a five-star review posted (review-engine detects\nexactly this), an effusive thank-you at job completion, a \"you saved us\"\ntext. Never ask a merely-satisfied customer; a referral is the customer\nspending social capital with a friend, and they only spend it at an\nemotional peak. This is the concrete handoff from review-engine: every\nfive-star review triggers the referral SMS within a day or two.\n\n```\nReferral ask SMS (1-2 days after a five-star moment):\n\"Hi [FILL: name], [FILL: owner\u002Ftech] from Summit Plumbing - thanks\nagain for the kind words! Small favor: most of our work comes from\nneighbors recommending us. If a friend ever needs a plumber, send\nthem our way - and as a thank-you, you'll both get $50 off your\nnext service. Just have them mention your name.\"\n```\n\n### Step 2: Design the incentive two-sided\n\nTwo-sided beats one-sided: reward the referrer and discount the friend. A\none-sided reward makes the recommendation feel like a commission (\"is he\nrecommending them for the fifty bucks?\"); two-sided lets the referrer open\nwith a gift (\"use these guys, you'll get $50 off\"), which preserves the\nsocial framing that makes referrals work. Summit's design: $50 service\ncredit to the referrer, $50 off the friend's first job. Against a $450\naverage ticket at 55 percent margin, a $100 total incentive still lands the\ncustomer far below the $119 paid CAC - and the referred customer closes\nbetter and refers onward. Size the incentive at roughly 10-25 percent of\naverage ticket total across both sides. Keep redemption dead simple: \"have\nthem mention your name,\" tracked in a spreadsheet - no codes, no portal.\n\n### Step 3: Build complementary-trade partnerships\n\nTrades see each other's future customers constantly: the electrician spots\nthe corroded water heater, the GC needs a plumber on every remodel, and the\nplumber sees breaker panels. Build a bench of 3-5 non-competing partners -\nfor Summit: an electrician, a GC, an HVAC company, a restoration company.\nRules that keep it alive:\n\n- Reciprocity is the currency. Track referrals given and received per\n  partner each quarter; a partner who receives five and sends zero gets a\n  friendly conversation, then gets dropped.\n- Refer only businesses you would let into your own house - their bad job\n  becomes your bad review.\n- Money between trades: a flat thank-you referral fee ($25-50) or pure\n  reciprocity both work; keep it simple and consistent. Check local\n  licensing rules - some jurisdictions and trades restrict paid referrals.\n- Make the intro warm: the partner texts the customer your name, not just\n  the reverse. A warm handoff closes at multiples of a cold mention.\n- These relationships also earn the real local links local-seo-playbook\n  wants - a \"trusted partners\" mention on each other's sites is prominence\n  that money cannot buy cleanly.\n\n### Step 4: Dominate the neighborhood around every job\n\nEvery job is a beachhead; density is the goal, because five jobs on one\nstreet cuts drive time and makes the brand ambient.\n\n- Job-site signage: a small yard sign during multi-day jobs, with\n  permission (\"mind if we leave this up while we work?\"). A truck wrapped\n  with the name and number is signage that never comes down.\n- \"We just worked on your street\" cards: after each job, the tech drops\n  cards at the 10-15 nearest doors. Script on the card: \"We just fixed a\n  water heater for one of your neighbors on [FILL: street]. If your\n  plumbing ever acts up, we're already in the neighborhood - $25 off for\n  [FILL: street] residents this month.\" Neighbor proof plus a local-only\n  offer outperforms any cold flyer.\n- Neighborhood groups: when a customer offers to post in the neighborhood\n  Facebook group or on Nextdoor, say yes and make it easy - a\n  recommendation there is a referral to three hundred neighbors at once.\n\n### Step 5: Track referral share monthly\n\nLog every new customer's source at booking (\"How did you hear about us?\" is\nmandatory, not optional). Track referral plus partner share of new\ncustomers monthly and feed the repeat\u002Freferral rate into\nlocal-unit-economics. Healthy mature share for a residential trade: 30-50\npercent of new customers from referral, partner, and neighborhood sources.\nBelow 15 percent after six months of running this engine means the asks are\nnot actually firing - audit whether the five-star trigger is being executed,\nnot whether customers \"just don't refer.\"\n\n## Inputs to elicit\n\nCollect: current referral share of new customers (label the usual guess as\na guess - booking-source logging is step zero), average ticket and margin\n(from local-unit-economics), review flow (is review-engine live - this\nskill's trigger depends on it), candidate partner trades already known, and\njobs per month per neighborhood. Defaults: $50\u002F$50 two-sided credit, cards\nat 10-15 doors per job, 3-5 partners.\n\n## Concrete thresholds\n\n- Ask timing: within 1-2 days of a five-star moment; never cold, never in\n  the same message as the review ask (one ask per message, always).\n- Incentive: two-sided, totaling 10-25 percent of average ticket; credits\n  beat cash for repeat-visit trades because they guarantee a next booking.\n- Partners: 3-5 active; reciprocity reviewed quarterly; give-receive\n  imbalance beyond 3:1 for two quarters means drop or renegotiate.\n- Neighborhood cards: 10-15 doors per completed job, same day.\n- Referral share target: 30-50 percent of new customers within a year;\n  under 15 percent after six months means the trigger is not firing.\n\n## Worked artifact: Summit's referral math\n\n```\nProgram: $50 credit to referrer + $50 off friend's first job\nFive-star moments\u002Fmo (from review-engine, at its 12\u002Fmo target\n  plus in-person delight):            ~18 asks sent\nReferrals landed (25% of asks):       ~4-5 new customers\u002Fmo\nPartner bench (electrician, GC, HVAC, restoration):\n  referrals received:                 ~4\u002Fmo   given: ~5\u002Fmo (healthy)\nStreet cards: ~55 jobs\u002Fmo x 12 doors = ~660 cards -> ~3 jobs\u002Fmo\nNew referred\u002Fpartner\u002Fneighbor customers: ~11-12\u002Fmo of ~35 new\n  customers = ~32% referral share  (target band: 30-50%)\nCost check: ~$100 incentive per referred customer vs $119 paid CAC,\nwith a customer who closes better and refers onward. Verdict: scale.\n```\n\n## Deliverable\n\nA referral operating system on one page: the five-star-trigger ask SMS with\nfields filled, the two-sided incentive spec and its tracking sheet, a\npartner bench list with the reciprocity ledger, the street-card copy and\ndrop routine, and the monthly referral-share line that feeds\nlocal-unit-economics.\n\n## Do NOT\n\n- Do not ask merely-satisfied customers for referrals; a lukewarm referral\n  spends trust the customer does not have, and the silence teaches staff\n  the program \"doesn't work.\"\n- Do not run one-sided incentives; paying the referrer while the friend\n  pays full price converts a recommendation into a commission.\n- Do not reward referrals for leaving reviews or blend the two asks -\n  review incentives violate platform policy (review-engine owns that\n  boundary); referral incentives are fine, so keep the programs separate.\n- Do not partner with a trade you have not seen work; their callback\n  becomes your one-star review.\n- Do not canvass streets cold with generic flyers; the card works because\n  of the neighbor-proof line, which requires an actual nearby job.\n\n## Quality bar\n\n- Every ask traces to a logged five-star moment; no cold blasts.\n- Both sides of the incentive are stated in every ask message.\n- The partner ledger shows given and received per partner per quarter.\n- Booking staff log a source for 100 percent of new customers - the share\n  number is only as real as the logging.\n\n## Escalation and routing\n\nCheck local licensing and consumer rules before paying inter-trade referral\nfees - some trades and jurisdictions restrict them; this is not legal\nadvice. Route the five-star detection and review asks to review-engine,\npartner-site links into local-seo-playbook, gym-specific referral programs\nto referral-and-affiliate-system, and the monthly referral-share and\nincentive-cost math into local-unit-economics to confirm the program stays\ncheaper than paid acquisition.\n",{"name":5,"description":7},"main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Flocal-referral-engine",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 local-referral-engine",{"tool":39,"command":40},"bunx","bunx skills add SkillMedev\u002Fskills --skill local-referral-engine",{"tool":42,"command":43},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill local-referral-engine","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Flocal-referral-engine\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",[],[]]