[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75160AXE58347XEVYXGRDVQ":3,"skill-same:01M75160AXE58347XEVYXGRDVQ":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},"01M75160AXE58347XEVYXGRDVQ","no-show-reduction",null,"Cuts appointment no-shows for a local service business with a three-step reminder ladder (booking confirmation, day-before SMS, morning-of SMS with the tech's name and photo), confirmation-required policies, deposit rules for high-value appointments, and a reschedule-not-cancel script. Use when an owner says \"customers keep not being home when the tech shows up\", \"how do I reduce no-shows\", \"should I take deposits for appointments\", or \"people cancel same-day and it kills my schedule\". Do NOT use for chasing quotes after the visit happened - use quote-follow-up-sequences instead. Do NOT use for winning back lapsed customers - use win-back-campaign 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\u002Fno-show-reduction\u002FSKILL.md",[],[],"2026-11-11 18:11:01",false,"---\nname: no-show-reduction\ndescription: Cuts appointment no-shows for a local service business with a three-step reminder ladder (booking confirmation, day-before SMS, morning-of SMS with the tech's name and photo), confirmation-required policies, deposit rules for high-value appointments, and a reschedule-not-cancel script. Use when an owner says \"customers keep not being home when the tech shows up\", \"how do I reduce no-shows\", \"should I take deposits for appointments\", or \"people cancel same-day and it kills my schedule\". Do NOT use for chasing quotes after the visit happened - use quote-follow-up-sequences instead. Do NOT use for winning back lapsed customers - use win-back-campaign instead.\n---\n\n# No-Show Reduction\n\nA no-show is the most expensive kind of nothing: the lead was paid for, the\nslot was reserved, the tech drove out or sat idle, and no revenue arrived.\nThe costly mistake this skill prevents is treating no-shows as weather -\nrandom and unmanageable - when a reminder ladder and a confirmation policy\nreliably cut them by half or more. This skill and quote-follow-up-sequences\nare the pack's two revenue-protection systems: both defend money the lead\nspend already paid for.\n\nWorked business throughout: Summit Plumbing, 4 techs, $450 average ticket,\n$75,000 a month, booking roughly 300 appointments monthly. At its current 14\npercent no-show rate that is about 42 missed visits; at the 65 percent close\nrate that is roughly 14 lost jobs and $6,100 a month in gross revenue - the\nsame figures local-unit-economics uses when it flags show rate as Summit's\nconstrained lever.\n\n## Operating procedure\n\n### Step 1: Measure the real no-show rate\n\nCount last month's booked appointments and how many the customer missed\n(not home, not answering, same-hour cancellation). The red line: a no-show\nrate above 10 percent is a systemic problem - process, not bad luck - and\nthis whole skill applies. Under 5 percent is healthy; run only the ladder's\nfirst two rungs and move on. Summit measures 14 percent: systemic.\n\n### Step 2: Install the reminder ladder\n\nThree rungs, each with a distinct job. SMS for rungs two and three - texts\nget read within minutes, email does not.\n\n```\nRUNG 1 - Booking confirmation (immediately at booking, SMS + email):\n\"You're booked! Summit Plumbing will be out [FILL: day, date],\narrival window [FILL: window], for [FILL: job]. Reply C to confirm,\nR to reschedule. Questions? Call [FILL: office number].\"\n\nRUNG 2 - Day-before SMS (previous day, ~4 pm):\n\"Hi [FILL: name], reminder: Summit Plumbing is scheduled tomorrow,\n[FILL: window], for [FILL: job]. Reply C to confirm or R to\nreschedule - please have someone 18+ home and the area accessible.\"\n\nRUNG 3 - Morning-of SMS with the tech's name and photo (2 hours ahead):\n\"Good morning [FILL: name]! [FILL: tech name] from Summit Plumbing\nis headed your way, arriving [FILL: window]. Here's [FILL: tech\nfirst name] so you know who's at the door: [FILL: photo link\u002FMMS].\nRunning into a problem? Reply here or call [FILL: office].\"\n```\n\nThe tech name and photo on rung 3 does double duty: it humanizes the\nappointment (people no-show a company, rarely a person named Marcus whose\nface they have seen) and it is a safety courtesy that customers rate highly.\n\n### Step 3: Decide confirmation-required vs assumed, by slot value\n\nTwo policies, applied by appointment type:\n\n- Confirmation-assumed (default for standard repair calls): the appointment\n  stands unless the customer cancels. Low friction, fits abundant slot\n  supply.\n- Confirmation-required (for high-value or long slots): if the customer has\n  not replied C by rung 2, the office calls; no confirmation by 6 pm means\n  the slot is released to the waitlist and the customer is told so in the\n  rung-2 message. Use when a no-show costs half a day, not half an hour.\n\nSummit runs assumed for standard calls, required for half-day jobs like\nwater heater replacements and sewer line work.\n\n### Step 4: Take deposits on high-value appointments\n\nDeposit rule: any appointment reserving 4+ tech-hours or requiring ordered\nmaterials takes a deposit - 10 to 20 percent of the quoted job or a flat\n$100, whichever is greater, credited to the invoice. Frame it as reserving\nmaterials and the crew, not as distrust: \"We order your unit and block the\ncrew's day, so we take a $150 deposit that comes straight off your bill.\"\nDeposit-backed appointments no-show at a fraction of the open-slot rate.\nDo not take deposits on standard diagnostic calls - the friction costs more\nbookings than the no-shows cost.\n\n### Step 5: Answer every cancellation with the reschedule-not-cancel script\n\nNever end a cancellation call with the calendar empty. The script:\n\n```\nCustomer: \"I need to cancel Thursday.\"\nOffice:  \"No problem at all, [FILL: name] - let's just move it so you\n         don't lose your place. I've got [FILL: day] at [FILL: time]\n         or [FILL: day] at [FILL: time] - which is easier?\"\nIf they resist a date: \"Totally fine - I'll pencil you for [FILL: day\n+7] and text you the day before to confirm. If that doesn't work,\nwe'll shuffle it then. Sound good?\"\n```\n\nA cancellation converted to a reschedule keeps the customer, the CAC already\nspent, and the job. A pure cancellation usually means they call a competitor\nthe next time the pipe drips.\n\n### Step 6: Handle the no-show that still happens\n\nSame day, one friendly SMS - assume good faith: \"Hi [FILL: name], we came by\nat [FILL: time] but couldn't reach you. No worries - want me to find you a\nnew slot this week?\" Track repeat offenders; two no-shows moves that\ncustomer to confirmation-required permanently, three adds a deposit\nrequirement. Keep a same-day waitlist of flexible customers to backfill\nreleased slots so a no-show costs a phone call, not a tech-hour.\n\n### Step 7: Re-measure monthly and report the show rate\n\nTrack no-show rate on the monthly sheet and feed the show rate into\nlocal-unit-economics. For Summit, cutting 14 percent to 7 percent recovers\nroughly $6,100 a month gross and drops CAC from about $119 to about $110 -\nthe cheapest customer-acquisition improvement available, because it buys\nzero new leads.\n\n## Inputs to elicit\n\nCollect: booked appointments and no-shows last month (count them - owners\nguess low; label a guess as a guess), booking channel (phone, web, both),\nwhether SMS with photos is available, average slot length by job type, and\ncurrent deposit practice. Defaults: ladder at booking \u002F day-before 4 pm \u002F\n2-hours-ahead; deposits only on 4+ hour jobs; assumed confirmation for\nstandard calls.\n\n## Concrete thresholds\n\n- Red line: no-show rate above 10 percent is systemic; under 5 percent is\n  healthy.\n- Ladder timing: confirmation at booking, reminder day before around 4 pm,\n  morning-of 2 hours ahead. Three touches - a fourth is nagging.\n- Deposits: 4+ tech-hours or ordered materials; 10-20 percent or $100\n  minimum, credited to the invoice.\n- Confirmation-required cutoff: unconfirmed by 6 pm day-before releases the\n  slot.\n- Expected result: a full ladder plus policies typically cuts no-shows by\n  half within 60 days; if not, the booking process is overbooking or the\n  arrival windows are unrealistic.\n\n## Worked artifact: Summit's no-show economics\n\n```\n                          BEFORE          AFTER (60 days)\nBooked appointments\u002Fmo:   300             300\nNo-show rate:             14%             7%\nMissed visits:            42              21\nLost jobs (65% close):    ~27             ~14\nLost gross revenue:       ~$12,300\u002Fmo     ~$6,100\u002Fmo\nRecovered:                                ~$6,100\u002Fmo (~$73k\u002Fyr)\nChanges made: 3-rung ladder w\u002F tech photo, deposits on 4+ hr jobs,\nreschedule-not-cancel script at the front desk, same-day waitlist.\n```\n\n## Deliverable\n\nA one-page no-show system: the three ladder messages with fields filled, the\nconfirmation policy per appointment type, the deposit rule with its customer\nframing sentence, the reschedule-not-cancel script at the booking desk, and\na monthly no-show log line that feeds the show rate into\nlocal-unit-economics.\n\n## Do NOT\n\n- Do not add reminder rungs beyond three; past that, reminders train\n  customers to ignore them.\n- Do not take deposits on low-value diagnostic calls - the booking friction\n  costs more than the no-shows.\n- Do not scold no-show customers on the first offense; assume good faith\n  once, tighten policy on repeats.\n- Do not accept a bare cancellation when a reschedule was never offered -\n  that is the script's whole job.\n- Do not quietly overbook to compensate for no-shows; the double-booked day\n  when everyone shows costs reviews (see review-engine's 1-star procedure)\n  and burns techs.\n\n## Quality bar\n\n- The no-show rate is measured from real counts, before and 60 days after.\n- Every ladder message states the job, the window, and a one-tap reply\n  action.\n- The deposit policy names its threshold and its invoice-credit framing.\n- Repeat offenders have an escalation path written down, not improvised.\n\n## Escalation and routing\n\nIf no-shows concentrate in one lead source, the problem is lead quality -\ntake it to the channel math in local-unit-economics before blaming the\nladder. Quotes that go silent after a completed visit belong to\nquote-follow-up-sequences. Lapsed past customers belong to\nwin-back-campaign. Completed visits that end happy are review-engine's\npeak-satisfaction moment - make sure the ask fires.\n","# No-Show Reduction\n\nA no-show is the most expensive kind of nothing: the lead was paid for, the\nslot was reserved, the tech drove out or sat idle, and no revenue arrived.\nThe costly mistake this skill prevents is treating no-shows as weather -\nrandom and unmanageable - when a reminder ladder and a confirmation policy\nreliably cut them by half or more. This skill and quote-follow-up-sequences\nare the pack's two revenue-protection systems: both defend money the lead\nspend already paid for.\n\nWorked business throughout: Summit Plumbing, 4 techs, $450 average ticket,\n$75,000 a month, booking roughly 300 appointments monthly. At its current 14\npercent no-show rate that is about 42 missed visits; at the 65 percent close\nrate that is roughly 14 lost jobs and $6,100 a month in gross revenue - the\nsame figures local-unit-economics uses when it flags show rate as Summit's\nconstrained lever.\n\n## Operating procedure\n\n### Step 1: Measure the real no-show rate\n\nCount last month's booked appointments and how many the customer missed\n(not home, not answering, same-hour cancellation). The red line: a no-show\nrate above 10 percent is a systemic problem - process, not bad luck - and\nthis whole skill applies. Under 5 percent is healthy; run only the ladder's\nfirst two rungs and move on. Summit measures 14 percent: systemic.\n\n### Step 2: Install the reminder ladder\n\nThree rungs, each with a distinct job. SMS for rungs two and three - texts\nget read within minutes, email does not.\n\n```\nRUNG 1 - Booking confirmation (immediately at booking, SMS + email):\n\"You're booked! Summit Plumbing will be out [FILL: day, date],\narrival window [FILL: window], for [FILL: job]. Reply C to confirm,\nR to reschedule. Questions? Call [FILL: office number].\"\n\nRUNG 2 - Day-before SMS (previous day, ~4 pm):\n\"Hi [FILL: name], reminder: Summit Plumbing is scheduled tomorrow,\n[FILL: window], for [FILL: job]. Reply C to confirm or R to\nreschedule - please have someone 18+ home and the area accessible.\"\n\nRUNG 3 - Morning-of SMS with the tech's name and photo (2 hours ahead):\n\"Good morning [FILL: name]! [FILL: tech name] from Summit Plumbing\nis headed your way, arriving [FILL: window]. Here's [FILL: tech\nfirst name] so you know who's at the door: [FILL: photo link\u002FMMS].\nRunning into a problem? Reply here or call [FILL: office].\"\n```\n\nThe tech name and photo on rung 3 does double duty: it humanizes the\nappointment (people no-show a company, rarely a person named Marcus whose\nface they have seen) and it is a safety courtesy that customers rate highly.\n\n### Step 3: Decide confirmation-required vs assumed, by slot value\n\nTwo policies, applied by appointment type:\n\n- Confirmation-assumed (default for standard repair calls): the appointment\n  stands unless the customer cancels. Low friction, fits abundant slot\n  supply.\n- Confirmation-required (for high-value or long slots): if the customer has\n  not replied C by rung 2, the office calls; no confirmation by 6 pm means\n  the slot is released to the waitlist and the customer is told so in the\n  rung-2 message. Use when a no-show costs half a day, not half an hour.\n\nSummit runs assumed for standard calls, required for half-day jobs like\nwater heater replacements and sewer line work.\n\n### Step 4: Take deposits on high-value appointments\n\nDeposit rule: any appointment reserving 4+ tech-hours or requiring ordered\nmaterials takes a deposit - 10 to 20 percent of the quoted job or a flat\n$100, whichever is greater, credited to the invoice. Frame it as reserving\nmaterials and the crew, not as distrust: \"We order your unit and block the\ncrew's day, so we take a $150 deposit that comes straight off your bill.\"\nDeposit-backed appointments no-show at a fraction of the open-slot rate.\nDo not take deposits on standard diagnostic calls - the friction costs more\nbookings than the no-shows cost.\n\n### Step 5: Answer every cancellation with the reschedule-not-cancel script\n\nNever end a cancellation call with the calendar empty. The script:\n\n```\nCustomer: \"I need to cancel Thursday.\"\nOffice:  \"No problem at all, [FILL: name] - let's just move it so you\n         don't lose your place. I've got [FILL: day] at [FILL: time]\n         or [FILL: day] at [FILL: time] - which is easier?\"\nIf they resist a date: \"Totally fine - I'll pencil you for [FILL: day\n+7] and text you the day before to confirm. If that doesn't work,\nwe'll shuffle it then. Sound good?\"\n```\n\nA cancellation converted to a reschedule keeps the customer, the CAC already\nspent, and the job. A pure cancellation usually means they call a competitor\nthe next time the pipe drips.\n\n### Step 6: Handle the no-show that still happens\n\nSame day, one friendly SMS - assume good faith: \"Hi [FILL: name], we came by\nat [FILL: time] but couldn't reach you. No worries - want me to find you a\nnew slot this week?\" Track repeat offenders; two no-shows moves that\ncustomer to confirmation-required permanently, three adds a deposit\nrequirement. Keep a same-day waitlist of flexible customers to backfill\nreleased slots so a no-show costs a phone call, not a tech-hour.\n\n### Step 7: Re-measure monthly and report the show rate\n\nTrack no-show rate on the monthly sheet and feed the show rate into\nlocal-unit-economics. For Summit, cutting 14 percent to 7 percent recovers\nroughly $6,100 a month gross and drops CAC from about $119 to about $110 -\nthe cheapest customer-acquisition improvement available, because it buys\nzero new leads.\n\n## Inputs to elicit\n\nCollect: booked appointments and no-shows last month (count them - owners\nguess low; label a guess as a guess), booking channel (phone, web, both),\nwhether SMS with photos is available, average slot length by job type, and\ncurrent deposit practice. Defaults: ladder at booking \u002F day-before 4 pm \u002F\n2-hours-ahead; deposits only on 4+ hour jobs; assumed confirmation for\nstandard calls.\n\n## Concrete thresholds\n\n- Red line: no-show rate above 10 percent is systemic; under 5 percent is\n  healthy.\n- Ladder timing: confirmation at booking, reminder day before around 4 pm,\n  morning-of 2 hours ahead. Three touches - a fourth is nagging.\n- Deposits: 4+ tech-hours or ordered materials; 10-20 percent or $100\n  minimum, credited to the invoice.\n- Confirmation-required cutoff: unconfirmed by 6 pm day-before releases the\n  slot.\n- Expected result: a full ladder plus policies typically cuts no-shows by\n  half within 60 days; if not, the booking process is overbooking or the\n  arrival windows are unrealistic.\n\n## Worked artifact: Summit's no-show economics\n\n```\n                          BEFORE          AFTER (60 days)\nBooked appointments\u002Fmo:   300             300\nNo-show rate:             14%             7%\nMissed visits:            42              21\nLost jobs (65% close):    ~27             ~14\nLost gross revenue:       ~$12,300\u002Fmo     ~$6,100\u002Fmo\nRecovered:                                ~$6,100\u002Fmo (~$73k\u002Fyr)\nChanges made: 3-rung ladder w\u002F tech photo, deposits on 4+ hr jobs,\nreschedule-not-cancel script at the front desk, same-day waitlist.\n```\n\n## Deliverable\n\nA one-page no-show system: the three ladder messages with fields filled, the\nconfirmation policy per appointment type, the deposit rule with its customer\nframing sentence, the reschedule-not-cancel script at the booking desk, and\na monthly no-show log line that feeds the show rate into\nlocal-unit-economics.\n\n## Do NOT\n\n- Do not add reminder rungs beyond three; past that, reminders train\n  customers to ignore them.\n- Do not take deposits on low-value diagnostic calls - the booking friction\n  costs more than the no-shows.\n- Do not scold no-show customers on the first offense; assume good faith\n  once, tighten policy on repeats.\n- Do not accept a bare cancellation when a reschedule was never offered -\n  that is the script's whole job.\n- Do not quietly overbook to compensate for no-shows; the double-booked day\n  when everyone shows costs reviews (see review-engine's 1-star procedure)\n  and burns techs.\n\n## Quality bar\n\n- The no-show rate is measured from real counts, before and 60 days after.\n- Every ladder message states the job, the window, and a one-tap reply\n  action.\n- The deposit policy names its threshold and its invoice-credit framing.\n- Repeat offenders have an escalation path written down, not improvised.\n\n## Escalation and routing\n\nIf no-shows concentrate in one lead source, the problem is lead quality -\ntake it to the channel math in local-unit-economics before blaming the\nladder. Quotes that go silent after a completed visit belong to\nquote-follow-up-sequences. Lapsed past customers belong to\nwin-back-campaign. Completed visits that end happy are review-engine's\npeak-satisfaction moment - make sure the ask fires.\n",{"name":5,"description":7},"main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Fno-show-reduction",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 no-show-reduction",{"tool":39,"command":40},"bunx","bunx skills add SkillMedev\u002Fskills --skill no-show-reduction",{"tool":42,"command":43},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill no-show-reduction","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fno-show-reduction\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",[],[]]