Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
← Back to list

docs-check — Plugin Documentation Compatibility Checker

A contributor-only skill that downloads the latest Claude Code docs and validates a plugin's agents, skills, hooks, and config against them.

Dev & CodingAdvanced★ 560⑂ 44AI score 7/10Last updated: Oct 2, 2026

What it does

  • Runs scripts/fetch-claude-docs.sh to pull all 9 official Claude Code doc pages (~420KB) into a local cache. Pure curl, so zero token cost; pages cached within 24h are skipped.
  • Delegates to a docs-validation-orchestrator (opus) that inventories plugin components, reads only from cache, and spawns one sonnet subagent per component type in parallel.
  • Compresses results through a haiku context-supervisor whenever 3+ workers run, keeping context under control.
  • Flags breaking changes and deprecations as BLOCKERS, surfaces newly available features, writes a report, and offers to open a PR.
  • Local structural checks always run, even if the docs fetch fails.

Who it's for

  • Maintainers of Claude Code plugins/marketplaces who need a pre-release sanity check.
  • Anyone verifying that plugin.json, marketplace.json, and agent/skill/hook definitions still match the current spec.
  • Developers looking for a solid reference implementation of parallel subagent orchestration.

※ It is explicitly a contributor tool, not shipped with the distributed plugin, and its paths are hardwired to plugins/elixir-phoenix/.

Examples

  1. Full pre-release sweep: /docs-check — fetches everything and validates all component types.
  2. Fast, token-free pass: /docs-check --quick — structural checks only, no doc download.
  3. Targeted audit: /docs-check --focus=hooks — compares only hook definitions against the latest docs to catch renamed events or schema changes.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/oliver-kriska/claude-elixir-phoenix/HEAD/.claude/skills/docs-check/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the .claude/skills/docs-check folder from the GitHub repo oliver-kriska/claude-elixir-phoenix into my ~/.claude/skills/docs-check/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/oliver-kriska/claude-elixir-phoenix.git && mkdir -p ~/.claude/skills && cp -r claude-elixir-phoenix/.claude/skills/docs-check ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal and go to your working directory.
  2. Clone the repo: git clone https://github.com/oliver-kriska/claude-elixir-phoenix.git
  3. Create the skills directory and copy the skill: mkdir -p ~/.claude/skills && cp -r claude-elixir-phoenix/.claude/skills/docs-check ~/.claude/skills/
  4. The skill depends on scripts/fetch-claude-docs.sh, the references/ files, and the docs-validation-orchestrator agent — copy those along too, or simply run Claude Code from inside the cloned repo.
  5. Make the fetch script executable: chmod +x claude-elixir-phoenix/.claude/skills/docs-check/scripts/*.sh (adjust the path as needed).
  6. Restart Claude Code and try /docs-check --quick first as a lightweight smoke test.
  7. To reuse it on your own project, replace the hardcoded plugins/elixir-phoenix/ path in SKILL.md and the orchestrator with your plugin's path.