skill-improver

Run the skill-improver audit, which reads the style guide and skill registry, then checks each skill's frontmatter, section order, body budget, and decision gates. It returns a report grouped by skill with severity levels and exact proposed changes.

A SKILL.md should contain frontmatter with name, description, license, and metadata, followed by Activation Contract, Hard Rules, Decision Gates, Execution Steps, Output Contract, and References sections. The body should target 180-450 tokens with a hard maximum of 1000.

No, the default mode is audit-only and produces a report without changing files. Modifications happen only when the user explicitly requests apply mode, and even then only safe issues are edited while meaningful content is preserved.

Use skill-improver when auditing, refactoring, or normalizing existing SKILL.md files. Use skill-creator when building a brand-new skill from a reusable pattern, since the improver treats existing files as the source of truth.

Conflicting rules or unclear intent are reported as ambiguities for human review rather than rewritten automatically. The skill never invents triggers, policies, or domain rules during refactoring.