sdk-docs-auditor
Audits any SDK documentation site and produces a fully scored, downloadable HTML report. Use this skill whenever a user provides a documentation URL and asks to audit, review, analyse, score, or check the quality of SDK docs. Also trigger for phrases like "audit the SDK docs at X", "check if the docs at X are complete", "review this SDK documentation", "how good are these docs", "run an SDK audit on X", or any time a user pastes a URL alongside words like audit, review, crawl, check, analyse, quality, completeness, or gaps. ALWAYS use this skill — do not attempt the audit without following thi
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill sdk-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.
# SDK Docs Auditor Produces a comprehensive, cross-referenced audit of any SDK documentation site with a fully styled downloadable HTML report. ## What this skill does 1. Discovers all SDK pages via `llms.txt` first, falling back to `sitemap.xml` (using curl), then homepage nav crawl 2. Fetches and reads every relevant SDK page 3. Audits six fixed sections: Installation, Quick Start, Error Handling, Troubleshooting, Examples, Best Practices 4. Cross-references every gap across ALL other SDK pages — never flag something as missing if it exists elsewhere 5. Scores each section 0–100 and assigns a rating tier 6. Generates a beautiful, self-contained, downloadable HTML report --- ## Step 1 — Discover all SDK pages Use a three-tier discovery strategy, trying each method in order until one succeeds. ### 1a. Try llms.txt first (preferred) Run a bash curl command to fetch llms.txt: ```bash curl -s <docs_url>/llms.txt ``` If found: - Extract every URL from lines matching the pattern `- [Page Title](URL): description` - Filter to SDK-relevant pages only — keep URLs whose path contains any of: `sdk`, `installation`, `quickstart`, `quick-start`, `error`, `troubleshoot`, `example`, `best-practi
- What this skill does
- Step 1 — Discover all SDK pages
- 1a. Try llms.txt first (preferred)
- 1b. Fallback — Try sitemap.xml
- 1c. Final fallback — Homepage nav crawl
- 1d. Identify section mapping
- Build the corpus
- Step 2 — Fetch every page in the corpus
- Output
curl -s <docs_url>/llms.txt
curl -s <docs_url>/sitemap.xml | python3 -c "import sys, re; print('\n'.join(re.findall(r'<loc>(.*?)</loc>', sys.stdin.read())))"
curl -s "https://docs.example.com/sdk/some-page" -L | python3 -c "
import sys, re, html
content = sys.stdin.read()
content = re.sub(r'<script[^>]*>.*?</script>', '', content, flags=re.DOTALL)
content = re.sub(r'<style[^>]*>.*?</style>', '', content, flags=re.DOTALL)
text = re.sub(r'<[^>]+>', ' ', content)
text = html.unescape(text)
text = re.sub(r'\s+', ' ', text).strip()What does the sdk-docs-auditor skill do?
Audits any SDK documentation site and produces a fully scored, downloadable HTML report. Use this skill whenever a user provides a documentation URL and asks to audit, review, analyse, score, or check the quality of SDK docs. Also trigger for phrases like "audit the SDK docs at X", "check if the docs at X are complete", "review this SDK documentation", "how good are these docs", "run an SDK audit on X", or any time a user pastes a URL alongside words like audit, review, crawl, check, analyse, quality, completeness, or gaps. ALWAYS use this skill — do not attempt the audit without following thi
How do I install it?
Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill sdk-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.