ai-audit-docs
From the author
Audits documentation files against actual repo state. Detects dead references (links to nonexistent files/URLs), false claims (doc says feature X exists but the code doesn't), outdated version numbers, and references to commands that don't exist. Input: path to docs dir or specific files (defaults to docs/ README.md AGENTS.md). Output: ranked markdown table of findings with severity and location. Report-only, NO auto-fix. Trigger phrases: "audit docs", "check documentation", "verify docs", "docs review", "documentation audit".
Install
npx skills add arcasilesgroup/ai-engineering --skill ai-audit-docs -a claude-code
Installs to .claude/skills/ai-audit-docs/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- docs-auditorInfrasity-Labs/dev-gtm-claude-skillsAudits 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.Marketing★ 143
- guide-audittonone-ai/tononeAudit existing API documentation for completeness, accuracy, and developer experience. Use when asked to "audit our API docs", "are our docs accurate", or "review documentation quality".Engineering★ 76
- api-docs-quality-reportInfrasity-Labs/dev-gtm-claude-skillsAudits 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 response schema completeness. Produces a polished interactive HTML report with a summary scorecard, site-wide pattern analysis, ranked top issues, and per-endpoint findings with specific fix guidance. Trigger this skill whenever a user provides a documentation URL and asks to audit, review, analyse, or check their API docs. Also trigger for: "do the same audit for X", "audit docs.company.com", "check the API docs at X", "run the API docs audit on X", "review the docs for Y API", or 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 this structured crawl-score-report workflow.Engineering★ 143
- docs-claim-checkkyungseo/skillsteadFact-check public docs, verify a README against a repo, audit release notes, or find stale/overstated claims using supplied evidence. Advisory findings only. Not for standalone code/security review, fixes or command execution; use it only for eligible claims in mixed requests. When using this skill, never edit files and run no commands except to load its SKILL.md at the exact host-catalog path. Use an already supplied full body without rereading. Follow the native loader or, for command-backed loading, one safely quoted literal cat of that path; no other file, shell expansion, chaining, redirection or pipeline. Resolve aliases only from host-provided mappings, without commands. If the path is unresolved or loading fails, is denied or finishes incomplete, stop and request full instructions; do not probe, retry, use shell paging or elevate. The command exception never covers target/evidence reads. Disclose loading and its outcome, including failure; a prohibited attempt invalidates the assessment.Security★ 84
- ai-read-docsarcasilesgroup/ai-engineeringUse when the work depends on versioned or external behaviour — adding a package, writing setup or config, integrating an SDK or a paid API, debugging a framework change — or on anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs, fast-moving product behavior, user requests for latest/current/official behavior, unfamiliar repo docs/specs, errors that may indicate API drift, or high-stakes auth, security, billing, data, migration, deployment, compliance, or privacy behavior. Forces a docs pass (web-search of official sources) and reading primary docs before assuming from memory. Not for evidence from outside this repository generally — use /ai-research; not for questions the repository answers — use /ai-explore.Security★ 61
- docs-auditqshanx/docs-governance只读审计现有项目文档，检查资料散乱、入口难找、断链、内容过时、重复主源及当前与历史混用。用于用户要求“审计文档”“检查文档是否过时”“看看文档哪里乱”，或阶段交接前检查文档体系时。Other★ 241
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in