Personal Skills Taxonomy
Kevin-owned executable skills live in the shared
skills/{engineering,productivity,personal,misc}/<slug>/SKILL.mdtree, then project into every harness through the generated runtime index.
Use this page when installing, editing, or routing a default Kevin skill. For Dedalus-origin skills, open Dedalus Skills Taxonomy first. For generated pack/docs boundaries, open Agent Docs System Map.
Current Model
The old mental model was "personal skills live under skills/personal." The current model is broader: category source directories are the source of truth, while runtime consumers read a generated flat projection.
| Layer | Path | Job |
|---|---|---|
| Editable source | skills/{engineering,productivity,personal,misc}/<slug>/SKILL.md |
Executable skill body and frontmatter. |
| Draft and retired source | skills/in-progress/, skills/deprecated/ |
Excluded or clearly marked before promotion. |
| Runtime projection | skills/.runtime/all/<slug> |
Flat symlink index for Cursor, Codex, Claude, and .agents. |
| Generated wiki registry | Skill Registry and wiki/skills/<category>/ |
Browseable inventory generated from source. |
| Readable synthesis | wiki/concepts/*-skills.md |
Family-level routing, failure modes, and ownership. |
Do not recreate one wiki article per executable skill. Generated registry rows and family synthesis pages are the reader-facing layer.
Install Or Edit Flow
- Search first with Security and Review Skills,
rg, orqmd search. - Extend an existing owner skill when the work type already exists.
- Add or edit the source
SKILL.mdin the right category directory. - Run the relevant quality gate for the skill body.
- Regenerate skill surfaces with
npm run skill-registry. - Verify runtime projections with
npm run skills:checkorbash scripts/sync-skills.sh --check. - If routing changed, run
npm run routing-doctor.
npx skills add <source> -g -y can install external skills, but the durable wiki shape still needs source placement, registry generation, and a family route.
MECE Owner Rule
Every recurring work type should have exactly one owner skill. If two skills can both claim the same task, merge the procedure or make the router explicit. If no skill owns the task and Kevin will ask for it again, prototype once, then codify through Browser Testing Skills.
Codex, Cursor, Claude, and other harnesses can have different loader syntax. They should not have different skill truth.
Closeout
After changing skill source, run npm run skill-registry, npm run skills:check, npm run routing-doctor, npm run build-index, and qmd update && qmd embed. If generated agent packs mention the changed skill route, run npm run agent-packs:refresh and npm run agent-packs:check.
Timeline
- 2026-07-01 | Reframed personal skills as Kevin's shared category-source taxonomy with generated runtime projections, registry surfaces, and MECE owner rules. Source: User request, 2026-07-01
- 2026-06-27 | Replaced one-page-per-skill catalog guidance with generated registry plus family synthesis pages. Source: User request, 2026-06-27
- 2026-06-24 | Documented the bidirectional skill/catalog contract for portable setup. Source: User request, 2026-06-24
- 2026-05-31 | Agent doc created from AGENTS.md skills taxonomy. Source: AGENTS.md, 2026-05-31