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.

MITAuto-check passedMarketing & SEO

Install Docs Auditor

skills CLI
$ npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill docs-auditor -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Infrasity-Labs/dev-gtm-claude-skills docs-auditor --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/docs-auditor .claude/skills/docs-auditor && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
docs-auditor
GitHub stars
136
Token cost
~3k tokens
SKILL.md length
1,499 words
Files
6 (incl. references)
Skills in repo
26
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 4 steps: Run All 33 Checks → Score Calculation → Render the Report → …
  • A user provides a docs URL and asks to audit it
  • SKILL.md covers Step 0a — Unlock Derived URLs…, Step 0b — URL Expansion…, Step 1 — Run All 33 Checks and Step 2 — Score Calculation, plus 3 more sections
  • Calls pip

What it does

Docs Auditor is an agent skill from Infrasity-Labs/dev-gtm-claude-skills. 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…

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `README.md`, `references/fetch-strategy.md` and `references/scoring.md`).

It sits in Marketing & SEO, covering Static sites and blogs and Technical SEO. The repository describes itself as: Open-source Claude skills for GEO, AI discoverability, and developer GTM workflows. Built for developer-focused companies that want their documentation to be found, parsed, and… The licence is MIT.

When your agent uses it

  • A user provides a docs URL and asks to audit it
  • Check its quality
  • Evaluate it for AI discoverability
  • The user says run a docs audit

Example prompts

  • “run a docs audit”
  • “audit these docs”
  • “check this documentation”
  • “/docs-auditor”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Run All 33 Checks
  2. Score Calculation
  3. Render the Report
  4. After the Report

What it can do on your machine

Read from SKILL.md and the folder at commit 02cfefb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pip

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pip, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Docs Auditor loads about 3k tokens when it runs, and up to ~6.8k if it reads all its reference files. Until then it costs about 162 tokens; SKILL.md has 1,499 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~162
When it runs · the whole SKILL.md, loaded when a task matches
~3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Infrasity-Labs/dev-gtm-claude-skills at commit 02cfefb, republished under its MIT licence (© Infrasity-Labs). 1,499 words, ~3,009 tokens.

Download SKILL.mdSave it as .claude/skills/docs-auditor/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
docs-auditor
description
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 following this structured workflow.

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 fetch.

Do this search silently as an internal setup step. Do not narrate it to the user.


Step 0b — URL Expansion (CRITICAL)

