[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M751KF7XKTJ8XNBZ1SHJGGYV":3,"skill-same:01M751KF7XKTJ8XNBZ1SHJGGYV":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},"01M751KF7XKTJ8XNBZ1SHJGGYV","retainer-pricing-calculator",null,"Prices monthly freelance retainers from capacity math (billable hours at 50-60 percent of working hours), an effective-rate floor, and a value-anchor adjustment, with utilization red lines and a runnable Node calculator. Use when a freelancer says \"what should I charge for a retainer\", \"how many clients can I actually take\", \"price my monthly package\", \"am I undercharging\", \"my calendar is full but I'm broke\", or \"what's my minimum viable rate\". Do NOT use for pricing a software product or subscription tiers - use saas-pricing instead; for one-time salary or offer negotiation, use salary-negotiation.","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\u002Fretainer-pricing-calculator\u002FSKILL.md",[],[],"2026-11-11 18:21:06",false,"---\nname: retainer-pricing-calculator\ndescription: Prices monthly freelance retainers from capacity math (billable hours at 50-60 percent of working hours), an effective-rate floor, and a value-anchor adjustment, with utilization red lines and a runnable Node calculator. Use when a freelancer says \"what should I charge for a retainer\", \"how many clients can I actually take\", \"price my monthly package\", \"am I undercharging\", \"my calendar is full but I'm broke\", or \"what's my minimum viable rate\". Do NOT use for pricing a software product or subscription tiers - use saas-pricing instead; for one-time salary or offer negotiation, use salary-negotiation.\n---\n\n# Retainer Pricing Calculator\n\nFreelancers price retainers by gut, and the gut consistently forgets two things: that only half of a working month is billable, and that a retainer sells guaranteed availability, which is worth more than the hours inside it. The result is the classic trap - fully booked and still underpaid. This calculator prices from capacity up and value down, and tells the freelancer the floor below which a retainer quietly loses money.\n\nThis is the third skill in the Freelancer \u002F Consultant OS setup sequence: freelance-positioning chose the niche, productized-service-designer built the tiers, and this skill validates the prices. Worked example: Maya, a freelance brand designer at $6,000\u002Fmonth on hourly work at $75\u002Fhr, pricing her Brand System Retainer.\n\n## Operating procedure\n\n### Step 1: Collect the inputs\n\nLabel any guess as a guess.\n\n1. Working hours per month (Maya: 40 hrs\u002Fweek x 4 = 160).\n2. Target monthly gross income (Maya: $9,000 - a deliberate raise from her current $6,000).\n3. Monthly business overhead: software, insurance, accounting, fees (Maya: $500).\n4. Hours budgeted per retainer client per month (Maya: 36, from her Tier 2 scope in productized-service-designer).\n5. Current hourly rate, for the before\u002Fafter comparison (Maya: $75).\n\n### Step 2: Do the capacity math\n\nBillable hours are realistically **50-60 percent of working hours**. The other 40-50 percent goes to sales, admin, invoicing, marketing, and email - it does not disappear because the freelancer wishes it away. Use 0.55 as the default; 0.60 only for freelancers with steady inbound and minimal admin; below 0.50 while actively building a pipeline.\n\nMaya: 160 x 0.55 = **88 billable hours\u002Fmonth**. This number is the whole ballgame - every promise sold must fit inside it.\n\n### Step 3: Compute the effective-rate floor\n\n```\nfloor hourly = (target income + overhead) \u002F billable capacity\nfloor retainer = floor hourly x hours per client\n```\n\nMaya: ($9,000 + $500) \u002F 88 = **$107.95\u002Fhr** floor; x 36 hrs = **$3,886 floor retainer**. Any retainer priced below the floor means the target income is arithmetically unreachable at full capacity. The floor is a red line, never the price.\n\n### Step 4: Apply the value-anchor adjustment\n\nThe floor prices hours; the retainer also sells reserved capacity, priority turnaround, and accumulated context. Multiply the floor by a value anchor of **1.15-1.5**: 1.15-1.25 when proof in the niche is thin, 1.25-1.4 with solid case studies, up to 1.5 when the deliverable moves client revenue directly and the freelancer can show it. Round up to a clean number.\n\nMaya, with three food-and-beverage case studies, uses 1.25: $3,886 x 1.25 = $4,858, rounded to **$4,900\u002Fmonth** - the Tier 2 price in productized-service-designer.\n\n### Step 5: Check the utilization red lines\n\n- **80 percent of capacity is the ceiling for sold retainer hours** (Maya: 70.4 of 88). The buffer absorbs overruns, sick days, and sales time; selling to 100 percent guarantees either missed deadlines or a dead pipeline - and sustained utilization above 80 percent is also the trigger condition in raise-your-rates-playbook.\n- Max clients = floor(capacity \u002F hours per client). Maya: floor(88\u002F36) = **2 retainer clients**, using 72 hours (82 percent - at the line, so any third engagement must be small or replace one).\n- If income at the full roster (clients x retainer) misses the target, the fix is price or scope, not a third client that breaks the red line.\n\n### Step 6: Run the calculator and read the verdict\n\n## Calculator\n\nSelf-contained Node script. Save as `retainer_calc.js`, edit the inputs, run `node retainer_calc.js`. No dependencies.\n\n```javascript\n\u002F\u002F Retainer pricing calculator. Edit the inputs, then: node retainer_calc.js\nconst inputs = {\n  workingHoursPerMonth: 160,   \u002F\u002F total working hours (40 hrs\u002Fweek x 4 weeks)\n  billableShare: 0.55,         \u002F\u002F realistic billable fraction (0.50-0.60)\n  targetMonthlyIncome: 9000,   \u002F\u002F gross income goal for the month\n  monthlyOverhead: 500,        \u002F\u002F software, insurance, subcontractors, fees\n  retainerHoursPerClient: 36,  \u002F\u002F hours budgeted per retainer client per month\n  valueMultiplier: 1.25,       \u002F\u002F value-anchor adjustment (1.15-1.5)\n  currentHourlyRate: 75,       \u002F\u002F what the freelancer charges today\n}\n\nfunction model(i) {\n  const capacityHours = i.workingHoursPerMonth * i.billableShare\n  const floorHourly = (i.targetMonthlyIncome + i.monthlyOverhead) \u002F capacityHours\n  const floorRetainer = floorHourly * i.retainerHoursPerClient\n  const targetRetainer = Math.ceil((floorRetainer * i.valueMultiplier) \u002F 100) * 100\n  const maxRetainerClients = Math.floor(capacityHours \u002F i.retainerHoursPerClient)\n  const utilizationRedLine = capacityHours * 0.8\n  const effectiveRateAtTarget = targetRetainer \u002F i.retainerHoursPerClient\n  const incomeAtFullRoster = targetRetainer * maxRetainerClients\n  return { capacityHours, floorHourly, floorRetainer, targetRetainer,\n    maxRetainerClients, utilizationRedLine, effectiveRateAtTarget, incomeAtFullRoster }\n}\n\nconst r = model(inputs)\nconst money = (n) => '$' + n.toFixed(2)\nconsole.log('Billable capacity (hrs\u002Fmonth):   ', r.capacityHours.toFixed(1))\nconsole.log('Effective-rate floor (hourly):   ', money(r.floorHourly))\nconsole.log('Retainer floor price:            ', money(r.floorRetainer))\nconsole.log('Target retainer (value-anchored):', money(r.targetRetainer))\nconsole.log('Max retainer clients:            ', r.maxRetainerClients)\nconsole.log('Utilization red line (hrs):      ', r.utilizationRedLine.toFixed(1))\nconsole.log('Effective rate at target:        ', money(r.effectiveRateAtTarget))\nconsole.log('Income at full roster:           ', money(r.incomeAtFullRoster))\nconsole.log('Vs current hourly rate:          ', money(inputs.currentHourlyRate), '->', money(r.effectiveRateAtTarget))\n```\n\n### Worked example output\n\nWith Maya's inputs above the script prints:\n\n```\nBillable capacity (hrs\u002Fmonth):    88.0\nEffective-rate floor (hourly):    $107.95\nRetainer floor price:             $3886.36\nTarget retainer (value-anchored): $4900.00\nMax retainer clients:             2\nUtilization red line (hrs):       70.4\nEffective rate at target:         $136.11\nIncome at full roster:            $9800.00\nVs current hourly rate:           $75.00 -> $136.11\n```\n\nRead it: Maya has 88 billable hours, not 160. Her floor is $107.95\u002Fhr - her current $75\u002Fhr rate was below her own floor, which is exactly why full months still produced only $6,000. The value-anchored retainer lands at $4,900; two clients fill 72 of 88 hours (right at the 80 percent line) and produce $9,800\u002Fmonth at an effective $136\u002Fhr - a raise of over 80 percent in effective rate while working fewer billed hours.\n\n## Concrete thresholds\n\n- Billable share: 50-60 percent of working hours; default 0.55.\n- Value anchor: 1.15-1.5 on the floor, scaled to proof strength.\n- Utilization red line: sold hours at or below 80 percent of billable capacity; sustained above 80 percent triggers raise-your-rates-playbook.\n- Never price at or below the floor; the floor is the walk-away number, not the offer.\n- Re-run the calculator whenever scope, overhead, or the income target changes, and at every rate review.\n\n## Deliverable\n\nThe filled calculator output plus a one-line pricing verdict: floor price, target retainer, max clients, and whether the full roster hits the income target. This validates (or corrects) the tier prices in productized-service-designer.\n\n## Do NOT\n\n- Do not assume 100 percent billable hours; that single error understates the needed rate by nearly half.\n- Do not present the floor price to clients - it is an internal red line, and anchoring on it invites negotiation below it.\n- Do not add a client past the 80 percent red line to hit an income target; raise the price instead.\n- Do not convert the retainer back to an hourly comparison in front of the client (\"that's $136\u002Fhr!\") - the retainer sells an outcome and reserved capacity, and re-hourly-izing it invites hourly objections.\n- Do not skip the value anchor out of modesty; pricing at the bare floor leaves the freelancer with zero margin for a single bad month.\n\n## Quality bar\n\nDone when: every input is sourced or labeled a guess; the target retainer clears the floor with the anchor applied; the roster respects the 80 percent red line; and the full-roster income is compared against the target with an explicit pass\u002Ffail.\n\n## Escalation and neighbors\n\nNot financial or tax advice - an accountant should sanity-check the overhead and income targets against taxes and benefits, which this model treats as inside the target figure. Scope the hours-per-client input in productized-service-designer; contract the price with statement-of-work-writer; when utilization holds above 80 percent, go to raise-your-rates-playbook.\n","# Retainer Pricing Calculator\n\nFreelancers price retainers by gut, and the gut consistently forgets two things: that only half of a working month is billable, and that a retainer sells guaranteed availability, which is worth more than the hours inside it. The result is the classic trap - fully booked and still underpaid. This calculator prices from capacity up and value down, and tells the freelancer the floor below which a retainer quietly loses money.\n\nThis is the third skill in the Freelancer \u002F Consultant OS setup sequence: freelance-positioning chose the niche, productized-service-designer built the tiers, and this skill validates the prices. Worked example: Maya, a freelance brand designer at $6,000\u002Fmonth on hourly work at $75\u002Fhr, pricing her Brand System Retainer.\n\n## Operating procedure\n\n### Step 1: Collect the inputs\n\nLabel any guess as a guess.\n\n1. Working hours per month (Maya: 40 hrs\u002Fweek x 4 = 160).\n2. Target monthly gross income (Maya: $9,000 - a deliberate raise from her current $6,000).\n3. Monthly business overhead: software, insurance, accounting, fees (Maya: $500).\n4. Hours budgeted per retainer client per month (Maya: 36, from her Tier 2 scope in productized-service-designer).\n5. Current hourly rate, for the before\u002Fafter comparison (Maya: $75).\n\n### Step 2: Do the capacity math\n\nBillable hours are realistically **50-60 percent of working hours**. The other 40-50 percent goes to sales, admin, invoicing, marketing, and email - it does not disappear because the freelancer wishes it away. Use 0.55 as the default; 0.60 only for freelancers with steady inbound and minimal admin; below 0.50 while actively building a pipeline.\n\nMaya: 160 x 0.55 = **88 billable hours\u002Fmonth**. This number is the whole ballgame - every promise sold must fit inside it.\n\n### Step 3: Compute the effective-rate floor\n\n```\nfloor hourly = (target income + overhead) \u002F billable capacity\nfloor retainer = floor hourly x hours per client\n```\n\nMaya: ($9,000 + $500) \u002F 88 = **$107.95\u002Fhr** floor; x 36 hrs = **$3,886 floor retainer**. Any retainer priced below the floor means the target income is arithmetically unreachable at full capacity. The floor is a red line, never the price.\n\n### Step 4: Apply the value-anchor adjustment\n\nThe floor prices hours; the retainer also sells reserved capacity, priority turnaround, and accumulated context. Multiply the floor by a value anchor of **1.15-1.5**: 1.15-1.25 when proof in the niche is thin, 1.25-1.4 with solid case studies, up to 1.5 when the deliverable moves client revenue directly and the freelancer can show it. Round up to a clean number.\n\nMaya, with three food-and-beverage case studies, uses 1.25: $3,886 x 1.25 = $4,858, rounded to **$4,900\u002Fmonth** - the Tier 2 price in productized-service-designer.\n\n### Step 5: Check the utilization red lines\n\n- **80 percent of capacity is the ceiling for sold retainer hours** (Maya: 70.4 of 88). The buffer absorbs overruns, sick days, and sales time; selling to 100 percent guarantees either missed deadlines or a dead pipeline - and sustained utilization above 80 percent is also the trigger condition in raise-your-rates-playbook.\n- Max clients = floor(capacity \u002F hours per client). Maya: floor(88\u002F36) = **2 retainer clients**, using 72 hours (82 percent - at the line, so any third engagement must be small or replace one).\n- If income at the full roster (clients x retainer) misses the target, the fix is price or scope, not a third client that breaks the red line.\n\n### Step 6: Run the calculator and read the verdict\n\n## Calculator\n\nSelf-contained Node script. Save as `retainer_calc.js`, edit the inputs, run `node retainer_calc.js`. No dependencies.\n\n```javascript\n\u002F\u002F Retainer pricing calculator. Edit the inputs, then: node retainer_calc.js\nconst inputs = {\n  workingHoursPerMonth: 160,   \u002F\u002F total working hours (40 hrs\u002Fweek x 4 weeks)\n  billableShare: 0.55,         \u002F\u002F realistic billable fraction (0.50-0.60)\n  targetMonthlyIncome: 9000,   \u002F\u002F gross income goal for the month\n  monthlyOverhead: 500,        \u002F\u002F software, insurance, subcontractors, fees\n  retainerHoursPerClient: 36,  \u002F\u002F hours budgeted per retainer client per month\n  valueMultiplier: 1.25,       \u002F\u002F value-anchor adjustment (1.15-1.5)\n  currentHourlyRate: 75,       \u002F\u002F what the freelancer charges today\n}\n\nfunction model(i) {\n  const capacityHours = i.workingHoursPerMonth * i.billableShare\n  const floorHourly = (i.targetMonthlyIncome + i.monthlyOverhead) \u002F capacityHours\n  const floorRetainer = floorHourly * i.retainerHoursPerClient\n  const targetRetainer = Math.ceil((floorRetainer * i.valueMultiplier) \u002F 100) * 100\n  const maxRetainerClients = Math.floor(capacityHours \u002F i.retainerHoursPerClient)\n  const utilizationRedLine = capacityHours * 0.8\n  const effectiveRateAtTarget = targetRetainer \u002F i.retainerHoursPerClient\n  const incomeAtFullRoster = targetRetainer * maxRetainerClients\n  return { capacityHours, floorHourly, floorRetainer, targetRetainer,\n    maxRetainerClients, utilizationRedLine, effectiveRateAtTarget, incomeAtFullRoster }\n}\n\nconst r = model(inputs)\nconst money = (n) => '$' + n.toFixed(2)\nconsole.log('Billable capacity (hrs\u002Fmonth):   ', r.capacityHours.toFixed(1))\nconsole.log('Effective-rate floor (hourly):   ', money(r.floorHourly))\nconsole.log('Retainer floor price:            ', money(r.floorRetainer))\nconsole.log('Target retainer (value-anchored):', money(r.targetRetainer))\nconsole.log('Max retainer clients:            ', r.maxRetainerClients)\nconsole.log('Utilization red line (hrs):      ', r.utilizationRedLine.toFixed(1))\nconsole.log('Effective rate at target:        ', money(r.effectiveRateAtTarget))\nconsole.log('Income at full roster:           ', money(r.incomeAtFullRoster))\nconsole.log('Vs current hourly rate:          ', money(inputs.currentHourlyRate), '->', money(r.effectiveRateAtTarget))\n```\n\n### Worked example output\n\nWith Maya's inputs above the script prints:\n\n```\nBillable capacity (hrs\u002Fmonth):    88.0\nEffective-rate floor (hourly):    $107.95\nRetainer floor price:             $3886.36\nTarget retainer (value-anchored): $4900.00\nMax retainer clients:             2\nUtilization red line (hrs):       70.4\nEffective rate at target:         $136.11\nIncome at full roster:            $9800.00\nVs current hourly rate:           $75.00 -> $136.11\n```\n\nRead it: Maya has 88 billable hours, not 160. Her floor is $107.95\u002Fhr - her current $75\u002Fhr rate was below her own floor, which is exactly why full months still produced only $6,000. The value-anchored retainer lands at $4,900; two clients fill 72 of 88 hours (right at the 80 percent line) and produce $9,800\u002Fmonth at an effective $136\u002Fhr - a raise of over 80 percent in effective rate while working fewer billed hours.\n\n## Concrete thresholds\n\n- Billable share: 50-60 percent of working hours; default 0.55.\n- Value anchor: 1.15-1.5 on the floor, scaled to proof strength.\n- Utilization red line: sold hours at or below 80 percent of billable capacity; sustained above 80 percent triggers raise-your-rates-playbook.\n- Never price at or below the floor; the floor is the walk-away number, not the offer.\n- Re-run the calculator whenever scope, overhead, or the income target changes, and at every rate review.\n\n## Deliverable\n\nThe filled calculator output plus a one-line pricing verdict: floor price, target retainer, max clients, and whether the full roster hits the income target. This validates (or corrects) the tier prices in productized-service-designer.\n\n## Do NOT\n\n- Do not assume 100 percent billable hours; that single error understates the needed rate by nearly half.\n- Do not present the floor price to clients - it is an internal red line, and anchoring on it invites negotiation below it.\n- Do not add a client past the 80 percent red line to hit an income target; raise the price instead.\n- Do not convert the retainer back to an hourly comparison in front of the client (\"that's $136\u002Fhr!\") - the retainer sells an outcome and reserved capacity, and re-hourly-izing it invites hourly objections.\n- Do not skip the value anchor out of modesty; pricing at the bare floor leaves the freelancer with zero margin for a single bad month.\n\n## Quality bar\n\nDone when: every input is sourced or labeled a guess; the target retainer clears the floor with the anchor applied; the roster respects the 80 percent red line; and the full-roster income is compared against the target with an explicit pass\u002Ffail.\n\n## Escalation and neighbors\n\nNot financial or tax advice - an accountant should sanity-check the overhead and income targets against taxes and benefits, which this model treats as inside the target figure. Scope the hours-per-client input in productized-service-designer; contract the price with statement-of-work-writer; when utilization holds above 80 percent, go to raise-your-rates-playbook.\n",{"name":5,"description":7},"main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Fretainer-pricing-calculator",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 retainer-pricing-calculator",{"tool":39,"command":40},"bunx","bunx skills add SkillMedev\u002Fskills --skill retainer-pricing-calculator",{"tool":42,"command":43},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill retainer-pricing-calculator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fretainer-pricing-calculator\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",[],[]]