manage-skills
Installation
SKILL.md
Goal
Maintain portable agent skills while consumer repositories retain their own architecture, commands, permissions, and delivery policy.
Definition of Done
- Outcome, owner, effects, callers, portability boundary, and validation criteria are explicit.
- Assessment and planning change nothing.
- Authorized changes retain valid metadata, callers, scenario evidence, and explicit gaps.
- The skill has the appropriate template, clear contract, and targeted pitfalls where needed.
- Current validation accepts the current candidate; no required finding remains.
Workflow
- Resolve outcome, scope, owner, effects, callers, applicable instructions, completion proof, and whether an existing skill owns the capability.
- For assessment or planning, inspect and propose only. For authorized create, update, organize, or retire work, prepare the smallest distinct candidate and resolve callers before retirement.
- Use the family template: workflows state Goal, Definition of Done, optional Boundaries, and Workflow; internal reference procedures state Contract, Acceptance, Procedure, and targeted Pitfalls without skill metadata; mandatory entries state Principles only.
- Verify metadata, path/name, references, callers, commands, final diff, success scenarios, and failure or partial-discovery scenarios. Keep shared procedures canonical; package needed references with each workflow, link them conditionally, and verify isolated installation.
- For substantive maintenance, use Quality validation with the mode, scope, candidate, and evidence; otherwise apply the same self-assess, independent review, critique, triage, improve, and renewed-verdict cycle directly. Do not create recursive review pools.