Skip to content
Skills Library
AI & agents · Learning & explanation

claude-code-docs

/claude-code-docs

Answer questions about Claude Code (features, hooks, plugins, skills, MCP, Agent SDK, settings, CLI) from the official docs. Uses the ask CLI to resolve a version-pinned local mirror and csp for semantic search, falling back to grep and WebFetch. Use when the user asks how Claude Code works, what a configuration field does, or whether Claude Code supports something.

Licence
MIT
Last repository change
14.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 14.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Answer questions about Claude Code (features, hooks, plugins, skills, MCP, Agent SDK, settings, CLI) from the official docs. Uses the ask CLI to resolve a version-pinned local mirror and csp for semantic search, falling back to grep and WebFetch. Use when the user asks how Claude Code works, what a configuration field does, or whether Claude Code supports something.

Arguments

/claude-code-docs [question]
Original author description

Answer questions about Claude Code (features, hooks, plugins, skills, MCP, Agent SDK, settings, CLI) from the official docs. Uses the ask CLI to resolve a version-pinned local mirror and csp for semantic search, falling back to grep and WebFetch. Use when the user asks how Claude Code works, what a configuration field does, or whether Claude Code supports something.

How it works

  1. How to find the answer
Original SKILL.md headings · 64 lines, 343 words
SKILL.md preview
---
name: claude-code-docs
description: Answer questions about Claude Code (features, hooks, plugins, skills, MCP, Agent SDK, settings, CLI) from the official docs. Uses the ask CLI to resolve a version-pinned local mirror and csp for semantic search, falling back to grep and WebFetch. Use when the user asks how Claude Code works, what a configuration field does, or whether Claude Code supports something.
argument-hint: [question]
arguments: [question]
---

Answer this question about Claude Code using the official documentation:

**$question**

## How to find the answer

Work through these steps, falling back gracefully when a tool is missing.

### 1. Resolve the docs mirror

```bash
DOCS="$(ask src github:pleaseai/claude-code-docs)/docs"
```

`ask src` prints the root of a cached checkout of the docs mirror (clones on first use). If the `ask` CLI is not on PATH, run it via npx/bunx instead:

```bash
DOCS="$(npx -y @pleaseai/ask src github:pleaseai/claude-code-docs)/docs"
```

Only fall back to step 4 (WebFetch) when neither works, such as offline sandboxes without npm registry access.

### 2. Search for relevant pages

Prefer semantic search with csp, scoped to the per-page markdown:

```bash
csp search "$question" "$DOCS" --content docs --top-k 8
```

Or equivalently via ask (requires csp on PATH):

```bash
ask search github:pleaseai/claude-code-docs "$question" --content docs --top-k 8
```

If csp is not on PATH, run it via npx/bunx:

```bash
npx -y @pleaseai/csp search "$question" "$DOCS" --content docs --top-k 8
```

If that fails too, fall back to grep over the mirror — search for 2-3 distinct keyword variants, not one long phrase:

```bash
grep -ril "<keyword>" "$DOCS"
```

The manifest at `$DOCS/../llms.txt` lists every page with a one-line summary; reading it is a fast way to shortlist pages when keyword search is noisy.

### 3. Read and answer

Read the top matching pages (whole pages — they are small). Ground every claim in what the pages actually say:

- Answer in the user's language; keep code identifiers, field names, and flags verbatim.
- Cite each source page with its canonical URL: a mirror file `$DOCS/hooks.md` corresponds to `https://code.claude.com/docs/en/hooks`.
- Quote exact field names, JSON shapes, and version requirements (`min-version` markers) when they matter.
- If the docs do not answer the question, say so explicitly — do not fill gaps from memory.

### 4. Fallback: WebFetch

If the `ask` CLI is unavailable, fetch `https://code.claude.com/docs/llms.txt`, pick the relevant page URLs from the manifest, and fetch each as `<page-url>.md` (this plugin's hook rewrites page URLs to `.md` automatically). Then answer as in step 3.

Versions

RepositoryScoreLicence
This page · pleaseai/claude-code-plugins100MIT
MacHu-GWU/sanhe-claude-code-plugins100MIT
answerdotai/skill-plugins86Apache-2.0

Database snapshot: 13.11.2026 · package version b210346af3fd (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100working-with-claude-code
    Use when working with Claude Code CLI, plugins, hooks, MCP servers, skills, configuration, or any Claude Code feature - provides comprehensive official documentation for all aspects of Claude Code
  • 100working-with-claude-code
    Use when working with Claude Code CLI, plugins, hooks, MCP servers, skills, configuration, or any Claude Code feature - provides comprehensive official documentation for all aspects of Claude Code
  • 100agents-docs
    Use for current official documentation about Codex, Codex CLI, or Claude Code behavior, configuration, prompting, skills, permissions, tools, surfaces, capabilities, troubleshooting, hooks, app-server, or hook trust. Consult the relevant official source before answering.
  • 86codex-docs
    Use when answering questions about current Codex behavior, configuration, CLI features, hooks, skills, plugins, sessions, compaction, permissions, or other Codex-specific interfaces from official documentation.
  • 90docs-lookup
    Get facts from live official docs through docs MCP connectors, not WebFetch or web search: Claude Code, claude.ai/Cowork, Claude API, MCP, ACP, OpenAI/Codex, xAI/Grok, plus any docs connector the session has. Use whenever a doc fact matters: answering, building, reviewing or debugging.
  • 100claude-docs
    Search and read locally-stored Claude documentation covering Claude Code CLI, Claude API (Messages, tool use, vision, streaming, batch), Agent SDK (Python and TypeScript), prompt engineering, and all Anthropic platform docs. Use this skill whenever the user asks about Claude…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.