doctree-mcp: Skill for Claude Code

.claude/skills/doc-lint/SKILL.md

doc-lint is a skill for Claude Code from joesaby/doctree-mcp. It costs 27 tokens per session (351 once invoked), scanned A, original, MIT.

A documentation-quality checker for the doctree-mcp wiki. It looks for pages that are disconnected, unusually short, missing information at the top, or linked incorrectly.

In plain words
What is it for?
Use it to find orphaned pages, stub pages, missing title or category fields, and broken links, then decide what documentation needs improvement.
Why use it?
It reveals documentation gaps that can make a wiki hard to navigate or unreliable for readers and tools.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is joesaby/doctree-mcp's own configuration. It tells Claude Code how to work on doctree-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything doctree-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to joesaby/doctree-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/joesaby/doctree-mcp/main/.claude/skills/doc-lint/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/joesaby/doctree-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for doc-lint

README.md
[![agentmods](https://agentmods.dev/badge/skills/joesaby/doctree-mcp/doc-lint/github.svg)](https://agentmods.dev/skills/joesaby/doctree-mcp/doc-lint)
Your own site
<a href="https://agentmods.dev/skills/joesaby/doctree-mcp/doc-lint"><img src="https://agentmods.dev/badge/skills/joesaby/doctree-mcp/doc-lint/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for doc-lint

Your own site · 80×15
<a href="https://agentmods.dev/skills/joesaby/doctree-mcp/doc-lint"><img src="https://agentmods.dev/badge/skills/joesaby/doctree-mcp/doc-lint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 351 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.00351
Opus 5 $0.00014 $0.00176
Sonnet 5 $0.00005 $0.00070
Haiku 4.5 $0.00003 $0.00035

Measured 10d ago against content hash 234013e781da, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

doc-lint scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/doc-lint/SKILL.md · 43 lines

What it actually says

Audit Wiki Health

Perform a health check on the doctree-mcp wiki using the available tools.

Workflow

Step 1: Find orphaned pages

list_documents()

Look for documents where the links to: field is absent or empty — these have no inbound cross-references from other docs.

Step 2: Find stubs

In the list_documents results, identify documents with very low word counts (under ~100 words). Call get_tree on each to confirm they are sparse rather than just compact.

Step 3: Check frontmatter

For each flagged doc, call get_node_content(doc_id, [root_node_id]). Check whether frontmatter includes: title, description, tags, type, category.

Step 4: Report and fix

For each issue found, report to the user:

Orphaned pages: Suggest adding a cross-reference link from a related doc. Stubs: Suggest either expanding the content or merging it into a related doc. Missing frontmatter: Suggest the missing fields based on the content you read.

Ask the user whether to fix each issue now, or skip.

Tips

  • Run bunx doctree-mcp lint in the terminal for a quick machine-readable summary
  • Use find_similar if you want to check whether a stub should be merged into another doc
  • Cross-references are markdown links — adding [Auth Guide](../auth/guide.md) to a doc removes its orphan status
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 43 lines · 27 tokens per session scan A 234013e781da

Subscribe to this mod's changes

doc-lint is a skill published in the GitHub repository joesaby/doctree-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 351 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens