dashboard-reading-flow

Restructure analytical dashboards into a clear top-to-bottom reading sequence.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill dashboard-reading-flow-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dashboard-reading-flow
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/dashboard-reading-flow
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill dashboard-reading-flow-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Dashboards often contain all the right data but present it in a confusing order, leaving users unsure what they are looking at, what they can change, or where to dig deeper. This Skill provides a structured method to audit and reorganize dashboard sections so the interface explains itself in the right sequence. ## Core Features & Use Cases - Section Ordering: Apply a default reading sequence (identity, snapshot, controls, interpretation, evidence charts, drill-down tables) to any analytics or BI page. - Snapshot vs. Controls Balance: Decide whether KPI cards or filter controls should lead, and separate them visually with spacing, surfaces, or headings. - Interaction Affordance: Make buttons, filter chips, and interactive legends visibly clickable instead of looking like passive labels. - Use Case: A tokenomics dashboard has charts above the fold with no context and controls blended into KPI cards. Use this Skill to reorder sections, separate the snapshot and control zones, and restyle legends as actionable controls. ## Quick Start Audit my analytics dashboard layout and reorder the sections so snapshot cards, controls, interpretation, and charts follow a clear reading sequence.

Frequently Asked Questions about dashboard-reading-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure the layout of an analytics dashboard?

Order dashboard sections as: identity and context, snapshot KPI cards, primary controls, interpretation layer, main evidence chart, secondary charts, then drill-down tables. This sequence lets users orient themselves before interacting with filters or data.

Should KPI cards or filter controls come first on a dashboard?

Place snapshot cards first when the page needs fast orientation or reads like an executive summary. Place controls first when every number is meaningless without a scenario choice, such as in modeling tools. If both are needed, keep them near the top but visually separated.

How do I make dashboard buttons and filter chips look clickable?

Give interactive elements a visible fill, adequate padding, border contrast that survives dark backgrounds, and distinct hover, focus, and selected states. Avoid outline-only controls on dark surfaces and chips that look identical to passive tags.

Can interactive chart legends be styled as filter controls?

Yes. When legends can filter, isolate, or toggle data series, style them like buttons with clear default, muted, and selected states. Preserve keyboard focus visibility and keep label text readable in every state.

When should I not reorder dashboard sections?

Avoid reordering when the issue is purely visual styling rather than information hierarchy. This approach moves whole sections first and tunes typography or color second; it does not replace detailed visual design or data accuracy work.