kai-data-dashboard - Data To Dashboard Handoff

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.

Turn existing Kai artifacts into a dashboard spec, data contract, or lightweight static dashboard. This skill is a companion surface. It should not replace analytics setup, audit analysis, or outbound strategy.

Use /kai-analytics when the user needs a tracking plan or attribution model. Use /kai-html-presentation when the user needs a client-ready audit deck. Use /kai-client-dashboard when the ask is a durable, white-labeled, client-facing product with its own onboarding wizard and page set — that skill calls this one for the data-contract layer underneath it. Use this skill when the data already exists and needs to become a dashboard-ready operator surface.

Phase 0: Identify The Source

Accept these inputs:

workspace/sdr-operator/<package-slug>/
Any folder with kai-data.json, audit-data.json, _data-sources.md, or _data-gaps.md
CSV exports from CRM, ESP, sequencer, ads, analytics, or sales tools
Markdown reports with source-backed findings
User-provided metrics and targets

If there is no source folder or file, ask for it. Do not fabricate sample data unless the output is explicitly labeled internal_demo.