[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M751ENR1QRV38ZP2S5PPJR8V":3,"skill-same:01M751ENR1QRV38ZP2S5PPJR8V":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},"01M751ENR1QRV38ZP2S5PPJR8V","prompt-to-skill",null,"Converts a prompt a user runs repeatedly into a reusable, paid-quality SKILL.md. Use when someone says \"I keep pasting this prompt\", \"turn this prompt into a skill\", \"package this workflow\", or has a recurring task pattern they want portable across projects and sessions. Do NOT use to author a skill from a capability idea with no existing prompt (use skill-creator) or to restructure an existing SKILL.md (use skill-author).","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\u002Fprompt-to-skill\u002FSKILL.md",[],[],"2026-11-11 18:15:31",false,"---\nname: prompt-to-skill\ndescription: Converts a prompt a user runs repeatedly into a reusable, paid-quality SKILL.md. Use when someone says \"I keep pasting this prompt\", \"turn this prompt into a skill\", \"package this workflow\", or has a recurring task pattern they want portable across projects and sessions. Do NOT use to author a skill from a capability idea with no existing prompt (use skill-creator) or to restructure an existing SKILL.md (use skill-author).\nmetadata:\n  title: \"Prompt to Skill\"\n---\n\n# Prompt to Skill\n\nTakes a prompt someone runs over and over and packages it into a skill any agent can load, discover, and execute consistently. The costly mistake this prevents: transcribing the prompt verbatim into frontmatter, which preserves its padding and loses its triggers - producing a skill that neither fires nor performs.\n\n## Inputs to collect\n\n1. The prompt itself, verbatim - the real text they paste, not a summary of it.\n2. Two or three example runs: the input they gave and the output they liked. Real runs reveal what the prompt actually does versus what it says.\n3. What the prompt gets wrong today - the edits they make to its output every time. Those corrections become skill rules.\n\nIf the user cannot produce an example run, treat the request as a capability idea and hand off to skill-creator.\n\n## Operating procedure\n\n### Step 1 - Extract the pattern\n\nAnswer before writing anything:\n\n1. What is the one-sentence job this prompt does?\n2. What exact inputs does the user provide each run?\n3. What does a successful output look like, structurally?\n4. When would someone reach for this? Name three or more concrete trigger phrases in the user's own words.\n\nIf the prompt handles more than one job, split it: one skill per job. A prompt that \"reviews my code and writes the commit message\" is two skills.\n\n### Step 2 - Distill into the anatomy\n\nMap the prompt onto the standard skill anatomy (see skill-author for the full standard):\n\n- Procedural instructions become the numbered operating procedure.\n- The inputs from Step 1 become the input-elicitation section.\n- Heuristics and rules of thumb become concrete thresholds or if\u002Fthen rules.\n- The best example run becomes the worked artifact - keep one representative example, formatted as a good\u002Fbad pair if the user's corrections show what \"bad\" looked like.\n- The user's recurring corrections become the Do NOT section. These are the highest-value lines in the whole skill: they encode failure modes the base model actually exhibits.\n- The output description becomes the Deliverable section.\n\nDrop prompt padding entirely: \"please\", \"make sure to\", \"always remember\", role-play framing (\"you are an expert…\"). Keep the rule, cut the filler.\n\n### Step 3 - Write the description last\n\nOnly after the body is settled, write the frontmatter description using the WHAT + WHEN + NOT formula (see skill-description-writer), quoting the trigger phrases from Step 1 verbatim. The description is what makes the skill fire; the trigger phrases came from the user, so use their words.\n\n### Step 4 - Verify against the original\n\nRun the user's example input through the new skill mentally (or via skill-tester for a live check). The output must match or beat the output they liked. If it loses something the prompt had, a rule got dropped in distillation - find it and restore it as a rule, not as padding.\n\n## Quality bar\n\nThe conversion is done when: the skill fires on all three trigger phrases; every recurring correction the user reported is encoded as a Do NOT rule; the worked example survives from a real run; the body contains zero lines of prompt padding; and the user could delete their saved prompt without losing anything.\n\n## Do NOT\n\n- Do not transcribe the prompt verbatim - distill it. Padding in a prompt is annoying; padding in a skill is a recurring token tax on every session.\n- Do not invent triggers the user never said. Their real phrasing is the discoverability data; synthetic phrasing misses how they actually ask.\n- Do not merge multiple jobs to keep one file. Two small precise skills beat one vague one.\n- Do not skip the example run. A skill converted without evidence of what \"good output\" means is a guess wearing frontmatter.\n","# Prompt to Skill\n\nTakes a prompt someone runs over and over and packages it into a skill any agent can load, discover, and execute consistently. The costly mistake this prevents: transcribing the prompt verbatim into frontmatter, which preserves its padding and loses its triggers - producing a skill that neither fires nor performs.\n\n## Inputs to collect\n\n1. The prompt itself, verbatim - the real text they paste, not a summary of it.\n2. Two or three example runs: the input they gave and the output they liked. Real runs reveal what the prompt actually does versus what it says.\n3. What the prompt gets wrong today - the edits they make to its output every time. Those corrections become skill rules.\n\nIf the user cannot produce an example run, treat the request as a capability idea and hand off to skill-creator.\n\n## Operating procedure\n\n### Step 1 - Extract the pattern\n\nAnswer before writing anything:\n\n1. What is the one-sentence job this prompt does?\n2. What exact inputs does the user provide each run?\n3. What does a successful output look like, structurally?\n4. When would someone reach for this? Name three or more concrete trigger phrases in the user's own words.\n\nIf the prompt handles more than one job, split it: one skill per job. A prompt that \"reviews my code and writes the commit message\" is two skills.\n\n### Step 2 - Distill into the anatomy\n\nMap the prompt onto the standard skill anatomy (see skill-author for the full standard):\n\n- Procedural instructions become the numbered operating procedure.\n- The inputs from Step 1 become the input-elicitation section.\n- Heuristics and rules of thumb become concrete thresholds or if\u002Fthen rules.\n- The best example run becomes the worked artifact - keep one representative example, formatted as a good\u002Fbad pair if the user's corrections show what \"bad\" looked like.\n- The user's recurring corrections become the Do NOT section. These are the highest-value lines in the whole skill: they encode failure modes the base model actually exhibits.\n- The output description becomes the Deliverable section.\n\nDrop prompt padding entirely: \"please\", \"make sure to\", \"always remember\", role-play framing (\"you are an expert…\"). Keep the rule, cut the filler.\n\n### Step 3 - Write the description last\n\nOnly after the body is settled, write the frontmatter description using the WHAT + WHEN + NOT formula (see skill-description-writer), quoting the trigger phrases from Step 1 verbatim. The description is what makes the skill fire; the trigger phrases came from the user, so use their words.\n\n### Step 4 - Verify against the original\n\nRun the user's example input through the new skill mentally (or via skill-tester for a live check). The output must match or beat the output they liked. If it loses something the prompt had, a rule got dropped in distillation - find it and restore it as a rule, not as padding.\n\n## Quality bar\n\nThe conversion is done when: the skill fires on all three trigger phrases; every recurring correction the user reported is encoded as a Do NOT rule; the worked example survives from a real run; the body contains zero lines of prompt padding; and the user could delete their saved prompt without losing anything.\n\n## Do NOT\n\n- Do not transcribe the prompt verbatim - distill it. Padding in a prompt is annoying; padding in a skill is a recurring token tax on every session.\n- Do not invent triggers the user never said. Their real phrasing is the discoverability data; synthetic phrasing misses how they actually ask.\n- Do not merge multiple jobs to keep one file. Two small precise skills beat one vague one.\n- Do not skip the example run. A skill converted without evidence of what \"good output\" means is a guess wearing frontmatter.\n",{"name":5,"metadata":24,"description":7},{"title":25},"Prompt to Skill","main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Fprompt-to-skill",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 prompt-to-skill",{"tool":41,"command":42},"bunx","bunx skills add SkillMedev\u002Fskills --skill prompt-to-skill",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill prompt-to-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fprompt-to-skill\u002FSKILL.md",true,[],[50,58,65,72,79,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"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).","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",[],[]]