[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M751SCDPP5PVDHEXZP9ZYJ4S":3,"skill-same:01M751SCDPP5PVDHEXZP9ZYJ4S":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},"01M751SCDPP5PVDHEXZP9ZYJ4S","skill-tester",null,"Empirically tests a skill with subagent scenarios to verify it fires on the right prompts, stays silent on the wrong ones, and performs its job when loaded. Use when validating a new or modified SKILL.md before publishing - \"test this skill\", \"does this trigger correctly\", \"verify the skill works\". Do NOT use to statically grade or rewrite skill quality (use skill-auditor) - this runs live behavioral tests.","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\u002Fskill-tester\u002FSKILL.md",[],[],"2026-11-11 18:22:23",false,"---\nname: skill-tester\ndescription: Empirically tests a skill with subagent scenarios to verify it fires on the right prompts, stays silent on the wrong ones, and performs its job when loaded. Use when validating a new or modified SKILL.md before publishing - \"test this skill\", \"does this trigger correctly\", \"verify the skill works\". Do NOT use to statically grade or rewrite skill quality (use skill-auditor) - this runs live behavioral tests.\nmetadata:\n  title: \"Skill Tester\"\n---\n\n# Skill Tester\n\nVerifies empirically that a skill fires on the right prompts, stays silent on unrelated ones, and produces the behavior its body promises when loaded. Static review (skill-auditor) judges the text; this skill judges the behavior. A skill that reads perfectly and never fires is still broken.\n\n## Inputs to collect\n\n1. The SKILL.md under test, from source.\n2. The neighbor skills whose territory borders it (for negative scenarios).\n3. The intended user phrasing, if the author collected any - real phrasing makes the best positive scenarios.\n\n## Operating procedure\n\n### Step 1 - Write the scenario matrix\n\nFor each skill, write at minimum:\n\n- **Three positive trigger scenarios** - prompts that must fire the skill. Paraphrase the description's WHEN clause in different words; do not copy it verbatim, or you test string matching instead of routing.\n- **Two negative trigger scenarios** - adjacent tasks the skill must NOT hijack. The best negatives are the named neighbors from the description's NOT clause; the second-best are near-miss requests one topic over.\n- **Two performance scenarios** - full realistic requests where you will judge the output against the skill's own quality bar and deliverable sections.\n\nExample for a database-migration skill:\n- Positive: \"add a nullable column to a live orders table without downtime\"\n- Positive: \"we need to backfill a new field across 40M rows\"\n- Negative: \"design the schema for a new app\" (neighbor: database-schema)\n- Negative: \"why is this query slow\" (neighbor: sql-query-optimizer)\n\n### Step 2 - Run trigger tests\n\nLaunch each scenario as a fresh subagent with the skill (and its neighbors, when testing collisions) available. Record for each: did the skill load, did anything else load instead, did the agent act on the skill's instructions. Run positives and negatives in the same batch so conditions match.\n\n### Step 3 - Run performance tests\n\nFor the two performance scenarios, judge the output against the skill's own contract:\n\n- Did the agent follow the operating procedure in order?\n- Did it elicit the inputs the skill says to collect, instead of assuming them?\n- Does the output contain the Deliverable the skill promises?\n- Does the output violate anything in the skill's Do NOT section?\n- If the skill contains a calculator or template, was it actually used, and does the calculator run and produce the documented output?\n\n### Step 4 - Iterate to green\n\n- Trigger failures → revise the description's WHEN clause; add the missing trigger terms or strengthen the NOT clause (hand to skill-description-writer if the fix is description-only).\n- Performance failures → revise the body section for the failing behavior; a procedure the agent skipped is usually a procedure stated as a principle instead of a numbered step.\n- Re-run the failing scenario after each revision. Do not publish until all scenarios pass.\n\n## Pass criteria\n\n- All positive scenarios fire the skill; all negative scenarios do not.\n- No collision: neighbors stay silent on this skill's positives and vice versa.\n- Both performance outputs satisfy the skill's own quality bar and include its deliverable.\n- Any embedded calculator runs as documented; any template's FILL fields survive into the output.\n- No frontmatter parsing errors.\n\n## Deliverable\n\nA test report: the scenario matrix with pass\u002Ffail per scenario, the observed failure behavior for each fail (what fired instead, which step was skipped), and the specific revision made or recommended for each failure.\n\n## Do NOT\n\n- Do not test with the description's own words as the positive prompt - that validates string overlap, not routing.\n- Do not skip negative scenarios; a skill that fires on everything looks great in positive-only testing and is a defect in production.\n- Do not judge performance by general output quality; judge against the skill's own quality bar and deliverable, or the test cannot fail meaningfully.\n- Do not rewrite the skill wholesale from inside a test run - report, fix the specific failing clause, re-run. Structural rewrites go to skill-auditor.\n","# Skill Tester\n\nVerifies empirically that a skill fires on the right prompts, stays silent on unrelated ones, and produces the behavior its body promises when loaded. Static review (skill-auditor) judges the text; this skill judges the behavior. A skill that reads perfectly and never fires is still broken.\n\n## Inputs to collect\n\n1. The SKILL.md under test, from source.\n2. The neighbor skills whose territory borders it (for negative scenarios).\n3. The intended user phrasing, if the author collected any - real phrasing makes the best positive scenarios.\n\n## Operating procedure\n\n### Step 1 - Write the scenario matrix\n\nFor each skill, write at minimum:\n\n- **Three positive trigger scenarios** - prompts that must fire the skill. Paraphrase the description's WHEN clause in different words; do not copy it verbatim, or you test string matching instead of routing.\n- **Two negative trigger scenarios** - adjacent tasks the skill must NOT hijack. The best negatives are the named neighbors from the description's NOT clause; the second-best are near-miss requests one topic over.\n- **Two performance scenarios** - full realistic requests where you will judge the output against the skill's own quality bar and deliverable sections.\n\nExample for a database-migration skill:\n- Positive: \"add a nullable column to a live orders table without downtime\"\n- Positive: \"we need to backfill a new field across 40M rows\"\n- Negative: \"design the schema for a new app\" (neighbor: database-schema)\n- Negative: \"why is this query slow\" (neighbor: sql-query-optimizer)\n\n### Step 2 - Run trigger tests\n\nLaunch each scenario as a fresh subagent with the skill (and its neighbors, when testing collisions) available. Record for each: did the skill load, did anything else load instead, did the agent act on the skill's instructions. Run positives and negatives in the same batch so conditions match.\n\n### Step 3 - Run performance tests\n\nFor the two performance scenarios, judge the output against the skill's own contract:\n\n- Did the agent follow the operating procedure in order?\n- Did it elicit the inputs the skill says to collect, instead of assuming them?\n- Does the output contain the Deliverable the skill promises?\n- Does the output violate anything in the skill's Do NOT section?\n- If the skill contains a calculator or template, was it actually used, and does the calculator run and produce the documented output?\n\n### Step 4 - Iterate to green\n\n- Trigger failures → revise the description's WHEN clause; add the missing trigger terms or strengthen the NOT clause (hand to skill-description-writer if the fix is description-only).\n- Performance failures → revise the body section for the failing behavior; a procedure the agent skipped is usually a procedure stated as a principle instead of a numbered step.\n- Re-run the failing scenario after each revision. Do not publish until all scenarios pass.\n\n## Pass criteria\n\n- All positive scenarios fire the skill; all negative scenarios do not.\n- No collision: neighbors stay silent on this skill's positives and vice versa.\n- Both performance outputs satisfy the skill's own quality bar and include its deliverable.\n- Any embedded calculator runs as documented; any template's FILL fields survive into the output.\n- No frontmatter parsing errors.\n\n## Deliverable\n\nA test report: the scenario matrix with pass\u002Ffail per scenario, the observed failure behavior for each fail (what fired instead, which step was skipped), and the specific revision made or recommended for each failure.\n\n## Do NOT\n\n- Do not test with the description's own words as the positive prompt - that validates string overlap, not routing.\n- Do not skip negative scenarios; a skill that fires on everything looks great in positive-only testing and is a defect in production.\n- Do not judge performance by general output quality; judge against the skill's own quality bar and deliverable, or the test cannot fail meaningfully.\n- Do not rewrite the skill wholesale from inside a test run - report, fix the specific failing clause, re-run. Structural rewrites go to skill-auditor.\n",{"name":5,"metadata":24,"description":7},{"title":25},"Skill Tester","main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Fskill-tester",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 skill-tester",{"tool":41,"command":42},"bunx","bunx skills add SkillMedev\u002Fskills --skill skill-tester",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill skill-tester","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-tester\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",[],[]]