Cc docs

Skill ToruAI/toru-claude-agents/skills/cc-docs

Look up how Claude Code itself works — hooks, skills, subagents, MCP, plugins, settings — from the official docs, so answers come from the current spec instead of memory.From its SKILL.md

Install

npx -y skills add ToruAI/toru-claude-agents --skill cc-docs

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
runs commandsInstructs the agent to run 4 commands, including `claude plugin validate <path>` and 3 more.
fetches URLsInstructs the agent to fetch 8 URLs, including https://code.claude.com/docs/en/overview and 7 more.

SKILL.md

2.8 KB, 644 tokens by cl100k_base, as published. Nobody here has run it

Claude Code Documentation

Answer questions about Claude Code from the official documentation, fetched at the moment you need it. Do not answer from memory: this product ships changes weekly, and a confidently wrong answer about a hook event or a manifest field costs more than a fetch.

How to Use

Fetch the page that covers the question with WebFetch. Start from the overview only if you need to find your way around; otherwise go straight to the relevant page.

Topic	URL
Overview / index	`https://code.claude.com/docs/en/overview`
Skills	`https://code.claude.com/docs/en/skills`
Hooks — guide	`https://code.claude.com/docs/en/hooks-guide`
Hooks — full reference	`https://code.claude.com/docs/en/hooks`
Subagents	`https://code.claude.com/docs/en/sub-agents`
MCP	`https://code.claude.com/docs/en/mcp`
Plugins — guide	`https://code.claude.com/docs/en/plugins`
Plugins — reference	`https://code.claude.com/docs/en/plugins-reference`
Plugin marketplaces	`https://code.claude.com/docs/en/plugin-marketplaces`
Slash commands	`https://code.claude.com/docs/en/slash-commands`
Settings	`https://code.claude.com/docs/en/settings`
CLI reference	`https://code.claude.com/docs/en/cli-reference`

If a URL 404s, the docs have been reorganised — fetch the overview and follow its navigation rather than guessing a new path.

Verify against the live CLI where you can. For anything about plugins, hooks or settings, the installed binary is a second source of truth and it cannot be out of date:

claude plugin validate <path>    # what the schema actually accepts, warnings included
claude plugin --help             # current subcommands
claude --help                    # flags

When the docs and the CLI disagree, trust the CLI and say so in your answer.

When to Use

Someone asks "how do I…" about a Claude Code feature
You are about to write a hook, skill, subagent, plugin manifest or settings block
You need to check whether a field, event or flag actually exists
Something behaves differently than expected and you need the spec, not a guess

Offline

WebFetch needs network access. With none, say that you are answering from memory and that the spec should be re-checked — do not present a remembered field list as current.

If you want a local copy for offline work, scripts/scrape_claude_code_docs.py in this repo mirrors the docs into docs/claude-code/ for personal use. That mirror is deliberately not committed or shipped: it is Anthropic's content, and a stale local copy is exactly how wrong answers get confident.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most docs writing skills give in 644 tokens

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

Use third-person for skill descriptionsin 54 of 1951, across 35 files
Start descriptions with Use whenin 43 of 1951, across 29 files
Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
Use active voicein 40 of 1951, across 36 files
Map file responsibilities before defining tasksin 36 of 1951, across 29 files
Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
Ask one question at a timein 35 of 1951
Offer execution options after saving the planin 33 of 1951, across 24 files
Include complete code in every stepin 33 of 1951, across 27 files
Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
Announce the skill usage at the startin 30 of 1951
Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

Do not answer from memory
Verify information against the live CLI
Trust the CLI if documentation disagrees
Navigate from overview if URLs fail
State if answering from memory when offline

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.