skill-improve

Run static and category test suites, diagnose failures, and apply targeted edits.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/WindXRan/y3td --skill skill-improve-windxran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-improve
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/skill-improve
Command: npx skills add https://github.com/WindXRan/y3td --skill skill-improve-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the time and risk of improving an existing skill by guiding an AI through a controlled test → diagnose → targeted edit → retest loop, then keeping only changes that improve the score.

Core Features & Use Cases

  • Automated improvement loop: Runs static and (optionally) category tests to measure current quality, then iterates with a proposed targeted fix.
  • Deterministic, scoped edits: Identifies exact gaps tied to specific failing/warning checks and asks permission before writing changes.
  • Score-based keep-or-revert: Re-runs tests after edits and can revert via git if the combined score does not improve.

Quick Start

Run the improvement loop for the tech-debt skill by issuing: /skill-improve skill-improve

Frequently Asked Questions about skill-improve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve an existing skill using automated testing?

You can improve an existing skill by running a test-fix-retest workflow that executes static and category test suites, diagnoses failures, applies targeted file edits, and reverts changes if the combined failure score does not improve.

How does the test-fix-retest workflow diagnose and fix failing skill checks?

The test-fix-retest workflow diagnoses failures by parsing exact check gaps from test suites, proposing targeted file edits to fix those specific gaps, and asking permission before writing changes to the skill file.

Can I use skill improvement workflows to fix YAML frontmatter and static check warnings?

Yes, the skill improvement workflow runs static checks that validate YAML frontmatter and other structural requirements, then proposes scoped edits to resolve those specific warnings before re-testing the skill.

What is the best way to ensure code rewrites for skills actually improve quality?

The best way is a score-based keep-or-revert decision process that re-runs tests after edits and uses git revert to discard changes if the combined failure count does not decrease, ensuring only measurable quality gains are kept.

Does the skill improvement process require git for reverting failed edits?

Git is required for the revert mechanism, which discards proposed file edits if the combined test failure count does not improve after re-running static and category test suites on the modified skill.

What are the limitations of automated skill improvement loops?

Automated skill improvement loops are limited to skills located at .claude/skills/[name]/SKILL.md and rely on test failure counts to judge quality, meaning edits that pass tests but degrade overall behavior may still be kept.