docs-i18nlisted

# docs-i18n — Internationalization Analysis ## Workflow 1. **Check language configuration** — run `get_workspace` and check `enabled_languages`. If only one language is enabled, skip this skill entirely. 2. **Connect to Docsbook** — run `list_workspaces` to find the workspace, then `get_doc_graph` to get all pages across all languages. Reindex if graph is empty or stale. 3. **Apply checklist** — check language configuration, content parity by tier, navigation/UI translation, translation content rules, format localization, RTL handling, translation freshness, and SEO for multilingual. 4. **Produce report** — return one JSON issue object per finding, sorted by severity. ## Guardrails - Do not run this skill if only one language is enabled — exit early with a note. - Confirm the source-of-truth language (usually English) with the user before flagging parity gaps. - Content parity is priority-based: Tier 1 pages must be translated; Tier 3 can stay English-only. - A stale translation is worse than no translation — flag staleness even if the page exists. - Code inside code blocks is never translated — only surrounding prose and code comments. Flag translated code as an error. - Brand and product names (e.g., "Docsbook", "GitHub") are never translated. ## MCP Tools | Tool | Purpose | |------|---------| | `mcp__docsbook__list_workspaces` | Find workspace | | `mcp__docsbook__get_workspace` | Get enabled languages and settings | | `mcp__docsbook__get_doc_graph` | Full page list a