skill-managerlisted

# skill-manager — the one skill that is aware of all the others Individual lessons enter through the evolve procedure, one reviewed diff at a time. Somebody still has to see the whole genome: whether the pieces are at the right altitude, whether gaps and corpses are accumulating. That somebody is this skill, and the periodic pass runs with FRESH context — the writer of a skill never grades it. ## Nested-skill architecture (policy, decided 2026-07-11) - **Few top-level skills, lazy references inside.** A skill's body is the always-loaded front door; variants and less-common procedures live in `references/` files loaded only when their trigger row matches. Do not rely on separate sibling skills auto-triggering for sub-procedures. - **Hard cap: 10 top-level skills; prefer 5-7.** At the cap, adding a skill requires first consolidating two related ones (merge into core + references). Current top-level set (4): `workflow`, `skill-manager`, `socials`, `bootstrap`. - **Portability.** Embed the external knowledge the genome needs (e.g. authoring standards in `references/authoring.md`) so any coding agent operating this repo has it — never depend on a specific tool's plugin being installed. ## The structural rules (load-bearing, not style) - **Skills exist per task-shape, never per incident.** A recurring bug becomes one appended procedure in an existing skill, not a new skill. - **Variants of one shape are `references/` inside one skill** (`bootstrap` + `referen