exec-dashboard-blueprint — Claude Code skill
exec-dashboard-blueprint is a Claude Code skill for structuring board-ready marketing dashboards around a Story Arc. It organizes /marketing-analytics output into KPIs, risks, and actions with owners and due dates.
Apache-2.0 ★ 450 updated 2026-04-03
npx skills add gtmagents/gtm-agents --skill exec-dashboard-blueprint -a claude-codeWhat exec-dashboard-blueprint does
The skill covers the full dashboard build: KPI tiles with traffic-light status, Drill Cards broken out by channel, campaign, and audience, and Insight Callouts that tie anomalies to root causes and required decisions. KPI guardrails are built in — awareness deviation beyond 8% triggers an alert, beyond 12% kicks off a campaign review; pipeline must hit 3x quota per quarter with a warning at 2.5x; win rate floor is 25% with escalation below 20%; CAC payback cap is 14 months, escalating above 16.
The Weekly Exec Packet template pulls these pieces together: a headline with KPI spine, three bullets on drivers, a decisions table, and the action register. If a guardrail breach runs longer than two weeks, the governance overlay prescribes escalation to the Chief Product Officer or Sales Director. A three-slide deck structure, dashboard wireframe with recommended chart types, and an annotation checklist round out the templates.
Tool hooks are defined for Context7 (current GA4 and Salesforce docs), Serena (safe edits to SQL notebooks and dbt models), Sequential Thinking (retro facilitation), and Playwright (dashboard screenshots before distribution). The skill installs in Claude Code with npx skills add gtmagents/gtm-agents --skill exec-dashboard-blueprint -a claude-code.
What it helps with
- build a Weekly Exec Packet with KPI spine and a decisions table
- classify metrics into RAG zones against built-in guardrail thresholds
- standardise dashboard layout across BI, RevOps, and marketing teams
- set up a weekly cadence: Monday data QA, Tuesday ELT preview, Thursday exec meeting
- annotate anomalies with root causes directly inside the dashboard
Example prompts for the agent
- Build an executive dashboard from
/marketing-analyticsoutput for last quarter with RAG classification - Put together a Weekly Exec Packet — headline, KPI spine, drivers, action register with owners and due dates
- Check all metrics against guardrail thresholds and flag everything where win rate dropped below 20%
How to install exec-dashboard-blueprint
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill exec-dashboard-blueprint -a claude-code2Manually: put the files in place
~/.claude/skills/exec-dashboard-blueprint/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/exec-dashboard-blueprint/
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill exec-dashboard-blueprint -a codex2Manually: put the files in place
.agents/skills/exec-dashboard-blueprint/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill exec-dashboard-blueprint -a cursor2Manually: put the files in place
.cursor/skills/exec-dashboard-blueprint/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install gtmagents/gtm-agents plugins/marketing-analytics/skills/exec-dashboard-blueprint2Manually: put the files in place
.github/skills/exec-dashboard-blueprint/SKILL.md1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill exec-dashboard-blueprint -a gemini-cli2Platform CLI
gemini skills install https://github.com/gtmagents/gtm-agents --path plugins/marketing-analytics/skills/exec-dashboard-blueprintManually: put the files in place
.devin/skills/exec-dashboard-blueprint/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about exec-dashboard-blueprint
How do I install exec-dashboard-blueprint in Claude Code?
Run npx skills add gtmagents/gtm-agents --skill exec-dashboard-blueprint -a claude-code. The skill will be available at ~/.claude/skills/exec-dashboard-blueprint/SKILL.md.
What does the exec-dashboard-blueprint skill do?
It provides a framework for board-level marketing dashboards: Story Arc structure, KPI tiles with traffic lights, Drill Cards, anomaly annotations, and an action register with owners and deadlines.
What KPI guardrail values does the skill use?
Awareness: >8% deviation alerts, >12% triggers a campaign review. Pipeline: ≥3x quota per quarter, warning at 2.5x. Win rate: ≥25%, escalate below 20%. CAC payback: ≤14 months, escalate above 16.
Source text
SKILL.md · Apache-2.0
--- name: exec-dashboard-blueprint description: Layout and storytelling guide for marketing analytics executive dashboards. --- # Executive Dashboard Blueprint Skill ## When to Use - Preparing ELT/board-ready snapshots of marketing performance. - Standardizing dashboard layout across BI, RevOps, and marketing teams. - Packaging insights from `/marketing-analytics` commands into clear narratives. ## Framework 1. **Story Arc** – headline → KPI spine → risks/opps → actions. 2. **KPI Tiles** – awareness, demand, pipeline, revenue, efficiency metrics with traffic lights. 3. **Drill Cards** – channel, campaign, and audience breakouts linking to deeper views. 4. **Insight Callouts** – annotate anomalies, root causes, and required decisions. 5. **Action Register** – owners, due dates, and follow-ups surfaced alongside metrics. ## Templates - 3-slide deck structure (headline, KPIs, actions). - Dashboard wireframe with recommended chart types + layout. - Annotation checklist ensuring context + next steps accompany data. - **GTM Agents KPI Guardrail Sheet** – baseline vs target vs alert ranges for reach, pipeline, win rate, CAC payback @puerto/README.md#214-241. - **Measurement Spec** – metric definitions, filters, refresh cadence, owner column. - **Weekly Exec Packet** – combines dashboard screenshots, narrative summary, decision log (mirrors GTM Agents Data Analyst deliverable). ## Tips - Limit each dashboard view to one primary objective to avoid overload. - Embed links back to commands (`produce-campaign-report`, `monitor-channel-pacing`) for drilldowns. - Archive monthly snapshots for trend storytelling. - Adopt GTM Agents cadence: Monday data QA, Tuesday ELT preview, Thursday exec meeting, Friday retro + action register updates. - Highlight which KPIs are within guardrail, trending to alert, or breaching (RAG) so leadership can react quickly. - Pair with `docs/gtm-essentials.md` tools: Context7 for latest GA4 docs, Serena for patching data models, Sequential Thinking for retro facilitation. ## GTM Agents Dashboard Governance Overlay 1. **Data QA Loop** – run freshness + anomaly checks before distributing (log results in audit trail). 2. **Narrative Structure** – use Story Arc to link KPI shifts to drivers and required decisions. 3. **Action Register** – every dashboard delivery must include owner, due date, and status for prescribed actions. 4. **Escalation** – if guardrail breach persists >2 weeks, escalate to Chief Product Officer / Sales Director per GTM Agents governance. ## KPI Guardrails (GTM Agents Reference) - Awareness (reach/impressions) ±8% window before alerting; >12% triggers campaign review. - Pipeline add ≥3x quota per quarter; warn at 2.5x. - Win rate ≥25% for in-quarter commit; escalate if <20%. - CAC payback ≤14 months; escalate if >16 months. ## Weekly Exec Packet Outline ``` 1. Headline + KPI spine (traffic lights per guardrail) 2. Insights & Drivers – 3 bullets tying KPI movement to channels/programs 3. Required Decisions – what leadership must approve/block 4. Action Register – owner, due date, status 5. Appendix – detailed drill cards + methodology ``` ## Tool Hooks - **Context7** – fetch current platform docs (GA4, Salesforce) referenced in measurement specs. - **Serena** – update BI repo SQL notebooks or dbt models safely. - **Sequential Thinking** – facilitate monthly retros and architecture of dashboard iterations. - **Playwright** – capture dashboard screenshots or verify embedded web components before distribution. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents