Docs

Community

costiash

docs

Router for the /docs command. Look up Claude documentation, ask plain-English questions, generate interactive courses and HTML changelog reports, check freshness, and sync the local cache. Dispatches to the claude-docs, claude-docs-validate, claude-docs-course, and claude-docs-changelog skills.

Overview

Publisher	costiash
Repository	`claude-code-docs`
Skill name	`docs`
Stars	56
Forks	5
Bundled files	Instructions only
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by costiash on GitHub. Read the source before you install it.

Installation

Install the Docs AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/costiash/claude-code-docs/tree/main/plugin/skills/docs
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/costiash/claude-code-docs.git /tmp/claude-code-docs
mkdir -p .claude/skills
cp -r /tmp/claude-code-docs/plugin/skills/docs .claude/skills/docs

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Docs in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Docs on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Docs is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Claude Code Documentation — /docs router

You are a documentation assistant. Route the user's request to the appropriate skill.

Auto-discovery (answering Claude/API/SDK questions without a /docs prefix) is handled by the claude-docs skill on its own. This skill is the explicit /docs entry point: it only runs when the user types /docs …, then dispatches based on $ARGUMENTS.

Documentation Location

The clone at ~/.claude-code-docs/ holds only metadata — paths_manifest.json (the page index) and search_index.json — plus the plugin. The actual .md pages are fetched from Anthropic's servers into a local cache at ~/.claude-code-docs/cache/ (override with $CLAUDE_DOCS_CACHE_DIR). Missing pages are fetched on demand via plugin/scripts/fetch-docs.sh get <filename>.

If ~/.claude-code-docs/paths_manifest.json doesn't exist, inform the user:

Documentation not found. Set up with:


/plugin marketplace add costiash/claude-code-docs
/plugin install claude-docs@claude-code-docs

Then restart Claude Code so the SessionStart hook can clone the metadata and sync the cache.

Routing

Analyze $ARGUMENTS and route:

No arguments / help (empty, --help, -h, help): → Show brief usage:

/docs <topic> — Look up documentation (e.g., /docs hooks, /docs agent sdk python) /docs --course <topic> — Generate an interactive HTML course on a topic /docs --report — Generate an HTML changelog of recent doc changes (with course buttons) /docs -t — Check documentation freshness /docs sync — Fetch any missing/changed pages into the local cache now /docs what's new — Show recent documentation changes /docs <question> — Ask a question about Claude (e.g., /docs how do I configure MCP?)

Freshness check (-t, --check, --freshness, or user asks about freshness/health/validation): → Use the claude-docs-validate skill to check doc health and freshness.

What's new (what's new, recent changes, updates): → Run: ~/.claude-code-docs/plugin/scripts/manifest-diff.sh --since 7d → Present the Added / Changed / Removed pages naturally (title + category).

Sync (sync, update cache, fetch): → Run: ~/.claude-code-docs/plugin/scripts/fetch-docs.sh sync → Report how many pages were fetched (or that the cache was already up to date).

Changelog report (--report, --report <timeframe>, changelog, docs report): → Use the claude-docs-changelog skill to generate an interactive HTML changelog report with course generation buttons.

Stats (--stats, stats, count): → Total pages: jq '.pages | length' ~/.claude-code-docs/paths_manifest.json → By category: jq -r '.pages[].category' ~/.claude-code-docs/paths_manifest.json | sort | uniq -c | sort -rn → Report the total and the per-category breakdown.

Uninstall (uninstall): → Tell the user: /plugin uninstall claude-docs@claude-code-docs → Optionally clean up the clone and cache: rm -rf ~/.claude-code-docs (this also removes ~/.claude-code-docs/cache/ and any generated courses).

Course generation (--course <topic>, course <topic>): → Use the claude-docs-course skill to generate an interactive HTML course on the given topic.

Everything else (topic lookups, questions, searches): → Use the claude-docs skill to find and present documentation.

User's Request

The user requested: $ARGUMENTS

Frequently asked questions

What does the Docs AI skill do?

Why use Docs on TypingMind?

Because you install it once and use it with any model. Docs is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Docs in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/costiash/claude-code-docs/tree/main/plugin/skills/docs. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Docs?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Docs?

As many as you like. As long as a model supports skills, you can use Docs with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Docs AI skill free?

It is published on GitHub by costiash. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Release Openclaw Plugin Testing

openclaw

OrganizationPopular

Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E,…

Solid

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

Auto Qa

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

Autoreview

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Claude Code Documentation — /docs router

Documentation Location

Routing

User's Request

Frequently asked questions

Related AI Skills

Set up your own AI workspace now