Index of every page on this site: llms.txt
All skills
nimrodfisher avatar

/dashboard-specification

@9449d36
Run it yourself

Design specifications for effective dashboards. Use when planning new dashboards, improving existing ones, or documenting dashboard requirements before development starts.

Use this Skill: https://skilld.dev/gh/nimrodfisher/data-analytics-skills/dashboard-specification

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈49 tokens for metadata: the name and description. ≈691 when used: this file. ≈2k more on demand in 3 files.

Description uses 2.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈197 characters, or 2.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

  1. 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.
  2. 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.
  3. 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.
  4. 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.md for layout patterns.
  5. 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.
  6. 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 guidelines
  • references/dashboard_requirements_guide.md — how to run requirements gathering, avoid scope creep, and validate the spec
  • assets/dashboard_spec_template.md — complete spec: purpose, users, metric hierarchy, layout wireframe, interactivity, data sources, success criteria

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill is a collection of documentation templates and design principles for dashboard creation. It contains no executable code, network operations, or external dependencies.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 9449d36. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 7 months ago

README badge

README badge for nimrodfisher/data-analytics-skills/dashboard-specification