add-skilllisted

The meta-skill: it makes the repository's skill-authoring standard executable. Used by humans adding capabilities and by `/evolve` when a learning is procedure-shaped. ## Hold in mind 1. Skill bodies load on demand and may be long (the platform's own guidance: keep `SKILL.md` under 500 lines). Priming blocks may not — a handful of invariants, not a syllabus. 2. `description` + `when_to_use` are the only always-loaded parts and the model's trigger surface: action first, then the "Use when …" situations — ≤50 words total. The platform truncates the listing at 1,536 characters, but that is where rendering stops, not a target: every description taxes every future session. 3. Write for a model with judgment. Encode what this repo does differently — its gotchas, conventions, and irreversible steps — and leave general competence alone; an instruction that describes how to think is the first thing to cut. 4. Don't shadow built-ins (`init`, `review`, `verify`, `run`, `code-review`, `security-review`) or existing janus skills — the platform owns those mechanisms. 5. A skill is a permanent tax on every future session. Retire before adding; `/context`'s Skills row reports what the listing actually costs. ## Steps 1. Confirm the skill deserves to exist: it's a *procedure* (multi-step, repeatable), not a *fact* (belongs in CLAUDE.md), not a *path-local rule* (belongs in `.claude/rules/<topic>.md` with `paths:` frontmatter), and not a one-off. Check the public agent-skills library (gith