helplisted

# help Rides SYSTEM.md §3: *involve and teach* — a reply that requires knowledge the agent never gave is a defect · sober register. Run it: bash tools/skills.sh Then read the output back in the Principal's language, keeping the grouping. ## Why this file is thin on purpose The roster is **not written here.** It is read from `.claude/skills/*/SKILL.md` on every run, so a skill added a minute ago appears without anyone updating anything, and a skill deleted stops appearing. There is no index and no cache — nothing to go stale, and no second copy of the truth to drift from the first (§1). That is the whole reason this skill does not list capabilities itself. A help page that names them is a hand-maintained list wearing a command's clothes: it would be right the day it is written and wrong the day after, and being wrong there is worse than being absent, because a roster is trusted. Grouping comes from the frontmatter the runtime obeys, `user-invocable:` and `disable-model-invocation:`, for the same reason and one more. Adding a skill must never mean editing the thing that lists skills, and the roster must never say a skill has no command while the runtime still offers one (§8). ## What to do with what comes back - **A missing summary is the agent's work, not the Principal's.** Reading a skill and saying in one line what it does is the job. Handing the Principal a truncated description is returning labour that was never theirs. So: where a skill has no `summary:`,