docs-analyzelisted

Run a full audit of your documentation in one command. Orchestrates 10 specialized analyses — content type, structure, style, audience, links, SEO, a11y, i18n, media, maintenance — and returns a single prioritized report you can hand to the writer. Works on one page, a folder, or the entire docs/ tree.
Docsbook-io/docs-skills · ★ 1 · Data & Documents · score 75

Install: claude install-skill Docsbook-io/docs-skills

# docs-analyze — Documentation Analysis Orchestrator ## Workflow 1. **Gather the docs** — get the list of pages in scope and read their content. If a semantic/graph search tool over the markdown is available (self-hosted `markdown-lsp`, or a connected Docsbook workspace), prefer it — faster and cheaper than scanning files; otherwise read the files directly with `grep`/`find`. Prioritize Tier 1 pages (quick-start, pricing, auth, install) first. 2. **Identify Tier 1 pages** — flag quick-start, pricing, authentication, and installation pages for priority analysis. 3. **Run sub-skills in parallel** — spawn independent Agent calls for `docs-content-types`, `docs-structure-templates`, `docs-style-tone`, `docs-audience`, `docs-seo`, `docs-accessibility`, `docs-maintenance`. Run `docs-navigation-linking` and `docs-i18n` sequentially (they depend on the full graph and workspace language settings). 4. **Aggregate and deduplicate** — collect JSON issues from all skills; merge cross-cutting findings (e.g. missing alt = a11y + SEO — report once under higher severity, note both skills). 5. **Produce final report** — output a prioritized markdown report with severity summary, critical issues, recommendations by area, and quick-win list. ## Guardrails - Do not edit any documentation files — surface findings only. - Do not run `docs-i18n` if only one language is enabled in workspace settings. - A cross-skill finding (same line flagged by two skills) is reported once under the higher sever