skill-improver

## 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 `docs/skill-style-guide.md` as the normative style contract when it exists. - For installed global skills, use `references/skill-style-guide.md` as the bundled local copy when `docs/skill-style-guide.md` is unavailable. - Treat `SKILL.md` as the source of truth; preserve author intent, critical rules, activation semantics, and output requirements. - Use `.atl/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...