kai-client-dashboardlisted

> **Kai root note:** `knowledge/`, `harness/`, and `scripts/` paths in this skill live in the Kai install, not the user's project. Resolve them against the first ancestor directory of this SKILL.md that contains a `knowledge/` folder (the Kai plugin root, `~/.claude/kai`, or the kai-cmo-harness repo). `MARKETING.md`, `memory/`, and any output files live in the current project. If a referenced `scripts/` command is not available in this install, say so, skip it, and continue with the file-based guidance — never fabricate its output. # /kai-client-dashboard — A Live Branded Surface The Client Bookmarks ## Objective A co-branded, always-on reporting product standing up for **one** client: brand shell extracted from their own site, the page set they actually asked for, real data wired to real credentials, an explicit public-access decision, and the retention program that keeps them opening it. A report is a snapshot forgotten by Friday; this is a URL they return to. This is distinct from `/kai-data-dashboard`, which turns already-sourced data into a spec or static handoff, and from `scripts/build_dashboard.py`, which builds the *operator's own* internal ops dashboard (goals, tasks, integrations — `workspace/dashboard.html`). Use this skill when the deliverable is a durable product for someone outside your own team. **One client = one dashboard = one deployment.** Never fold a second client into an existing client's project. A shared default — a hardcoded client id, a fallbac