When the user provides a base docs URL (e.g. https://docs.example.com/), you MUST immediately treat ALL of the following derived URLs as user-provided and fetch them without asking for permission. This is the core mechanic that makes the audit work.

Given base URL https://docs.example.com/, fetch ALL of these in your first round:

{base}/robots.txt
{base}/sitemap.xml
{base}/llms.txt
{base}/llms-full.txt

Also try the root domain variants if the docs are on a subdomain:

https://{root-domain}/robots.txt
https://{root-domain}/llms.txt
https://{root-domain}/llms-full.txt
https://{root-domain}/sitemap.xml

Then fetch the main docs page itself, plus these standard sub-pages (adjust slugs based on what you find in the sidebar/nav):

{base}/                          ← landing / intro page
{base}/quickstart  (or /getting-started, /get-started)
{base}/changelog   (or /releases, /release-notes)
{base}/api         (or /api-reference, /reference)
{base}/faq         (or /troubleshooting, /help)
{base}/[one use-case or tutorial page]
{base}/[one deep settings or config page]

Fetch 6–8 pages minimum. More is better. Do NOT ask the user for more URLs — derive them.


Step 1 — Run All 33 Checks

After fetching, evaluate every check below. Use the fetched HTML/markdown content as evidence. Mark each check as pass, warn, or fail using the criteria defined per check.

Category 1 — AI & LLM Discoverability (5 checks)
#CheckPassWarnFail
1.1llms.txt present at root domainFile fetched successfully with contentFile exists but empty or malformed404 / not found
1.2llms-full.txt presentFile fetched successfullyFile exists but sparse404 / not found
1.3Docs pages listed in llms.txtLinks to doc pages found inside llms.txtSome pages listed but incompletellms.txt absent or no doc links
1.4AI bots allowed in robots.txtGPTBot, ClaudeBot, or similar explicitly allowed OR no disallow rules for themBots not mentioned (ambiguous)Bots explicitly disallowed
1.5Docs pages in sitemap.xmlSitemap found and contains doc page URLsSitemap exists but sparse / partialSitemap missing or 404
Category 2 — Structure & Navigation (6 checks)
#CheckPassWarnFail
2.1Introduction / overview page exists with real contentPage exists with substantive product description (>200 words)Page exists but thin / vagueNo intro page found
2.2Quickstart / Getting Started with actionable stepsStep-by-step guide gets user to working statePage exists but steps are vague or incompleteNo quickstart found
2.3API Reference / Reference section presentDedicated API reference section with endpoints or methodsSome reference content but not organized as API refNo reference section found
2.4Sidebar / navigation menu presentSidebar with categorized links visible in HTMLSidebar present but flat / uncategorizedNo sidebar detected
2.5Breadcrumb navigation presentBreadcrumb trail visible on sampled pagesPresent on some pages but not allNo breadcrumbs found
2.6Search functionality presentSearch input detected in HTMLSearch linked externally but not on-pageNo search found
Category 3 — Content Completeness (6 checks)
#CheckPassWarnFail
3.1Use cases / tutorials / examples section presentDedicated section with at least 2 full tutorial pagesSection exists but only 1 page or very thinNo use cases / tutorials found
3.2Code examples presentCode blocks found on multiple sampled pagesCode present on 1 page onlyNo code examples found
3.3Multiple language examples (Python, JS, cURL, etc.)2+ languages shown in code examplesOnly 1 language shownNo code examples at all
3.4Changelog / Release notes presentChangelog page exists with actual entriesPage exists but empty or placeholderNo changelog found
3.5FAQ / Troubleshooting section presentDedicated FAQ or troubleshooting page with real Q&AsFAQ mentioned but minimalNo FAQ or troubleshooting found
3.6Error messages / status codes documentedError codes or status codes listed anywhere in docsBrief mentions onlyNo error documentation found
Category 4 — Content Quality (3 checks)
#CheckPassWarnFail
4.1Intro page explains what the product is and who it's forClear product description + target audience statedProduct described but audience vagueGeneric/marketing intro with no substance
4.2Quickstart gets user to a working stateEnd-to-end steps from zero to working outputSteps present but incomplete or missing key detailQuickstart too vague to follow
4.3Sampled pages have sufficient depth (not stubs)All sampled pages have real content (>150 words, structured)Mix of full pages and stubsMajority of sampled pages are stubs
Category 5 — Technical SEO & Crawlability (5 checks)
#CheckPassWarnFail
5.1HTTPS enforcedAll fetched URLs use HTTPSMixed HTTP/HTTPSHTTP only
5.2Meta titles present on docs pages<title> tag found on all sampled pagesPresent on some pagesMissing on most pages
5.3Meta descriptions present on docs pagesmeta-description found on all sampled pagesPresent on some pagesMissing on most pages
5.4Canonical URLs present and correctCanonical tag present and points to the correct domainCanonical present but points to wrong/preview domainNo canonical tags found
5.5No noindex directives on docs pagesmeta-robots: index, follow on all sampled pagesMixed — some pages noindexMost pages set to noindex
Show full SKILL.md (558 more words)Show less
Category 6 — Internal Linking & Flow (4 checks)
#CheckPassWarnFail
6.1Docs pages cross-link to each otherInternal links found in body content of sampled pagesSome pages cross-link but most don'tNo internal links found in body
6.2Next / previous page navigation presentPrev/next nav links at bottom of sampled pagesPresent on some pagesNot found
6.3Links to GitHub / source codeGitHub or source code link found in docsMentioned in text but not linkedNo GitHub / source links found
6.4Community / support links present (Discord, Slack, Forum, Chat)Direct links to community or support channel foundMentioned but no direct linkNo community or support references
Category 7 — Versioning & Maintenance (4 checks)
#CheckPassWarnFail
7.1Version indicator visible (v1.2, "latest", badge)Version badge or label visible on sampled pagesVersion mentioned in text but no badgeNo versioning signals found
7.2Last updated / freshness signal on pages"Last updated" date or similar visibleChangelog exists as proxy signalNo freshness signals found anywhere
7.3Install commands include version pinningInstall commands show pinned versions (e.g. pip install foo==1.2)Install commands present but unpinnedNo install commands found
7.4Deprecation notices present (if multi-version)Deprecation banners or notices visibleChangelog mentions deprecationsNo deprecation notices (only fail if multi-version product)

Step 2 — Score Calculation

Score each category out of its max points. Each check is worth equal points within its category. Each category is weighted equally (each = 100/7 ≈ 14.3 points max).

Within each category:

  • Pass = full points
  • Warn = half points
  • Fail = 0 points

Final score = sum across all 7 categories, rounded to nearest integer out of 100.


Step 3 — Render the Report

Generate a standalone HTML report file:

  • Use the HTML/CSS/JS template in references/widget-template.md as the design reference.
  • Write the completed report to a file named {domain}-docs-audit.html in the current working directory (e.g. supabase-docs-audit.html).
  • The report must include:
    1. Score hero — large score out of 100, domain name, pass/warn/fail summary counts
    2. Legend — green dot = Pass, amber dot = Warn, red dot = Fail
    3. Category sections — one block per category with:
      • Category name and score (e.g. "3/5")
      • Pill badges: "X pass", "X warn", "X fail"
      • Each check row with icon (✓ / ! / ✗), label, and a short evidence note
  • Substitute all audit data (score, counts, category scores, check statuses, evidence notes) directly into the template — do not leave any placeholder values unfilled.
  • The file must be fully self-contained (no external dependencies) so it opens correctly in any browser without a server.

Step 4 — After the Report

After rendering, provide a short text summary (3–5 sentences) covering:

  • The 1–2 strongest categories
  • The biggest gaps / quick wins
  • Any critical issues (e.g. broken canonical, noindex on docs, AI bots blocked)

Offer to go deeper on any category or create a prioritized action plan.


Notes for Edge Cases

  • Subdomain docs (e.g. docs.stripe.com): always also check root domain (stripe.com) for robots.txt, llms.txt, and sitemap.xml — they are often hosted at root.
  • Docs behind auth: if pages return 401/403, mark relevant checks as warn with note "Could not verify — page requires authentication."
  • JS-rendered docs: if fetched HTML is sparse (< 200 chars of text), note that the docs may be JS-rendered and some checks may be inconclusive.
  • check 7.4 (deprecation): only fail this if evidence suggests the product has multiple versions. If it's clearly v1 only, mark as N/A (counts as pass for scoring).

© Infrasity-Labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in skills/docs-auditor of Infrasity-Labs/dev-gtm-claude-skills.

  • SKILL.md
  • README.md
  • references/fetch-strategy.md
  • references/scoring.md
  • references/widget-template.md
  • tests/test-cases.json

Open the folder on GitHubat commit 02cfefb

Compare with similar skills

Docs Auditor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Docs Auditor compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Docs Auditor this skillInfrasity-Labs/dev-gtm-claude-skills136—~3kAutomated safety check: PassMIT
Astro SEOjdevalk/skills105—~4.9kAutomated safety check: PassMIT
SEO Setupalisamadiii/Portfolio180—~1.7kAutomated safety check: PassNone
Content SEOjdevalk/skills105—~2.3kAutomated safety check: PassMIT
Agent Readiness Auditdocker/docs4.7k—~1.8kAutomated safety check: PassApache-2.0
SEO Coachakseolabs-seo/seo-coach146—~2.8kAutomated safety check: PassNone

Similar skills

  • Astro SEO

    jdevalk/skills

    Audits and improves SEO for Astro sites. An agent skill from jdevalk/skills.

    105 GitHub stars~4.9k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed
  • SEO Setup

    alisamadiii/Portfolio

    Full SEO/metadata setup and audit for client websites (Astro, Next.js, any static site).

    180 GitHub stars~1.7k tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed
  • Content SEO

    jdevalk/skills

    Audits a blog post draft or page copy for content-level SEO: search intent fit, focus keyphrase placement, E-E-A-T signals (experience, expertise, authoritativeness, trustworthiness), helpfulness…

    105 GitHub stars~2.3k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed
  • Official

    Audit a documentation site for agent-friendliness: discovery, markdown delivery, crawlability, semantic structure, machine-readable surfaces, and content legibility.

    4.7k GitHub stars~1.8k tokensUpdated today
    Frontend & DesignAuto-check passed
  • SEO Coach

    akseolabs-seo/seo-coach

    Beginner-first SEO coaching for people who want to learn by doing one safe, verifiable step at a time.

    146 GitHub stars~2.8k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Metadata Check

    jdevalk/skills

    Reviews short high-value strings — page titles, meta descriptions, schema description fields, FAQ answers, GitHub repo taglines, profile bios, social-card copy, and other metadata where Flesch and…

    105 GitHub stars~1k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed

More from Infrasity-Labs/dev-gtm-claude-skills

All 26 skills in this repo
  • Brief Outline Generator

    Infrasity-Labs/dev-gtm-claude-skills

    Generates a fully structured SEO content outline (not a finished brief) and exports it as a formatted .docx Word document.

    136 GitHub stars~4k tokensUpdated 3 mo ago
    Auto-check passed
  • Content Brief

    Infrasity-Labs/dev-gtm-claude-skills

    Generates a fully structured SEO content brief for a target keyword and optionally pushes it to a Notion database.

    136 GitHub stars~2.8k tokensUpdated 3 mo ago
    Auto-check passed
  • API Docs Quality Report

    Infrasity-Labs/dev-gtm-claude-skills

    Audits any API documentation site by crawling every endpoint page and scoring each one across 5 checks: description quality, OpenAPI spec presence, body param descriptions, response codes, and…

    136 GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed
  • Growth Report

    Infrasity-Labs/dev-gtm-claude-skills

    Generates a 3-month SEO performance HTML report for any domain using DataForSEO data.

    136 GitHub stars~4k tokensUpdated 3 mo ago
    Auto-check passed
  • Inbox

    Infrasity-Labs/dev-gtm-claude-skills

    Email triage system that handles both one-time setup and recurring triage in a single skill.

    136 GitHub stars~4.8k tokensUpdated 3 mo ago
    Auto-check passed
  • LLMs Txt Checker

    Infrasity-Labs/dev-gtm-claude-skills

    Audits any domain's AI-readiness by using curl to directly probe robots.txt, llms.txt, and llms-full.txt, then scores each file against a structured checklist and delivers a formatted report with…

    136 GitHub stars~2.4k tokensUpdated 3 mo ago
    Auto-check passed

Questions about Docs Auditor

What does Docs Auditor 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. Docs Auditor is an agent skill from Infrasity-Labs/dev-gtm-claude-skills. 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.

When should I use Docs Auditor?

Docs Auditor fits situations like: A user provides a docs URL and asks to audit it; check its quality; evaluate it for AI discoverability; the user says run a docs audit.

How do I install Docs Auditor in Claude Code?

Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill docs-auditor -a claude-code`. Or copy the skill folder (skills/docs-auditor in Infrasity-Labs/dev-gtm-claude-skills) into .claude/skills/docs-auditor in your project. Claude Code loads it when a task matches its description.

How do I install Docs Auditor in Codex?

Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill docs-auditor -a codex`. Or copy the skill folder (skills/docs-auditor in Infrasity-Labs/dev-gtm-claude-skills) into .agents/skills/docs-auditor in your project. Codex loads it when a task matches its description.

Can I use Docs Auditor in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill docs-auditor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs-auditor, .gemini/skills/docs-auditor, .github/skills/docs-auditor and .opencode/skills/docs-auditor in your project.

What does Docs Auditor need to run?

Going by SKILL.md and its folder, Docs Auditor needs the command-line tools its instructions call (pip). Our summary lists: Python 3.

Does Docs Auditor access the network?

SKILL.md contains no URLs. Its commands use pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Docs Auditor safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Docs Auditor use?

Docs Auditor is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Docs Auditor use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.8k tokens, read only when the agent opens those files.

What are the alternatives to Docs Auditor?

Skills that share tags, products or a category with Docs Auditor: Astro SEO (jdevalk/skills, 105 stars), SEO Setup (alisamadiii/Portfolio, 180 stars), Content SEO (jdevalk/skills, 105 stars) and Agent Readiness Audit (docker/docs, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Docs Auditor?

Infrasity-Labs (a GitHub user) maintains it in Infrasity-Labs/dev-gtm-claude-skills, which has 136 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on June 28, 2026.

Source: Infrasity-Labs/dev-gtm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.