What problem does it solve?
Teams repeatedly re-derive the same workflows across sessions and agents, or ship skills containing private paths, secrets, and unverified commands. This reference defines when a recurring pattern deserves a SKILL.md, how to distill session journals into triggered instructions, and how to scrub and validate a skill before it ships in a PR.
Core Features & Use Cases
- Write-vs-skip triage: Criteria for deciding whether an experience becomes a skill, stays a session-journal entry, or remains a shared-library candidate.
- Router vs nested-reference pattern: Rules for keeping root SKILL.md routers compact while nested references under reference/<topic>/ carry the detail, with same-commit catalog, routing-table, and test updates.
- De-privatization and pre-publish checklist: Canonical rules for parameterizing paths, people, secrets, and IDs, plus a benchmark checklist covering frontmatter, triggers, verified commands, and last_changed_at timestamps.
- Use Case: After noticing three agents independently re-implemented the same release workflow, use this reference to distill the pattern into a nested reference, scrub private details, run the checklist, and bundle it into a reviewable PR.
Quick Start
Ask the agent to evaluate whether a recently repeated workflow should become a skill and, if so, distill and de-privatize it following this stewardship reference.