docs-auditor
Audits any developer documentation site across 33 checks in 7 categories and produces a scored report (out of 100) with Pass / Warn / Fail status per check. Use this skill whenever a user provides a docs URL and asks to audit it, review it, score it, check its quality, or evaluate it for AI discoverability, SEO, structure, content, or completeness. Also trigger when the user says "run a docs audit", "audit these docs", "check this documentation", "how good are the docs for X", or pastes a docs URL with any evaluative intent. Always use this skill — do not attempt a freeform docs review without
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill docs-auditor --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Docs Auditor Skill Audits a developer documentation site across 33 checks in 7 categories. Given a docs URL, fetch all required pages, evaluate every check, and render a visual scored report. --- ## Step 0a — Unlock Derived URLs via Targeted Search (CRITICAL, do this first) Before fetching any derived URLs, run a single `web_search` that includes the exact file paths you need. This is required because `web_fetch` only allows fetching URLs that were user-provided or appeared in prior search/fetch results — the tool cannot fetch derived paths on its own, even if the root domain is known. Given a docs URL like `https://docs.example.com/`, construct and run this search: ``` docs.example.com/llms.txt docs.example.com/robots.txt docs.example.com/sitemap.xml example.com/llms.txt example.com/robots.txt example.com/sitemap.xml ``` Include both the subdomain and the root domain variants in the same query — these files may be hosted on either. This single search surfaces the exact file URLs in results, making them immediately fetchable. If a file doesn't appear in results at all, that is itself strong evidence it doesn't exist — mark the relevant checks as fail without needing to attempt a
- Step 0a — Unlock Derived URLs via Targeted Search (CRITICAL, do this first)
- Step 0b — URL Expansion (CRITICAL)
- Step 1 — Run All 33 Checks
- Category 1 — AI & LLM Discoverability (5 checks)
- Category 2 — Structure & Navigation (6 checks)
- Category 3 — Content Completeness (6 checks)
- Category 4 — Content Quality (3 checks)
- Category 5 — Technical SEO & Crawlability (5 checks)
- Category 6 — Internal Linking & Flow (4 checks)
- Category 7 — Versioning & Maintenance (4 checks)
- Step 2 — Score Calculation
- Step 3 — Render the Report
- Step 4 — After the Report
- Notes for Edge Cases
What does the docs-auditor skill do?
Audits any developer documentation site across 33 checks in 7 categories and produces a scored report (out of 100) with Pass / Warn / Fail status per check. Use this skill whenever a user provides a docs URL and asks to audit it, review it, score it, check its quality, or evaluate it for AI discoverability, SEO, structure, content, or completeness. Also trigger when the user says "run a docs audit", "audit these docs", "check this documentation", "how good are the docs for X", or pastes a docs URL with any evaluative intent. Always use this skill — do not attempt a freeform docs review without
How do I install it?
Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill docs-auditor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.