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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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
the read tool (path: "docs/...") 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.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Audit a page or UI against WCAG 2.2 AA. Runs a static HTML scanner and a contrast calculator, then walks the manual keyboard, zoom, screen-reader-name and form checks the tools cannot do, and reports findings with the criterion, evidence, fix and how to verify. Use for accessibility reviews, WCAG checks, contrast questions or "is this accessible".
The English summary is being prepared. Showing the original description.
Break a large, parallelizable goal into bounded work units, coordinate existing agent/worktree machinery, integrate, and verify. Explicit-only.
The English summary is being prepared. Showing the original description.
Generate a small set of independent candidate solutions in worktrees, judge them against one explicit rubric, and apply the winner only after PASS verification.
The English summary is being prepared. Showing the original description.
Read and act on selected Chrome tabs and frames — their real browser, their logged-in sessions. Use for questions about the current page, filling a form the user is on, following a link they mentioned, or checking what a site actually renders. Not for throwaway automation in a clean profile.
The English summary is being prepared. Showing the original description.
Deploy or change a Cloudflare Worker with cf. Review config, preflight, build and dry-run; show the target and change, obtain explicit approval, deploy and verify. Covers versions, secrets, rollback and named modes.
The English summary is being prepared. Showing the original description.
Look up current Cloudflare documentation (Workers, Pages, KV, R2, D1, Queues, DNS, WAF, platform APIs) through Cloudflare's official remote MCP server. Use when answering Cloudflare questions or writing Cloudflare config.
The English summary is being prepared. Showing the original description.