docs-setup-workspacelisted

Configure a fresh Docsbook workspace from one command. Wires branding, UI toggles, AI chat, SEO, languages and custom domain via Docsbook MCP — the natural follow-up to /docs-publish. Falls back to printed setup instructions if MCP isn't connected.
Docsbook-io/docs-skills · ★ 0 · AI & Automation · score 75

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

# docs-setup-workspace — Configure a Docsbook workspace via MCP The actual work is done by the **`docs-workspace-configurator`** subagent (Sonnet, pinned model). ## Workflow 1. Call `list_workspaces` first to confirm MCP transport is up. If it fails for non-auth reasons, print the MCP connection command and exit gracefully. 2. Check whether the workspace already exists before calling `create_workspace` — Docsbook auto-indexes repos within seconds of a push. 3. Read branding values from `_branding.json` if present. Fall back to sensible defaults when the file is missing. 4. Apply settings in priority order: navigation (Free-tier, always) → branding → UI → AI/SEO/languages (plan-gated). 5. Catch each plan-gated failure individually; record it in the result but do not abort the rest of the run. 6. Report which sections were applied, which were plan-gated, and any warnings. ## Guardrails - Never abort the whole run on a plan-limit (402) error — branding, UI, and navigation still apply on Free. - Set `defaultTheme` to `"system"` if the source had a theme toggle; otherwise pin to the detected scheme. - Always set navigation (back-link to source URL) even on Free — it is high-value and always available. - MCP transport is HTTP (hosted), not stdio — do not confuse it with local MCP servers. - If workspace is not yet indexed after `create_workspace`, retry once after a short wait before reporting failure. ## MCP Tools | Tool | Purpose | |------|---------| | `list_workspaces` |