[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7526P2T0WKMHDXS4Q58237T":3,"skill-same:01M7526P2T0WKMHDXS4Q58237T":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":31,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7526P2T0WKMHDXS4Q58237T","win-back-campaign",null,"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.","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\u002Fwin-back-campaign\u002FSKILL.md",[],[],"2026-11-11 18:27:18",false,"---\nname: win-back-campaign\ndescription: 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.\nmetadata:\n  title: \"Win-Back Campaign\"\n---\n\n# Win-Back Campaign\n\nA win-back campaign is a structured last attempt to re-engage users who have stopped responding - not a discount blast. Done correctly it surfaces the real reasons users left and converts a meaningful minority back into active customers; done lazily it burns deliverability, trains the list to expect discounts, and buries the churn signal the business needs. The two costly mistakes this skill prevents: treating all dormant users as one segment, and sending a \"final email\" that turns out not to be final.\n\n## Operating procedure\n\n### Step 1: Gather inputs\n\nCollect before writing anything. Label estimates as guesses.\n\n1. Product usage cadence: daily-use app, monthly subscription, or B2B tool - this sets the dormancy definition.\n2. The activity event that counts as \"alive\" (login, purchase, core action) and the re-activation event that counts as \"won back.\"\n3. Segment sizes at each inactivity depth, and rough LTV per segment (sets the incentive ceiling).\n4. What has shipped since these users left (fuel for Beat 2).\n5. Available incentives: discount, free month, feature unlock, consultation - and what finance will approve.\n\n### Step 2: Define dormancy precisely\n\nDormancy means different things per product. Set a hard threshold: no login in 30 days for a daily-use app, no purchase in 90 days for a monthly subscription, no activity in 60 days for a B2B tool. The threshold determines segment size and message urgency. \"Kind of inactive\" is not a segment.\n\n### Step 3: Tier by inactivity depth\n\nDepth of dormancy predicts winnability, so the offer must scale with it:\n\n- Tier 1 - recently lapsed (past threshold up to ~2x threshold, e.g. 30-60 days for a daily-use app): highest win rate. No incentive yet; lead with value and what is new. Discounting this tier trains users to lapse for coupons.\n- Tier 2 - cooled (roughly 2x-3x threshold, e.g. 60-90 days): value message plus a modest incentive.\n- Tier 3 - cold (beyond ~3x threshold, e.g. 90+ days): the strongest approved incentive, then a genuine goodbye. Win rates here are low single digits; spend accordingly.\n\nRun each tier through the same three-beat structure with tier-appropriate offers.\n\n### Step 4: Structure each tier as three beats\n\n- Beat 1 (day 0): acknowledge the silence without guilt-tripping. Open by naming the gap plainly - the user has not been around lately. Do not pretend nothing happened; users who feel seen re-engage at higher rates than recipients of tone-deaf promotion. Remind them of the specific value they were getting (their data: projects created, money saved), not generic benefits.\n- Beat 2 (day 7): show what is new since they left - a feature, an improvement, a piece of content. Give them a reason the product today is not the product they abandoned.\n- Beat 3 (day 14): the direct ask with the tier's incentive and a real deadline. This is the final email - apply the honesty rule below.\n\n### Step 5: Apply the final-email honesty rule\n\nIf Beat 3 says \"this is our last email,\" it must be true. After Beat 3, suppress non-responders from all marketing sends. A \"final\" email followed by more emails destroys the credibility that makes final emails work, invites spam complaints, and poisons every future campaign. Honesty here is also the mechanism: a true goodbye is the single highest-open email in most win-back sequences.\n\n### Step 6: Choose one strong incentive, not several\n\nOffer one clear thing - a discount, a free month, a feature unlock, a consultation. Multiple small incentives read as desperation and dilute perceived value. Size it to segment LTV: an incentive worth more than roughly one month of expected margin on a won-back user is buying vanity re-activations.\n\n### Step 7: Measure re-activation, then close the loop\n\nSuccess is users returning and completing a meaningful action, not opening an email. Track re-activation rate as the primary metric (open and click rates are diagnostics only). Include a one-question \"what made you leave?\" reply prompt or survey link in Beat 1 - the answers are churn-reduction's raw material. Suppressing non-responders is a win, not a loss: it protects deliverability and keeps the list healthy.\n\n## Worked artifact: three-email sequence, Tier 2 (B2B tool, 60-90 days inactive)\n\n```\nEMAIL 1 - day 0 - subject: \"You've been missed at [FILL: product]\"\n  Open: \"You haven't logged in since [FILL: date] - no guilt, just noticed.\"\n  Body: one concrete value recap using THEIR data (\"your team shipped\n        14 reports in your first two months\").\n  Ask:  one-question reply prompt: \"What pulled you away?\"\n  No incentive.\n\nEMAIL 2 - day 7 - subject: \"What's new since you left\"\n  Body: 2-3 shipped improvements, each one sentence, most relevant first.\n  Ask:  \"Log back in and see\" - deep link straight to the improved feature.\n  Incentive: soft - \"your data and settings are exactly where you left them.\"\n\nEMAIL 3 - day 14 - subject: \"Last email from us - 1 free month if you're in\"\n  Body: plain statement that this is the final email and why.\n  Offer: ONE incentive - 1 free month on re-activation, expires in 7 days.\n  Close: \"If now's not the time, no hard feelings - we'll stop emailing.\"\n  After: non-responders suppressed from marketing sends. Actually.\n```\n\nBad Beat 1 opener: \"We have exciting news and a special offer just for you!\"\nGood Beat 1 opener: \"You haven't been around since March. Fair enough - here's what you were getting from us, and one question: what changed?\"\n\n## Deliverable\n\nProduce a campaign spec containing: the dormancy definition, the three tiers with segment sizes and per-tier offers, the full three-beat copy outline per tier (subjects, openers, asks, incentive, send-day), the suppression rule, and the measurement plan naming the re-activation event.\n\n## Do NOT\n\n- Do NOT send one blast to all dormant users - a 35-day lapser and a 200-day ghost need different messages and different offers.\n- Do NOT open with a discount to recently lapsed users; it trains lapsing and skips the cheaper value-first win.\n- Do NOT stack multiple small incentives; one strong offer, proportional to segment LTV.\n- Do NOT send a fourth email to non-openers; if three beats got nothing, more volume only damages deliverability.\n- Do NOT call an email \"final\" and keep sending - the honesty rule is load-bearing.\n- Do NOT report opens as success; only the re-activation event counts.\n\n## Quality bar\n\nThe spec ships only when: dormancy has a hard numeric threshold per the product's cadence; every tier has a distinct offer that scales with inactivity depth; Beat 1 names the absence plainly and asks why they left; Beat 3 contains exactly one incentive with a real deadline; the suppression rule is written into the automation, not left as intent; and the primary metric is re-activation rate.\n\n## Adjacent jobs\n\nFor recovering an abandoned checkout within hours or days, use abandoned-cart-sequence. For diagnosing why active users cancel and fixing the leak upstream, use churn-reduction (feed it the Beat 1 survey replies). For ongoing lifecycle flows rather than a bounded re-engagement push, use email-drip-builder.\n","# Win-Back Campaign\n\nA win-back campaign is a structured last attempt to re-engage users who have stopped responding - not a discount blast. Done correctly it surfaces the real reasons users left and converts a meaningful minority back into active customers; done lazily it burns deliverability, trains the list to expect discounts, and buries the churn signal the business needs. The two costly mistakes this skill prevents: treating all dormant users as one segment, and sending a \"final email\" that turns out not to be final.\n\n## Operating procedure\n\n### Step 1: Gather inputs\n\nCollect before writing anything. Label estimates as guesses.\n\n1. Product usage cadence: daily-use app, monthly subscription, or B2B tool - this sets the dormancy definition.\n2. The activity event that counts as \"alive\" (login, purchase, core action) and the re-activation event that counts as \"won back.\"\n3. Segment sizes at each inactivity depth, and rough LTV per segment (sets the incentive ceiling).\n4. What has shipped since these users left (fuel for Beat 2).\n5. Available incentives: discount, free month, feature unlock, consultation - and what finance will approve.\n\n### Step 2: Define dormancy precisely\n\nDormancy means different things per product. Set a hard threshold: no login in 30 days for a daily-use app, no purchase in 90 days for a monthly subscription, no activity in 60 days for a B2B tool. The threshold determines segment size and message urgency. \"Kind of inactive\" is not a segment.\n\n### Step 3: Tier by inactivity depth\n\nDepth of dormancy predicts winnability, so the offer must scale with it:\n\n- Tier 1 - recently lapsed (past threshold up to ~2x threshold, e.g. 30-60 days for a daily-use app): highest win rate. No incentive yet; lead with value and what is new. Discounting this tier trains users to lapse for coupons.\n- Tier 2 - cooled (roughly 2x-3x threshold, e.g. 60-90 days): value message plus a modest incentive.\n- Tier 3 - cold (beyond ~3x threshold, e.g. 90+ days): the strongest approved incentive, then a genuine goodbye. Win rates here are low single digits; spend accordingly.\n\nRun each tier through the same three-beat structure with tier-appropriate offers.\n\n### Step 4: Structure each tier as three beats\n\n- Beat 1 (day 0): acknowledge the silence without guilt-tripping. Open by naming the gap plainly - the user has not been around lately. Do not pretend nothing happened; users who feel seen re-engage at higher rates than recipients of tone-deaf promotion. Remind them of the specific value they were getting (their data: projects created, money saved), not generic benefits.\n- Beat 2 (day 7): show what is new since they left - a feature, an improvement, a piece of content. Give them a reason the product today is not the product they abandoned.\n- Beat 3 (day 14): the direct ask with the tier's incentive and a real deadline. This is the final email - apply the honesty rule below.\n\n### Step 5: Apply the final-email honesty rule\n\nIf Beat 3 says \"this is our last email,\" it must be true. After Beat 3, suppress non-responders from all marketing sends. A \"final\" email followed by more emails destroys the credibility that makes final emails work, invites spam complaints, and poisons every future campaign. Honesty here is also the mechanism: a true goodbye is the single highest-open email in most win-back sequences.\n\n### Step 6: Choose one strong incentive, not several\n\nOffer one clear thing - a discount, a free month, a feature unlock, a consultation. Multiple small incentives read as desperation and dilute perceived value. Size it to segment LTV: an incentive worth more than roughly one month of expected margin on a won-back user is buying vanity re-activations.\n\n### Step 7: Measure re-activation, then close the loop\n\nSuccess is users returning and completing a meaningful action, not opening an email. Track re-activation rate as the primary metric (open and click rates are diagnostics only). Include a one-question \"what made you leave?\" reply prompt or survey link in Beat 1 - the answers are churn-reduction's raw material. Suppressing non-responders is a win, not a loss: it protects deliverability and keeps the list healthy.\n\n## Worked artifact: three-email sequence, Tier 2 (B2B tool, 60-90 days inactive)\n\n```\nEMAIL 1 - day 0 - subject: \"You've been missed at [FILL: product]\"\n  Open: \"You haven't logged in since [FILL: date] - no guilt, just noticed.\"\n  Body: one concrete value recap using THEIR data (\"your team shipped\n        14 reports in your first two months\").\n  Ask:  one-question reply prompt: \"What pulled you away?\"\n  No incentive.\n\nEMAIL 2 - day 7 - subject: \"What's new since you left\"\n  Body: 2-3 shipped improvements, each one sentence, most relevant first.\n  Ask:  \"Log back in and see\" - deep link straight to the improved feature.\n  Incentive: soft - \"your data and settings are exactly where you left them.\"\n\nEMAIL 3 - day 14 - subject: \"Last email from us - 1 free month if you're in\"\n  Body: plain statement that this is the final email and why.\n  Offer: ONE incentive - 1 free month on re-activation, expires in 7 days.\n  Close: \"If now's not the time, no hard feelings - we'll stop emailing.\"\n  After: non-responders suppressed from marketing sends. Actually.\n```\n\nBad Beat 1 opener: \"We have exciting news and a special offer just for you!\"\nGood Beat 1 opener: \"You haven't been around since March. Fair enough - here's what you were getting from us, and one question: what changed?\"\n\n## Deliverable\n\nProduce a campaign spec containing: the dormancy definition, the three tiers with segment sizes and per-tier offers, the full three-beat copy outline per tier (subjects, openers, asks, incentive, send-day), the suppression rule, and the measurement plan naming the re-activation event.\n\n## Do NOT\n\n- Do NOT send one blast to all dormant users - a 35-day lapser and a 200-day ghost need different messages and different offers.\n- Do NOT open with a discount to recently lapsed users; it trains lapsing and skips the cheaper value-first win.\n- Do NOT stack multiple small incentives; one strong offer, proportional to segment LTV.\n- Do NOT send a fourth email to non-openers; if three beats got nothing, more volume only damages deliverability.\n- Do NOT call an email \"final\" and keep sending - the honesty rule is load-bearing.\n- Do NOT report opens as success; only the re-activation event counts.\n\n## Quality bar\n\nThe spec ships only when: dormancy has a hard numeric threshold per the product's cadence; every tier has a distinct offer that scales with inactivity depth; Beat 1 names the absence plainly and asks why they left; Beat 3 contains exactly one incentive with a real deadline; the suppression rule is written into the automation, not left as intent; and the primary metric is re-activation rate.\n\n## Adjacent jobs\n\nFor recovering an abandoned checkout within hours or days, use abandoned-cart-sequence. For diagnosing why active users cancel and fixing the leak upstream, use churn-reduction (feed it the Beat 1 survey replies). For ongoing lifecycle flows rather than a bounded re-engagement push, use email-drip-builder.\n",{"name":5,"metadata":24,"description":7},{"title":25},"Win-Back Campaign","main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Fwin-back-campaign",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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SkillMedev\u002Fskills --skill win-back-campaign",{"tool":41,"command":42},"bunx","bunx skills add SkillMedev\u002Fskills --skill win-back-campaign",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill win-back-campaign","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwin-back-campaign\u002FSKILL.md",true,[],[50,59,66,73,80,87],{"skillNo":51,"name":52,"nameZh":53,"description":54,"descriptionZh":55,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"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",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"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",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M75264B53023MWYJM928JACH","weekly-review","Runs a timeboxed weekly review - empty every inbox to a decision, audit every open commitment, and pick the 3-5 outcomes that define next week. Use when someone asks \"walk me through a weekly review\", \"help me plan my week\", \"my task system feels stale and I don't trust it\", or \"I keep dropping commitments\". Do NOT use for setting up the underlying capture-and-organize system itself - use gtd-system instead - or for tracking long-horizon personal goals with an accountability loop - use goals-accountability instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[]]