[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M750VFPZFDTFC8EBAB0H2QFG":3,"skill-same:01M750VFPZFDTFC8EBAB0H2QFG":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},"01M750VFPZFDTFC8EBAB0H2QFG","kb-article-writer",null,"Turns a resolved support ticket into a clear, searchable knowledge-base or help center article. Use when someone asks \"write a KB article from this resolved ticket\", \"turn these resolved tickets into help center articles\", or \"write an internal knowledge base article for our support agents\" - converting ticket resolutions into self-service documentation that deflects future tickets. Do NOT use for writing user-facing how-to guides from scratch - use help-documentation 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\u002Fkb-article-writer\u002FSKILL.md",[],[],"2026-11-11 18:11:12",false,"---\nname: kb-article-writer\ndescription: Turns a resolved support ticket into a clear, searchable knowledge-base or help center article. Use when someone asks \"write a KB article from this resolved ticket\", \"turn these resolved tickets into help center articles\", or \"write an internal knowledge base article for our support agents\" - converting ticket resolutions into self-service documentation that deflects future tickets. Do NOT use for writing user-facing how-to guides from scratch - use help-documentation instead.\nmetadata:\n  title: \"Knowledge Base Article Writer\"\n---\n\n# Knowledge Base Article Writer\n\nEvery ticket that gets answered manually is a ticket that could have been self-served. A good knowledge-base article is written for the customer who is about to open a ticket, not for the agent who already knows the answer.\n\n## When to create an article\n\nCreate an article when a ticket has been answered by two or more different customers in the past 60 days, or when a support lead flags a topic as recurring. Do not create articles for one-off edge cases or deprecated features.\n\n## Article structure\n\nUse this structure for every article:\n1. Title: a plain-language question or task the customer is trying to accomplish ('How to reset your password', 'Why was I charged twice'). Use the exact words a customer would type into a search box.\n2. Summary (2-3 sentences): what this article covers and who it is for.\n3. Prerequisites (if applicable): what the customer needs before starting.\n4. Steps or explanation: numbered steps for procedural articles, short paragraphs for conceptual ones. Each step has one action. Use plain language, no internal jargon.\n5. What to do if it does not work: one to three common failure modes and their fixes.\n6. Related articles: two to four links to directly related help content.\n\n## Worked example\n\nThe same resolved ticket (\"customer saw two identical charges; second was an authorization hold\") turned into an article, badly and well:\n\nBad:\n\n> **Title:** Resolving duplicate charge incidents\n> **Opening:** In certain scenarios, the billing subsystem may generate a secondary transaction record when a pre-authorization is initiated prior to capture...\n\nGood:\n\n> **Title:** Why was I charged twice?\n> **Opening:** If you see two identical charges from us, the second one is almost always a temporary authorization hold, not a real charge. It disappears from your statement on its own, usually within 3-5 business days. Here's how to tell the difference and what to do if both charges stay.\n\nThe bad version is titled in the team's internal vocabulary (\"duplicate charge incident\"), opens with system internals, and buries the answer. The good version is titled in the customer's search words, answers the most common scenario in the first two sentences, and only then handles the rarer case.\n\n## Writing rules\n\nWrite in second person ('you', not 'the user'). Use active voice. Keep sentences under 20 words. Screenshots or short screen recordings reduce confusion for procedural articles - include them where possible. Avoid mentioning specific version numbers or dates unless the content is truly version-specific; these make articles go stale.\n\n## SEO and findability\n\nThe article title and first paragraph must contain the keywords the customer would naturally use. Think about synonyms: a customer might search 'cancel subscription', 'end plan', 'stop billing', or 'delete account' for the same workflow - address each variant either in the title or in the first two sentences.\n\n## Review and freshness\n\nSet a review date of 90 days on every new article. Mark articles as 'needs review' when the underlying product or policy changes. Archive articles that have not received a visit in 180 days - they add noise to search results.\n\n## Deliverable\n\nProduce one publish-ready article containing: a search-phrased title, a 2-3 sentence summary, prerequisites where applicable, numbered steps or a short explanation, a \"what to do if it does not work\" section covering one to three failure modes, two to four related-article links, and a 90-day review date.\n\n## Quality bar\n\n- The title uses words a customer would actually type into search, not internal terminology.\n- The answer to the most common scenario appears within the first two sentences of the body.\n- Every procedural step contains exactly one action.\n- No internal jargon, ticket language, or agent-only terminology survives into the article.\n- Synonym variants of the customer's search are covered in the title or the first two sentences.\n\n## What to avoid\n\n- Do not copy-paste the agent's reply verbatim; ticket language is written for one customer, not all customers.\n- Do not bury the answer - lead with the most common scenario, not the edge case.\n","# Knowledge Base Article Writer\n\nEvery ticket that gets answered manually is a ticket that could have been self-served. A good knowledge-base article is written for the customer who is about to open a ticket, not for the agent who already knows the answer.\n\n## When to create an article\n\nCreate an article when a ticket has been answered by two or more different customers in the past 60 days, or when a support lead flags a topic as recurring. Do not create articles for one-off edge cases or deprecated features.\n\n## Article structure\n\nUse this structure for every article:\n1. Title: a plain-language question or task the customer is trying to accomplish ('How to reset your password', 'Why was I charged twice'). Use the exact words a customer would type into a search box.\n2. Summary (2-3 sentences): what this article covers and who it is for.\n3. Prerequisites (if applicable): what the customer needs before starting.\n4. Steps or explanation: numbered steps for procedural articles, short paragraphs for conceptual ones. Each step has one action. Use plain language, no internal jargon.\n5. What to do if it does not work: one to three common failure modes and their fixes.\n6. Related articles: two to four links to directly related help content.\n\n## Worked example\n\nThe same resolved ticket (\"customer saw two identical charges; second was an authorization hold\") turned into an article, badly and well:\n\nBad:\n\n> **Title:** Resolving duplicate charge incidents\n> **Opening:** In certain scenarios, the billing subsystem may generate a secondary transaction record when a pre-authorization is initiated prior to capture...\n\nGood:\n\n> **Title:** Why was I charged twice?\n> **Opening:** If you see two identical charges from us, the second one is almost always a temporary authorization hold, not a real charge. It disappears from your statement on its own, usually within 3-5 business days. Here's how to tell the difference and what to do if both charges stay.\n\nThe bad version is titled in the team's internal vocabulary (\"duplicate charge incident\"), opens with system internals, and buries the answer. The good version is titled in the customer's search words, answers the most common scenario in the first two sentences, and only then handles the rarer case.\n\n## Writing rules\n\nWrite in second person ('you', not 'the user'). Use active voice. Keep sentences under 20 words. Screenshots or short screen recordings reduce confusion for procedural articles - include them where possible. Avoid mentioning specific version numbers or dates unless the content is truly version-specific; these make articles go stale.\n\n## SEO and findability\n\nThe article title and first paragraph must contain the keywords the customer would naturally use. Think about synonyms: a customer might search 'cancel subscription', 'end plan', 'stop billing', or 'delete account' for the same workflow - address each variant either in the title or in the first two sentences.\n\n## Review and freshness\n\nSet a review date of 90 days on every new article. Mark articles as 'needs review' when the underlying product or policy changes. Archive articles that have not received a visit in 180 days - they add noise to search results.\n\n## Deliverable\n\nProduce one publish-ready article containing: a search-phrased title, a 2-3 sentence summary, prerequisites where applicable, numbered steps or a short explanation, a \"what to do if it does not work\" section covering one to three failure modes, two to four related-article links, and a 90-day review date.\n\n## Quality bar\n\n- The title uses words a customer would actually type into search, not internal terminology.\n- The answer to the most common scenario appears within the first two sentences of the body.\n- Every procedural step contains exactly one action.\n- No internal jargon, ticket language, or agent-only terminology survives into the article.\n- Synonym variants of the customer's search are covered in the title or the first two sentences.\n\n## What to avoid\n\n- Do not copy-paste the agent's reply verbatim; ticket language is written for one customer, not all customers.\n- Do not bury the answer - lead with the most common scenario, not the edge case.\n",{"name":5,"metadata":24,"description":7},{"title":25},"Knowledge Base Article Writer","main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Fkb-article-writer",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 kb-article-writer",{"tool":41,"command":42},"bunx","bunx skills add SkillMedev\u002Fskills --skill kb-article-writer",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill kb-article-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fkb-article-writer\u002FSKILL.md",true,[],[50,60,67,74,81,88],{"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":59},"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":59},"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":59},"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":59},"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":59},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":59},"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",[],[]]