Route a "how do I use Codewhale" question to the installed help, config, and doctor surfaces instead of reciting a manual from memory. Explicit-only.
74
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Explicit-only. This skill is a router, not a manual. It is deliberately kept out of the ambient model catalogue so it never spends prompt budget, and it never restates documentation that the running build already exposes.
Load it only when the user explicitly asks how to use Codewhale itself — a command, a setting, a keybinding, or where a feature lives.
Answer from the surface that owns the fact, in this order:
/help lists the commands this build registers;
/help <command> prints that command's usage line. This is the only
authoritative command list, because it is generated from the registry./skills opens the manager, /skills inspect prints the
discovery mode, searched directories, and source paths. /skill <name>
activates one. See docs/SKILLS.md in a Codewhale checkout./config is the live settings surface. Config file
keys are documented in docs/CONFIGURATION.md; provider/model routing in
docs/PROVIDERS.md.docs/KEYBINDINGS.md in a checkout. There is no
keybinding slash command; do not invent one.codewhale-tui doctor reports the resolved
config path, provider credential presence (never values), and workspace
state. Prefer its output over inference.When the workspace is a Codewhale checkout, docs/ is present on disk and
read_file is the right tool. Read the single most relevant file and quote
the specific lines. Outside a checkout, docs/ is usually absent — in that
case rely on /help, /config, and doctor, and say plainly that the
reference docs are not installed locally.
docs/ looking for context.e1049cf
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.