← ClaudeAtlas

routemark-skill-reviewlisted

Use after writing a skill into skills/own/, before the user is asked to link it.
routemark/routemark · ★ 0 · Code & Development · score 72
Install: claude install-skill routemark/routemark
# Reviewing a skill **Who this is for.** The Controller, with the user beside it. Never a delegate: if you are one and you have ended up here, stop. This is the step `routemark-skill-building` ends with. It is three things: the checker, and the two questions the charter asks of everything - what here is unnecessary, and what here is unsafe. The review is advice. The user's yes is the gate. ## 1. The checker ``` routemark skills check <path to the skill's directory> ``` It reads the real command line, so every line it rejects is one that would send a Controller down a dead end. It also checks the frontmatter, and that the two commands which are the user's in person stand only under their hand-over line. Fix what it reports and run it again, or tell the user what it reported and why you left it. It says nothing about anything below. ## 2. What here is unnecessary? - Does it restate `--help`, or what a command already prints? A skill says what the Controller cannot work out from those (charter principle 9). - Does it add a step Routemark does not require - a plan, an approval, a record, a check before work can start? One project file, and a task contract for each job, are the whole of what a project needs. A step nobody enforces is paperwork. - Could an addendum to a shipped skill have done this instead of a new skill? If it is about how to do something on this machine, it is an addendum. - Does it duplicate a shipped skill it could have named instead? - Is ther