Dashboard Specification
Designdashboard-specificationDashboard Specification is an Agent Skill for design published in the nimrodfisher/data-analytics-skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Design specifications for effective dashboards. Use when planning new dashboards, improving existing ones, or documenting dashboard requirements before development starts.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/nimrodfisher/data-analytics-skills/blob/HEAD/04-data-storytelling-visualization/dashboard-specification/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/dashboard-specification, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Dashboard Specification
When to use
- A new dashboard is being built and developers need a clear brief before starting
- An existing dashboard is confusing or underused and needs a structured redesign
- Stakeholders and the data team have different ideas about what a dashboard should show
- Documenting dashboard requirements as part of a broader data product process
- Creating a self-service analytics specification that can be handed off without multiple Q&A rounds
Process
- Define the purpose — write one sentence: "This dashboard answers [question] for [audience] who need to [decision or action]." If it can't be stated in one sentence, the scope needs narrowing first. See
references/dashboard_design_principles.md. - Profile target users — for each audience (executive, manager, IC), document their visit frequency, the primary question they come to answer, and their technical comfort level. Users with different needs usually need different dashboards, not more filters on one.
- Define the metric hierarchy — list primary KPIs (hero numbers at the top), secondary supporting metrics, and detail-level breakdowns. A dashboard with more than 10–12 distinct metrics is trying to do too much.
- Design the information architecture — sketch the layout using the hero → trends → breakdowns → details pattern. Position the most important information in the top-left. Use
references/dashboard_requirements_guide.mdfor layout patterns. - Specify interactivity — list global filters (date range, region, segment), drill-down paths, click actions, and hover tooltip content. Every filter and drill-down adds complexity; justify each one.
- Document data requirements and success criteria — for each metric, record the source table, transformation logic, and refresh frequency. Define how dashboard success will be measured (adoption rate, reduction in ad-hoc requests). Complete
assets/dashboard_spec_template.md.
Inputs the skill needs
- The business question the dashboard is meant to answer
- A list of candidate metrics (team can provide a rough list; you'll curate it)
- The primary audience (role, visit frequency, decision they make)
- Data availability: confirmed source tables and refresh schedules
- Any constraints: tool (Tableau, Looker, Metabase, etc.), branding guidelines
Output
references/dashboard_design_principles.md— layout hierarchy, chart selection, information density guidelinesreferences/dashboard_requirements_guide.md— how to run requirements gathering, avoid scope creep, and validate the specassets/dashboard_spec_template.md— complete spec: purpose, users, metric hierarchy, layout wireframe, interactivity, data sources, success criteria