skill-improver

1## Activation Contract
2 
3Use 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.
4 
5## Hard Rules
6 
7- Treat `docs/skill-style-guide.md` as the normative style contract when it exists.
8- For installed global skills, use `references/skill-style-guide.md` as the bundled local copy when `docs/skill-style-guide.md` is unavailable.
9- Treat `SKILL.md` as the source of truth; preserve author intent, critical rules, activation semantics, and output requirements.
10- Use `.atl/skill-registry.md` as an index of skill names, triggers, scopes, and exact paths; do not expect generated summaries.
11- Default to audit-only. Modify files only when the user explicitly asks to apply improvements.
12- Never delete meaningful content silently; move long explanation, examples, templates, or schemas into local `references/` or `assets/`.
13- Do not invent triggers, policies, or domain rules. Mark ambiguous cases for human review.
14 
15## Decision Gates
16 
17| Situation | Action |
18| --- | --- |
19| Missing or invalid frontmatter | Fix `name`, quoted one-line `description`, `license`, and `metadata` |
20| Skill reads like tutorial docs | Convert to runtime instructions and move background to `references/` |
21| Body exceeds budget | Preserve rules, move examples/background to supporting files |
22| Branching logic hidden in prose | Convert to a compact decision table |
23…