[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72A6N7X6SSSCJN95VDAVD6R":3,"skill-same:01M72A6N7X6SSSCJN95VDAVD6R":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":13,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M72A6N7X6SSSCJN95VDAVD6R","skill-improver",null,"Iteratively improve a Claude Code skill using the skill-reviewer agent until it meets quality standards. Use when improving a skill with multiple quality issues, iterating on a new skill until it meets standards, or automated fix-review cycles instead of manual editing.","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fantigravity\u002Fskill-improver\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: skill-improver\ndescription: \"Iteratively improve a Claude Code skill using the skill-reviewer agent until it meets quality standards. Use when improving a skill with multiple quality issues, iterating on a new skill until it meets standards, or automated fix-review cycles instead of manual editing.\"\nrisk: unknown\nsource: community\n---\n\n# Skill Improvement Methodology\n\nIteratively improve a Claude Code skill using the skill-reviewer agent until it meets quality standards.\n\n## Prerequisites\n\nRequires the `plugin-dev` plugin which provides the `skill-reviewer` agent.\n\nVerify it's enabled: run `\u002Fplugins` — `plugin-dev` should appear in the list. If missing, install from the Trail of Bits plugin repository.\n\n## Core Loop\n\n1. **Review** - Call skill-reviewer on the target skill\n2. **Categorize** - Parse issues by severity\n3. **Fix** - Address critical and major issues\n4. **Evaluate** - Check minor issues for validity before fixing\n5. **Repeat** - Continue until quality bar is met\n\n## When to Use\n- Improving a skill with multiple quality issues\n- Iterating on a new skill until it meets standards\n- Automated fix-review cycles instead of manual editing\n- Consistent quality enforcement across skills\n\n## When NOT to Use\n\n- **One-time review**: Use `\u002Fskill-reviewer` directly instead\n- **Quick single fixes**: Edit the file directly\n- **Non-skill files**: Only works on SKILL.md files\n- **Experimental skills**: Manual iteration gives more control during exploration\n\n## Issue Categorization\n\n### Critical Issues (MUST fix immediately)\n\nThese block skill loading or cause runtime failures:\n\n- Missing required frontmatter fields (name, description) — Claude cannot index or trigger the skill\n- Invalid YAML frontmatter syntax — Parsing fails, skill won't load\n- Referenced files that don't exist — Runtime errors when Claude follows links\n- Broken file paths — Same as above, leads to tool failures\n\n### Major Issues (MUST fix)\n\nThese significantly degrade skill effectiveness:\n\n- Weak or vague trigger descriptions — Claude may not recognize when to use the skill\n- Wrong writing voice (second person \"you\" instead of imperative) — Inconsistent with Claude's execution model\n- SKILL.md exceeds 500 lines without using references\u002F — Overloads context, reduces comprehension\n- Missing \"When to Use\" or \"When NOT to Use\" sections — Required by project quality standards\n- Description doesn't specify when to trigger — Skill may never be selected\n\n### Minor Issues (Evaluate before fixing)\n\nThese are polish items that may or may not improve the skill:\n\n- Subjective style preferences — Reviewer may have different taste than author\n- Optional enhancements — May add complexity without proportional value\n- \"Nice to have\" improvements — Consider cost-benefit before implementing\n- Formatting suggestions — Often valid but low impact\n\n## Minor Issue Evaluation\n\nBefore implementing any minor issue fix, evaluate:\n\n1. **Is this a genuine improvement?** - Does it add real value or just satisfy a preference?\n2. **Could this be a false positive?** - Is the reviewer misunderstanding context?\n3. **Would this actually help Claude use the skill?** - Focus on functional improvements\n\nOnly implement minor fixes that are clearly beneficial. Skill-reviewer may produce false positives.\n\n## Invoking skill-reviewer\n\nUse the skill-reviewer agent from the plugin-dev plugin. Request a review by asking Claude to:\n\n> Review the skill at [SKILL_PATH] using the plugin-dev:skill-reviewer agent. Provide a detailed quality assessment with issues categorized by severity.\n\nReplace `[SKILL_PATH]` with the absolute path to the skill directory (e.g., `\u002Fpath\u002Fto\u002Fplugins\u002Fmy-plugin\u002Fskills\u002Fmy-skill`).\n\n## Example Fix Cycle\n\n**Iteration 1 — skill-reviewer output:**\n```text\nCritical: SKILL.md:1 - Missing required 'name' field in frontmatter\nMajor: SKILL.md:3 - Description uses second person (\"you should use\")\nMajor: Missing \"When NOT to Use\" section\nMinor: Line 45 is verbose\n```\n\n**Fixes applied:**\n- Added name field to frontmatter\n- Rewrote description in third person\n- Added \"When NOT to Use\" section\n\n**Iteration 2 — run skill-reviewer again to verify fixes:**\n```text\nMinor: Line 45 is verbose\n```\n\n**Minor issue evaluation:**\nLine 45 communicates effectively as-is. The verbosity provides useful context. Skip.\n\n**All critical\u002Fmajor issues resolved. Output the completion marker:**\n```\n\u003Cskill-improvement-complete>\n```\n\nNote: The marker MUST appear in the output. Statements like \"quality bar met\" or \"looks good\" will NOT stop the loop.\n\n## Completion Criteria\n\n**CRITICAL**: The stop hook ONLY checks for the explicit marker below. No other signal will terminate the loop.\n\nOutput this marker when done:\n\n```\n\u003Cskill-improvement-complete>\n```\n\n**When to output the marker:**\n\n1. **skill-reviewer reports \"Pass\"** or **no issues found** → output marker immediately\n2. **All critical and major issues are fixed** AND you've verified the fixes → output marker\n3. **Remaining issues are only minor** AND you've evaluated them as false positives or not worth fixing → output marker\n\n**When NOT to output the marker:**\n\n- Any critical issue remains unfixed\n- Any major issue remains unfixed\n- You haven't run skill-reviewer to verify your fixes worked\n\nThe marker is the ONLY way to complete the loop. Natural language like \"looks good\" or \"quality bar met\" will NOT stop the loop.\n\n## Rationalizations to Reject\n\n- \"I'll just mark it complete and come back later\" - Fix issues now\n- \"This minor issue seems wrong, I'll skip all of them\" - Evaluate each one individually\n- \"The reviewer is being too strict\" - The quality bar exists for a reason\n- \"It's good enough\" - If there are major issues, it's not good enough\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Skill Improvement Methodology\n\nIteratively improve a Claude Code skill using the skill-reviewer agent until it meets quality standards.\n\n## Prerequisites\n\nRequires the `plugin-dev` plugin which provides the `skill-reviewer` agent.\n\nVerify it's enabled: run `\u002Fplugins` — `plugin-dev` should appear in the list. If missing, install from the Trail of Bits plugin repository.\n\n## Core Loop\n\n1. **Review** - Call skill-reviewer on the target skill\n2. **Categorize** - Parse issues by severity\n3. **Fix** - Address critical and major issues\n4. **Evaluate** - Check minor issues for validity before fixing\n5. **Repeat** - Continue until quality bar is met\n\n## When to Use\n- Improving a skill with multiple quality issues\n- Iterating on a new skill until it meets standards\n- Automated fix-review cycles instead of manual editing\n- Consistent quality enforcement across skills\n\n## When NOT to Use\n\n- **One-time review**: Use `\u002Fskill-reviewer` directly instead\n- **Quick single fixes**: Edit the file directly\n- **Non-skill files**: Only works on SKILL.md files\n- **Experimental skills**: Manual iteration gives more control during exploration\n\n## Issue Categorization\n\n### Critical Issues (MUST fix immediately)\n\nThese block skill loading or cause runtime failures:\n\n- Missing required frontmatter fields (name, description) — Claude cannot index or trigger the skill\n- Invalid YAML frontmatter syntax — Parsing fails, skill won't load\n- Referenced files that don't exist — Runtime errors when Claude follows links\n- Broken file paths — Same as above, leads to tool failures\n\n### Major Issues (MUST fix)\n\nThese significantly degrade skill effectiveness:\n\n- Weak or vague trigger descriptions — Claude may not recognize when to use the skill\n- Wrong writing voice (second person \"you\" instead of imperative) — Inconsistent with Claude's execution model\n- SKILL.md exceeds 500 lines without using references\u002F — Overloads context, reduces comprehension\n- Missing \"When to Use\" or \"When NOT to Use\" sections — Required by project quality standards\n- Description doesn't specify when to trigger — Skill may never be selected\n\n### Minor Issues (Evaluate before fixing)\n\nThese are polish items that may or may not improve the skill:\n\n- Subjective style preferences — Reviewer may have different taste than author\n- Optional enhancements — May add complexity without proportional value\n- \"Nice to have\" improvements — Consider cost-benefit before implementing\n- Formatting suggestions — Often valid but low impact\n\n## Minor Issue Evaluation\n\nBefore implementing any minor issue fix, evaluate:\n\n1. **Is this a genuine improvement?** - Does it add real value or just satisfy a preference?\n2. **Could this be a false positive?** - Is the reviewer misunderstanding context?\n3. **Would this actually help Claude use the skill?** - Focus on functional improvements\n\nOnly implement minor fixes that are clearly beneficial. Skill-reviewer may produce false positives.\n\n## Invoking skill-reviewer\n\nUse the skill-reviewer agent from the plugin-dev plugin. Request a review by asking Claude to:\n\n> Review the skill at [SKILL_PATH] using the plugin-dev:skill-reviewer agent. Provide a detailed quality assessment with issues categorized by severity.\n\nReplace `[SKILL_PATH]` with the absolute path to the skill directory (e.g., `\u002Fpath\u002Fto\u002Fplugins\u002Fmy-plugin\u002Fskills\u002Fmy-skill`).\n\n## Example Fix Cycle\n\n**Iteration 1 — skill-reviewer output:**\n```text\nCritical: SKILL.md:1 - Missing required 'name' field in frontmatter\nMajor: SKILL.md:3 - Description uses second person (\"you should use\")\nMajor: Missing \"When NOT to Use\" section\nMinor: Line 45 is verbose\n```\n\n**Fixes applied:**\n- Added name field to frontmatter\n- Rewrote description in third person\n- Added \"When NOT to Use\" section\n\n**Iteration 2 — run skill-reviewer again to verify fixes:**\n```text\nMinor: Line 45 is verbose\n```\n\n**Minor issue evaluation:**\nLine 45 communicates effectively as-is. The verbosity provides useful context. Skip.\n\n**All critical\u002Fmajor issues resolved. Output the completion marker:**\n```\n\u003Cskill-improvement-complete>\n```\n\nNote: The marker MUST appear in the output. Statements like \"quality bar met\" or \"looks good\" will NOT stop the loop.\n\n## Completion Criteria\n\n**CRITICAL**: The stop hook ONLY checks for the explicit marker below. No other signal will terminate the loop.\n\nOutput this marker when done:\n\n```\n\u003Cskill-improvement-complete>\n```\n\n**When to output the marker:**\n\n1. **skill-reviewer reports \"Pass\"** or **no issues found** → output marker immediately\n2. **All critical and major issues are fixed** AND you've verified the fixes → output marker\n3. **Remaining issues are only minor** AND you've evaluated them as false positives or not worth fixing → output marker\n\n**When NOT to output the marker:**\n\n- Any critical issue remains unfixed\n- Any major issue remains unfixed\n- You haven't run skill-reviewer to verify your fixes worked\n\nThe marker is the ONLY way to complete the loop. Natural language like \"looks good\" or \"quality bar met\" will NOT stop the loop.\n\n## Rationalizations to Reject\n\n- \"I'll just mark it complete and come back later\" - Fix issues now\n- \"This minor issue seems wrong, I'll skip all of them\" - Evaluate each one individually\n- \"The reviewer is being too strict\" - The quality bar exists for a reason\n- \"It's good enough\" - If there are major issues, it's not good enough\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":23,"source":24,"description":7},"unknown","community","main","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Fantigravity\u002Fskill-improver","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Sansar35\u002Fclaude-agent --skill skill-improver",{"tool":37,"command":38},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill skill-improver",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill skill-improver","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fantigravity\u002Fskill-improver\u002FSKILL.md",true,[],[46,53,60,67,74,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]