- Establish repeated, safe, generalizable evidence.
- Classify the skill as audit-only or action-capable.
- Define approval boundaries before command procedures.
- Keep platform and project behavior outside general skills.
- Obtain explicit scope approval.
Initialize skills with the official skill creator and include:
SKILL.mdagents/openai.yamlchecklist.mdexamples.mdfailure-modes.mdadapter-interface.mdevidence-template.md
Add a manifest example, command-policy example, evidence-pack example, workflow example, and executable tests.
- Never copy restricted evidence into reusable procedures.
- Never commit secrets or local
.envfiles. - Audit-only skills cannot gain mutation through adapters or approval.
- Action-capable skills must enumerate permitted local actions and reject everything else.
- Failed or skipped required checks cannot produce
complete.
Run:
node scripts/validate-pack.mjs .
node scripts/test-pack.mjs
node scripts/validate-maintainer-loop.mjs .
node --testUpdate the changelog and roadmap when behavior or scope changes.
./scripts/run-next --allow <permission> may inspect local repository state, validate the
pack, select the next ledger milestone, and append bounded run evidence. It must start from
a clean worktree and fails closed for missing, unknown, or mismatched permissions.
The loop does not replace human approval for scope changes, new skills, real adapters,
release publication, dependencies, or weakened safety rules. Update work-ledger.md when
the approved next milestone or its stop conditions change.