1 min read
Skill Maintenance Cadence
Skill maintenance turns repeated agent friction into executable skills, routing updates, and generated capability surfaces.
skill-maintenance is daily/manual-local in the current setup. It scans recent sessions for repeated workflows, repeated mistakes, and useful procedures that should not remain one-off chat memory. Source: automations/skill-maintenance.md; No One-Off Work
Promotion Rule
| Signal | Action |
|---|---|
| Same task requested twice | Create or extend the MECE owner skill. |
| Repeated agent failure | Add guardrail, checklist, or doctor step to the owning skill/protocol. |
| New tool enters active stack | Update tool page, active stack, capability routing, and skill if needed. |
| One-off preference with no recurrence | Update wiki/user/config only if durable; otherwise leave session-only. |
Generated Closeout
After skill changes, run the relevant registry/runtime/packs checks:
npm run skills:check
npm run agent-packs:refresh
npm run agent-packs:check
Then rebuild index/qmd and log. Generated wiki/skills/<category>/ source views are not hand-edited.
Timeline
- 2026-07-01 | Rebuilt skill maintenance around repeated-friction promotion, MECE skill ownership, and generated-surface closeout. Source: User request, 2026-07-01
- 2026-06-27 | Skill maintenance now uses generated skill registry plus family synthesis pages instead of one wiki page per skill. Source: User request, 2026-06-27
- 2026-06-24 | Added the reverse catalog invariant to skill maintenance: skill pages cannot exist without executable skills. Source: User request, 2026-06-24
- 2026-05-31 | Skill maintenance cadence from automations table. Source: public wiki expansion, 2026-05-31