new-skill git:20261023.9f9eaf2A

Immutable. This exact content never changes and is served at /api/v1/blob/8e3b89d15ae2620a.

---
# GENERATED by scripts/kernel/sync.py from skills/new-skill/SKILL.md - do not edit
name: new-skill
description: Use when a procedure has been repeated by hand twice, or the owner asks to add a skill to the agency or a project. Interview, SKILL.md from template, description budget check, sync to both engines, lint.
disable-model-invocation: true
---

# New skill

Today is !`date +%F`. Request: `$ARGUMENTS`

## Procedure
1. **Interview**: what recurring procedure does this capture, step by step? Which files does it
   read and write? What is the check that it worked? Should the owner invoke it by hand only?
2. **Classify**: agency-wide → `skills/<name>/SKILL.md`; project-owned → the project's own
   skills folder. `ls` the target and `grep -ril "<name>"` first; extend an existing skill before
   adding one.
3. **Scaffold** from `templates/skill/SKILL.md`. Frontmatter is only `name`,
   `description` (at most 300 characters, saying only when to use it), optional `metadata`, and
   `disable-model-invocation: true` if hand-invoked. Body: numbered steps that name real files and
   commands, and a verification step. Replace any date with `!`date +%F``.
4. **Wire**: `python3 scripts/kernel/sync.py` copies it to the engine adapters; the registry entry
   appears on the next sweep.
5. **Lint**: `python3 scripts/kernel/lint.py` (description length, frontmatter keys).
6. **Dry run**: invoke it once on a real input and confirm the verification step passes.
7. Report the path, the description length, and which engines received it.