data-visualization
Skill4 starsChanged 23 days agoMITView on GitHub
Select, design, label, and verify charts and data displays that help users interpret evidence accurately and accessibly.
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 40 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use for analytics dashboards, reports, metrics, charts, tables, trend comparisons, financial summaries, monitoring views, or any interface …
- Distinctive: line 27
Treat these as starting heuristics, not rigid rules.
- Distinctive: line 31
Use accurate scales, meaningful zero baselines when needed for comparison, consistent units, explicit ranges, and clear labels.
- Distinctive: line 47
Test legend toggles, tooltips, sorting, filters, resizing, small screens, long labels, large values, negative values, and missing points.
“Common” is measured: kept by at least 6 in 10 of the 40 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Data visualization
When to use
Use for analytics dashboards, reports, metrics, charts, tables, trend comparisons, financial summaries, monitoring views, or any interface that presents quantitative information for decisions.
Workflow
1. Clarify the decision
Identify the question the reader must answer, the metric definition, units, population, time range, aggregation, source, and relevant caveats. Do not start by choosing a chart. If the data cannot answer the question, state the limitation.
2. Match encoding to the task
- Compare categories: usually a bar or dot plot with a clear common baseline.
- Show change over ordered time: line charts when continuity is meaningful; bars for discrete periods when comparison is clearer.
- Show composition: stacked bars for comparisons, or a part-to-whole chart only when the number of parts and comparisons make it legible.
- Show distributions: histogram, box plot, or dot plot depending on sample size and audience.
- Show relationships: scatter plot when both variables and their units matter.
- Show exact values or dense detail: a sortable, labeled table may be better than a chart.
Treat these as starting heuristics, not rigid rules. Avoid 3D distortion, decorative chart junk, and dual axes unless the reasoning and scale are explicit.
3. Encode faithfully
Use accurate scales, meaningful zero baselines when needed for comparison, consistent units, explicit ranges, and clear labels. Do not truncate or normalize an axis in a way that exaggerates differences. Distinguish missing data from zero. Identify estimates, forecasts, and uncertainty.
4. Provide context and hierarchy
State the metric and unit, date range, relevant baseline, and what changed. Add concise annotations only when they support an interpretation. Avoid presenting a correlation as causation or a metric without its denominator or definition when these change its meaning.
5. Design for accessibility
Use direct labels and patterns or text alongside color when categories must be distinguished. Ensure sufficient contrast, readable tick labels, keyboard access for interactive charts, and a concise textual summary or equivalent data table for important information. Do not force people to hover to obtain essential values.
6. Design dashboard states
Define initial, loading, no-data, filtered-empty, partial-data, stale-data, error, and refreshed states. Make active filters and date windows visible. Explain data freshness and avoid fake live values or synthetic metrics represented as real.
7. Validate behavior and performance
Test legend toggles, tooltips, sorting, filters, resizing, small screens, long labels, large values, negative values, and missing points. Check that data remains interpretable when animation is disabled. Consider rendering cost for large data sets and avoid needless re-rendering.
Quality gates
- Chart type matches the user question and underlying data.
- Units, time range, definitions, scale, and data provenance are understandable.
- Encodings do not mislead; missing values are not confused with zero.
- Important information does not depend on color or hover alone.
- A text summary or equivalent table exists when needed.
- Loading, stale, empty, filtered, and error states are represented accurately.
- Conclusions do not exceed what the data supports.
Other versions46 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 46
- anthropics/knowledge-work-plugins★ 34ksame name
- langchain-ai/deepagents★ 31ksame name
- openai/plugins★ 7.4ksame name
- vivy-yi/xiaohongshu-skills★ 455same name
- NTCoding/claude-skillz★ 342same name
- didixuxu/didi-skills★ 83same name
- launchapp-dev/animus-cli★ 39same name
- xjtulyc/awesome-rosetta-skills★ 34same name
- kensaurus/cursor-kenji★ 9same name
- kensaurus/skills★ 9same name
36 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use case-study-writing, interview-script and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CAPP-FinancialsSkillcase-study-writing
Client case study with challenge-approach-solution-impact structure and quantified outcomes
Also in 3 projects that use this
launchapp-devSkillinterview-script
Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.
Also in 3 projects that use this
abinauvSkillchange-management
Comprehensive change management consulting toolkit — stakeholder mapping, ADKAR framework, Kotter's 8-Step Model, communication planning, resistance analysis, cultural assessment, readiness assessment, training needs analysis, impact assessment, and transition planning.
Also in 3 projects that use this
nandanosqlSkillswot-analysis
Conduct a structured SWOT analysis — Strengths, Weaknesses, Opportunities, Threats — that connects internal capabilities to external forces for strategic decision-making.
Also in 3 projects that use this
nddqSkilldashboard-design
Also in 3 projects that use this
MicrosoftSkillpresentations
Create or edit editable PowerPoint PPTX slides and Google Slides-bound decks. Use for presentations, slide layouts, speaker notes, and template-based decks.
Also in 3 projects that use this
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- max-designSkill
- accessibility-auditSkill
- design-reviewSkill
- design-systemSkill
- forms-uxSkill
- frontend-designSkill
- information-architectureSkill
- interaction-motionSkill
- max-designSkill
- resilient-localizationSkill
- ui-testingSkill
- ux-writing-contentSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

