Cockpit SkillOps
When to use
- After completing a meaningful task or slice.
- Before reporting final
outcome="done"for autopilot tasks that require SkillOps evidence.
Required sequence
node scripts/skillops.mjs debrief --skills <skill-a,skill-b> --title "What changed"Fast path when the learning is already clear:node scripts/skillops.mjs debrief --skills <skill-a,skill-b> --skill-update "skill-a:1-line rule" --title "What changed"node scripts/skillops.mjs distillnode scripts/skillops.mjs lint
Evidence contract
- Include all three commands in
testsToRun. - Include the debrief log markdown path in
artifacts(under.codex/skill-ops/logs/...). distillis non-durable. Do not claim it patched durable skill files.- Raw SkillOps logs are local evidence only.
queuedlogs are non-blocking runtime evidence, not removable dirt; runtime retires them only after processed mark-back succeeds.- Do not pretend a learned heuristic is durable until runtime either:
- retires the empty log locally, or
- queues the dedicated
skillops-promotionlane and later promotes the heuristic on the promotion PR branch.
Learned heuristics (SkillOps)
Converted and distributed by TomeVault — claim your Tome and manage your conversions.