skill-improver

name	skill-improver
description	Trigger: improve skills, audit skills, refactor skills, skill quality. Audit and upgrade existing LLM-first skills.
license	Apache-2.0
metadata	{"author":"iperez","version":"1.0"}

Activation Contract

Use this skill when asked to audit, refactor, normalize, or improve existing SKILL.md files. Use skill-creator instead when creating a brand-new skill from a reusable pattern.

Hard Rules

• Treat the project skill style guide as the normative style contract when it exists.
• Treat SKILL.md as the source of truth; preserve author intent, critical rules, activation semantics, and output requirements.
• Use .agent/skill-registry.md as an index of skill names, triggers, scopes, and exact paths; do not expect generated summaries.
• Default to audit-only. Modify files only when the user explicitly asks to apply improvements.
• Never delete meaningful content silently; move long explanation, examples, templates, or schemas into local references/ or assets/.
• Do not invent triggers, policies, or domain rules. Mark ambiguous cases for human review.

Decision Gates

Situation	Action
Missing or invalid frontmatter	Fix name, quoted one-line description, license, and metadata
Skill reads like tutorial docs	Convert to runtime instructions and move background to references/
Body exceeds budget	Preserve rules, move examples/background to supporting files
Branching logic hidden in prose	Convert to a compact decision table
Rules conflict or intent is unclear	Report the issue; do not rewrite that rule automatically

Execution Steps

1. Read the project skill style guide if available; otherwise enforce the core LLM-first structure: frontmatter, Activation Contract, Hard Rules, Decision Gates, Execution Steps, Output Contract, References.
2. Read .agent/skill-registry.md; use listed paths to select skills. If missing, scan known skill directories for */SKILL.md.
3. For each selected skill, audit metadata, trigger clarity, section order, body budget, actionability, decision gates, output contract, and local references.
4. Return an audit report grouped by skill with severity and exact proposed changes.
5. In apply mode, edit only safe issues, preserve content, create supporting files when needed, then rerun or request a skill-registry refresh.

Output Contract

Return:

• Skills audited and paths used.
• Issues found, grouped by severity.
• Files changed, if apply mode was requested.
• Registry refresh recommendation when skill metadata or paths changed.
• Ambiguities that need human review.

References

• skill-registry/SKILL.md — how the index is built and consumed.
• skill-creator/SKILL.md — preferred skill when authoring from scratch.