docs-audiencelisted

# docs-audience — Audience Targeting Analysis ## 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 — it's 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 stated audience** — before flagging vocabulary issues, read each page's stated prerequisites, "who this is for" sections, and content type signals. 3. **Apply checklist** — check audience declaration, vocabulary and jargon, beginner-page conventions, expert-page conventions, and mixed-audience red flags. 4. **Produce report** — return one JSON issue object per finding, sorted by severity. Group issues by page. ## Guardrails - Do not edit any documentation files — surface findings only. - Flag jargon only when it is undefined *and* the stated prerequisites do not cover it. Precise technical terms are not a problem if the audience is declared correctly. - A single page may legitimately serve both beginner and expert sections if they are clearly separated with headers — flag as mixed-audience only when no separation exists. - Ask the user to confirm the primary audience and assumed knowledge level before deep-diving. ## Inputs This skill needs two things, by whatever means are available: - **The list of pages in scope** —