executive-dashboard
Design executive marketing dashboards. Use when: building CMO reports, board metrics, or leadership views.
What this skill does
# /digital-marketing-pro:executive-dashboard
## Purpose
Design a C-suite marketing dashboard that translates marketing metrics into business outcomes for executive decision-making. Bridges the gap between marketing activity data and business impact, giving senior leaders the clarity to make faster, better-informed strategic decisions without drowning in operational detail.
## Input Required
The user must provide (or will be prompted for):
- **Executive role**: Primary audience — CEO, CMO, CFO, VP Marketing, or board — each requires different metric emphasis and abstraction level
- **Business model and revenue drivers**: How the company makes money — SaaS, e-commerce, lead gen, marketplace, subscription — and the key revenue levers marketing influences
- **Strategic priorities this quarter**: The 2-4 business priorities the executive team is focused on that marketing should ladder up to
- **Reporting frequency**: How often the dashboard will be reviewed — weekly executive standup, monthly leadership meeting, quarterly board review
- **Current data sources and tools**: Analytics platforms, CRM, ad platforms, attribution tools, and BI systems currently in use with data freshness and reliability notes
- **Existing reports being replaced**: Current reporting artifacts the dashboard will consolidate or replace — helps identify gaps and redundancies
- **Key decisions the dashboard should inform**: Specific decisions executives make that this dashboard should support — budget allocation, channel mix, hiring, campaign scaling, market expansion
- **Stakeholder data literacy level**: How comfortable the audience is with marketing metrics — determines labeling, context, and narrative density needed
## Process
1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply brand voice, compliance rules for target markets (`skills/context-engine/compliance-rules.md`), and industry context. **Also check for guidelines** at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` — if present, load restrictions and relevant category files. Check for custom templates at `~/.claude-marketing/brands/{slug}/templates/`. Check for agency SOPs at `~/.claude-marketing/sops/`. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.
2. **Identify north-star metrics**: Select 5-7 metrics that directly tie marketing activity to business outcomes — revenue influenced, pipeline generated, customer acquisition cost, lifetime value, market share, brand equity indicators
3. **Design metric hierarchy**: Organize metrics into three tiers — leading indicators (predict future performance), lagging indicators (confirm past results), and health metrics (signal system stability and sustainability)
4. **Select visualization type per metric**: Choose the optimal chart type for each metric based on data shape and decision context — trend lines for trajectory, gauges for targets, bar charts for comparisons, sparklines for density
5. **Define alert thresholds and anomaly triggers**: Set green/yellow/red thresholds for each metric with specific trigger values, and configure anomaly detection rules for unexpected spikes or drops
6. **Map data sources to each metric**: Document which system provides each metric, how it is calculated, data freshness (real-time, daily, weekly), and known limitations or lag
7. **Design layout for scanning speed**: Structure the dashboard for F-pattern or Z-pattern scanning — most critical metrics top-left, summary before detail, consistent visual hierarchy, minimal cognitive load
8. **Add narrative guidance**: Write "how to read this" instructions for each section — what good looks like, what bad looks like, and what action to take in each scenario
9. **Build drill-down structure**: Design three levels of depth — summary view (the dashboard itself), detail view (campaign or channel breakdowns), and root cause view (diagnostic data for investigating anomalies)
10. **Create mobile-friendly variant**: Adapt the dashboard layout for mobile or tablet viewing — prioritize top 3-5 metrics, stack vertically, enlarge touch targets, and simplify visualizations
11. **Add comparison baselines**: Define what each metric is compared against — plan/target, prior period (MoM, QoQ, YoY), industry benchmark, and competitive estimate — with comparison display format
## Output
A structured executive dashboard design containing:
- **North-star metrics (5-7)**: Selected metrics with business rationale explaining why each matters to the executive audience and how it connects to strategic priorities
- **Metric hierarchy diagram**: Visual framework showing leading, lagging, and health metrics with causal relationships and directional influence between them
- **Visualization recommendations**: Chart type, scale, color coding, and annotation style for each metric with rationale for the design choice
- **Alert threshold definitions**: Green/yellow/red boundaries for each metric with specific trigger values, anomaly detection rules, and notification routing
- **Data source mapping**: Metric-by-metric documentation of source system, calculation method, refresh frequency, data latency, and known quality issues
- **Dashboard wireframe layout**: Spatial layout showing metric placement, section grouping, visual hierarchy, and scanning flow optimized for the target audience
- **Narrative guide**: Section-by-section presentation guide explaining how to read each area, what questions it answers, and what actions to consider based on the data shown
- **Drill-down structure**: Three-level depth design — summary (dashboard), detail (channel/campaign breakdown), and root cause (diagnostic investigation) with navigation flow
- **Mobile layout variant**: Adapted design for mobile viewing with prioritized metrics, vertical stacking, simplified charts, and touch-optimized interactions
- **Comparison baseline definitions**: For each metric, the comparison standard (target, prior period, benchmark, competitive) with display format and context notes
- **Refresh cadence and data latency notes**: Documentation of how often each metric updates, expected data lag, and implications for decision timing
- **Executive summary template**: A 3-sentence written narrative template that synthesizes dashboard findings into a verbal briefing — what happened, why it matters, what to do next
- **Glossary of terms**: Plain-language definitions of all metrics and marketing terminology for non-marketing stakeholders with examples and context
## Agents Used
- **analytics-analyst** — Metric selection, hierarchy design, visualization recommendations, data source mapping, alert thresholds, drill-down architecture, refresh cadence, and dashboard layout optimization
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.