report-skills

# Report Skills — shared flow and rules All five skills publish through the **ReportRoom MCP server**. This file holds what they share; each skill's SKILL.md holds only what differs. ## The publish flow (every skill follows this) 1. **Check access.** Call `account_status`. If no account/API key exists, call `create_account` — it issues a key in-flow; never ask the user to leave the conversation to sign up. Note: publishing is blocked until the user clicks the email-verification link (`create_account` sends it), and unverified accounts serve from a preview/noindex domain — tell the user this upfront so the first publish isn't a surprise. 2. **Fetch the design language.** Call `get_design_system` and follow it exactly when authoring. The design system supplies the taste; you supply content and assembly. Do not improvise your own CSS framework. 3. **Author a self-contained HTML document.** Semantic HTML, responsive, dark-mode aware, no external dependencies beyond what the design system allows. 4. **Lint before publish.** Call `lint_document` and fix every issue it reports. Never skip this step. 5. **Approval gate.** Show the user: title, a one-paragraph summary of what the page contains, section list, and who it's for. **Wait for explicit approval before calling `publish` on anything client-facing.** For personal/internal shares the user may pre-approve ("just publish it"). Also tell them every published page carries a small "Published with ReportRoom" footer credit (see bel...