SkillAgentSearch skills...

docs-check

CONTRIBUTOR TOOL - Validate plugin against latest Claude Code documentation. Catches breaking changes, deprecations, discovers new features. Run before releases or periodically

Install / Use

npx skills add oliver-kriska/claude-elixir-phoenix --skill docs-check

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Claude Code

Our assessment of docs-check

docs-check scores 87/100 on our quality scale, 619th of 1,148 Content & Media skills we index.

Its SKILL.md is 3.7 KB long, well organised into 11 sections with 4 code examples: a solid amount of guidance for an agent.

It has 574 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
20/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 12 days ago, so docs-check is actively maintained.
  • Our last check on 2026-11-01 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

docs-check compared with similar skills

All 4 of these similar skills score higher than docs-check; compare them before choosing.

SkillScoreStarsUpdatedFormat
docs-check (this skill)by oliver-kriska8757412d agoSKILL.md
siyuanby siyuan-note10047.3ktodayMCP Server
algorithmic-artby anthropics100177.9k57d agoSKILL.md
pptxby anthropics100177.9k57d agoSKILL.md
prospectingby coreyhaines3110060.1k7d agoSKILL.md

Frequently asked questions

How do I install docs-check?
Run npx skills add oliver-kriska/claude-elixir-phoenix --skill docs-check. The install tabs above show the steps for each supported agent.
Which AI agents does docs-check work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is docs-check safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is docs-check still maintained?
The repository was last updated 12 days ago, so docs-check is actively maintained.

name: docs-check description: | CONTRIBUTOR TOOL - Validate plugin against latest Claude Code documentation. Catches breaking changes, deprecations, discovers new features. Run before releases or periodically. NOT part of the distributed plugin. argument-hint: "[--quick|--focus=agents|skills|hooks|config]"

Plugin Documentation Compatibility Check

Validates plugin agents, skills, hooks, and config against the latest Claude Code documentation to catch breaking changes and discover new features.

Usage

/docs-check                    # Full validation (all components)
/docs-check --quick            # Structural checks only (no docs fetch, no tokens)
/docs-check --focus=agents     # Validate only agents
/docs-check --focus=skills     # Validate only skills
/docs-check --focus=hooks      # Validate only hooks
/docs-check --focus=config     # Validate only plugin.json/marketplace.json

Architecture (OTP Supervision Pattern)

┌─────────────────────────────────────────────────────────────────┐
│  /docs-check (skill entry point)                                │
│   │                                                             │
│   ├─ Step 1: bash scripts/fetch-claude-docs.sh (zero tokens)    │
│   │          Always fetches all 9 doc pages (~420KB)             │
│   │                                                             │
│   └─ Step 2: delegate to orchestrator (reads from cache only)   │
│       │                                                         │
│       │  docs-validation-orchestrator (opus)                    │
│       │                                                         │
│       │  SCAN → READ CACHE → SPAWN WORKERS → COMPRESS → REPORT │
│       │   │         │              │             │          │   │
│       │   ↓         ↓              ↓             ↓          ↓   │
│       │ inventory  pre-fetched  4 parallel    context    report │
│       │ plugin     docs-cache   subagents     supervisor       │
│       │ components              (sonnet)      (haiku)          │
│       └─────────────────────────────────────────────────────────┘
└─────────────────────────────────────────────────────────────────┘

Execution

Step 1: Fetch Docs (Automatic)

Always run first. Downloads all doc pages to cache. Skips pages already cached within 24h. Zero token cost — pure curl.

# --quick mode: skip this step entirely (structural checks only)
# All other modes: always fetch
bash scripts/fetch-claude-docs.sh

Step 2: Delegate to Orchestrator

After docs are cached, delegate. The orchestrator reads from cache only and crashes if cache files are missing.

Task(subagent_type: "docs-validation-orchestrator")

Pass the user's flags (--quick, --focus) in the prompt.

What the Orchestrator Does

  1. Inventory — scan plugins/elixir-phoenix/ for existing components
  2. Read cached docs — from .claude/docs-check/docs-cache/ (never fetches)
  3. Spawn workers — one sonnet subagent per component type, in parallel
  4. Compress — context-supervisor (haiku) if 3+ workers
  5. Structural checks — fast local checks, always run
  6. Report & Action — write report, offer PR if issues found

Iron Laws

  1. Fetch ALL docs upfront — no conditional fetching, no partial downloads
  2. Use scripts/fetch-claude-docs.sh — single source of truth for doc fetching
  3. Workers get docs IN PROMPT — no runtime fetching
  4. Workers use sonnet — opus is wasteful for comparison tasks
  5. Structural checks always run — even if docs fetch fails
  6. Breaking changes are BLOCKERS — surface prominently

References

  • references/validation-rules.md — Per-component validation checklists
  • references/doc-pages.md — Component-to-URL mapping

Related Skills

View on GitHub
GitHub Stars574
CategoryContent
Updated12d ago
Forks45

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions