Skills overview

A Claude Code skill is a prompt template, plus optional metadata, that lives in ~/.claude/skills/ (or <project>/.claude/skills/) and runs when you invoke it with /skill-name or when its trigger conditions match a user message.

Skills are how we package the patterns from the Workflows section into one-line invocations. Instead of pasting the triage decision matrix into every session, you install a skill once and invoke it with /toado-triage.

Why use a skill at all

You do not have to. Everything a skill does, you can do by typing the steps yourself. Skills win when:

• You repeat the same multi-step flow. Triage, verify, screenshot regression, dupe detection.
• You want consistency across sessions. A skill bakes in the decision matrix so two runs months apart behave the same way.
• You want to share the workflow with teammates. Skills are files you commit to a repo; teammates clone and they work.
• You want shorter sessions. A four-word /toado-triage acme web replaces a long setup paragraph.

Where skills live

~/.claude/skills/<skill-name>/
  SKILL.md          ← the prompt template
  examples/         ← optional, reference behavior

For project-scoped skills, swap ~/.claude/skills/ for <project-root>/.claude/skills/. Project-scoped skills only load when Claude Code is run inside that project directory.

Installing a Toado skill

The fastest path is to copy the skill directly from the recipes:

1. Open the skill page (e.g., toado-triage or one of the recipes).
2. Copy the SKILL.md block.
3. Run:

mkdir -p ~/.claude/skills/toado-triage
$EDITOR ~/.claude/skills/toado-triage/SKILL.md

4. Paste, save.

Now in any Claude Code session you can invoke /toado-triage. Claude loads the skill’s prompt and runs it.

What a Toado skill needs

Every Toado-aware skill assumes you have:

• The Toado MCP server registered (see Installation).
• A token with the right scopes for what the skill does. Triage and verify need read, comments, and tickets:write. See Tokens & scopes.
• Optionally, a default project id baked into the skill (see Authoring your own for templating).

Skills are not magic

A skill is just a prompt that Claude reads when invoked. The MCP tools do the actual work. If a skill misbehaves, look at the tool calls it generates, not at “skill internals”, because there are none.

Toado skills we ship

Skill	Purpose	Page
toado-triage	Walk a column, fix what is fixable, comment what is not, move tickets forward.	toado-triage
toado-verify	Walk In Review, validate the previous run’s claims, move on or back.	Recipes › Verify
toado-screenshot-sweep	Compare the captured screenshot against the current page, file diffs as new tickets.	Recipes › Screenshot sweep
toado-dupes	Find probable duplicate tickets in a project and link them.	Recipes › Dupe detection

Authoring your own

When the recipes do not fit, write your own. See Authoring your own for patterns: when to use which MCP tool, how to scope to a project, comment-as-receipt convention, opt-out signals.