Search and access Anthropic documentation covering Claude Code CLI, API, Agent SDK, and more. Supports natural language queries, content search, and direct topic lookup. Trigger on: /docs, documentation questions about Claude Code, Claude API, Agent SDK, prompt engineering, MCP, hooks, skills, tool use, streaming, batch processing, extended thinking, or any Anthropic platform feature.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
This skill provides AI-powered search and access to a locally mirrored copy of Anthropic's official documentation. The documentation lives at ~/.claude-code-docs and covers ~1,250 paths across five categories.
When a user asks about Anthropic documentation, use the search tools and reference files described below to find the relevant content, read it, and synthesize an answer. Do not guess — always read the actual documentation before answering.
Documentation sources: Two Anthropic domains are mirrored:
code.claude.com — Claude Code CLI documentationplatform.claude.com — Everything else: API, Agent SDK, guidesFive categories organize the paths (approximate counts as of 2026-04):
| Category | User Label | Paths | Covers |
|---|---|---|---|
claude_code | Claude Code CLI | ~43 | CLI setup, hooks, skills, MCP, memory, plugins, settings, sub-agents |
api_reference | Claude API | ~1,060 | Messages API, models, batches, files, admin, multi-language SDKs (Python/TS/Go/Java/Kotlin/Ruby) |
core_documentation | Claude Documentation | ~143 | Prompt engineering, tool use, vision, streaming, extended thinking, evaluation |
release_notes | Release Notes | 2 | Version history and system prompts |
resources | Resources | 1 | Additional resources |
Agent SDK paths live within api_reference but are labeled "Claude Agent SDK" for users. They cover: overview, Python/TypeScript SDKs, sessions, skills, subagents, MCP, plugins, structured outputs, and more.
File naming convention: Documentation files use double underscores for path separators:
docs__en__hooks.md — Claude Code CLI page /docs/en/hooksen__docs__claude-code__hooks.md — Alternate format for the same pageen__api__messages__create.md — API reference page /en/api/messages/createFollow this workflow when handling documentation queries:
Extract from the user's query:
Use the upstream helper script at ~/.claude-code-docs/claude-docs-helper.sh:
# Content search (best for questions and concepts)
~/.claude-code-docs/claude-docs-helper.sh --search-content "<keywords>"
# Path search (best for finding specific docs)
~/.claude-code-docs/claude-docs-helper.sh --search "<keywords>"
# Direct topic lookup (fastest for known topics)
~/.claude-code-docs/claude-docs-helper.sh <topic>If the helper script is unavailable, fall back to Grep:
grep -ril "<keyword>" ~/.claude-code-docs/docs/ | head -20See references/search-guide.md for detailed search tool usage.
Check which product categories the results span:
See references/category-map.md for the full category-to-label mapping and disambiguation rules.
Load the reference file matching the topic before answering detailed questions about search mechanics or category routing.
| Topic | Reference File | Key Contents |
|---|---|---|
| How to use search tools, filename conventions, Python fallback, direct doc reading | references/search-guide.md | Search commands, output formats, file naming patterns, graceful degradation |
| Product categories, user-facing labels, disambiguation rules, when to ask vs synthesize | references/category-map.md | Category-to-label map, path patterns, cross-context resolution strategy |
Some queries span multiple reference files or require special handling:
| Question Pattern | Action |
|---|---|
| "How do I use X in agent sdk?" | Filter search to agent-sdk paths, read all matches, synthesize |
| "What's the difference between X and Y?" | Search for both terms, read docs for each, present comparison |
| "Show me all docs about X" | Run path search, present grouped by product category |
| "hooks" (ambiguous — CLI hooks vs Agent SDK hooks) | Search content, check categories — if split across products, ask user |
| Direct topic name (e.g., "mcp", "memory") | Try direct file read first: ~/.claude-code-docs/docs/docs__en__<topic>.md |
Freshness check (-t) | Run: ~/.claude-code-docs/claude-docs-helper.sh -t |
| "what's new" | Run: ~/.claude-code-docs/claude-docs-helper.sh "what's new" |
# Content search (returns JSON with product context)
~/.claude-code-docs/claude-docs-helper.sh --search-content "extended thinking"
# Path search (returns ranked path matches)
~/.claude-code-docs/claude-docs-helper.sh --search "hooks"
# Direct topic lookup
~/.claude-code-docs/claude-docs-helper.sh hooks
# List all available docs
ls ~/.claude-code-docs/docs/*.md | sed 's/.*\///' | sed 's/\.md$//'
# Check freshness and sync
~/.claude-code-docs/claude-docs-helper.sh -t
# What's new
~/.claude-code-docs/claude-docs-helper.sh "what's new"
# Installation status
~/.claude-code-docs/claude-docs-helper.sh --status
# Fallback search (no helper script)
grep -ril "keyword" ~/.claude-code-docs/docs/ | head -20code.claude.com/docs/en/<page>. Everything else is at platform.claude.com/<path>.~/.claude-code-docs/docs/.search_index.json is missing, content search won't work. Rebuild with: cd ~/.claude-code-docs && python3 scripts/build_search_index.pydd10cc1
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.