Adding a new tool (a skill)

Part 4 · A SESSION, SCHEMATICALLY · Slide 58 of 60

1. skills/<name>/SKILL.md — folder name = front-matter name;
   description carries a /verb trigger      (eval TRIGGER-SANITY)
2. Contract, self-check, finish sections    (eval WORKER-CONTRACT)
3. scripts/<tool>.py, named by the SKILL.md (eval SCRIPT-OWNS-SCANNING)
4. scripts/fixture.sh — exit 0 = all held    (the battery)
5. Every cited path exists                  (eval REFERENCES-CITED)
6. Routable? add the verb to router.sh AND
   oracle's routing table                    (eval ROUTE-TABLE-PARITY)
7. Name it on README, plugin README,
   marketplace, tutorial, the render        (doctor ROSTER PARITY,
                                              RENDER SURFACES)
8. Add its files to the golden release
   surface, say why in CHANGELOG            (eval RELEASE-SURFACE)

Each step names the check that goes red if you skip it.