routemark-skill-buildinglisted
Install: claude install-skill routemark/routemark
# Writing a Routemark skill
**Who this is for.** The Controller: the powerful model that holds the work,
with the user beside it. Every Routemark skill is for the Controller and no one
else. That includes a skill about a delegate harness -- the harness is the
subject, the Controller is the reader. If you are a delegate and you have
ended up reading a Routemark skill, stop here and ignore it: it is not your
work and nothing in it is a task for you. On an open project that sentence is
a request, not a wall: a delegate there can read whatever the user can. This
paragraph is the one place that is explained; every other skill just says who it
is for.
This skill is the specification the others are written to. Shipped skills follow
it exactly, and Routemark's own tests check that they do. For a skill made on
this machine, the checker and the review are advice you show the user; their
yes is what links it.
## What a skill is
A skill says what the Controller cannot work out from `--help` and a command's
own output. It does not restate them. If a paragraph would be true of any
competent reader of the command line, delete it (charter principle 9).
## The form of every skill
- A directory named for the skill. `SKILL.md` inside it, and beside it any
other file it needs. A harness skill keeps its harness report as `REPORT.md`
in the same directory.
- `SKILL.md` opens with YAML frontmatter holding two fields: `name`, equal to
the directory name, and `description`, one or two sen