tufte-viz
Skill10 starsChanged 6 months agoMITView on GitHub
Design, build, and critique data visualizations using Edward Tufte's principles. Use this skill WHENEVER the work involves a chart, graph, plot, dashboard, table, diagram, or any visual display of data, even if the user does not name Tufte or "data viz" explicitly. Triggers include: (1) Building a new chart, graph, plot, or figure (bar, line, scatter, time-series, small multiples, sparkline, etc.) (2) Designing or reviewing a dashboard, report, or slide with quantitative visuals (3) Critiquing or improving an existing visualization (4) Choosing between visualization approaches ("what's the best way to show this?") (5) Reducing chartjunk, improving the data-ink ratio, or fixing a misleading chart (6) Planning high-density displays, comparisons, or part-to-whole views Applies data-ink ratio, chartjunk elimination, graphical integrity, lie factor, small multiples, layering, sparklines, and analytical design. Consult before producing any chart so output is clear, honest, and high-density.
6 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- angadhn/botferencetheir own version, first seen Oct 30, 2026
- pskoett/pmx-canvastheir own version, first seen Oct 20, 2026
- nbbaier/agent-skillsedited, first seen Jul 8, 2026
- pjsny/tufte-vizedited, first seen May 25, 2026
- aparente/claude-skillstheir own version, first seen May 24, 2026
- ImpactMojo/ImpactMojoedited, first seen Apr 12, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- nbbaier/agent-skills★ 1416% same
- pjsny/tufte-viz★ 1016% same
- ImpactMojo/ImpactMojo★ 316% same
Wrote their own version · 3
- aparente/claude-skills★ 65same name
- pskoett/pmx-canvas★ 30same name
- angadhn/botference★ 20same name
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.
In this repository2 other files it gives its agents.
- exec-proseSkill
- executivepitchcrafterSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
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 48
Evaluate the data-ink ratio: Ask what can be erased and what is redundant, then say so specifically.
“Common” is measured: kept by at least 6 in 10 of the 6 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
Tufte Data Visualization
Apply Edward Tufte's principles to produce clear, honest, high-density visualizations, and to critique existing ones. The goal is always the same: maximize the information the viewer extracts per unit of ink and pixel, while never distorting what the data say.
Core stance
Before drawing anything, hold three questions in mind. What comparison is the viewer meant to make. What is the single insight that must survive a glance. Who is reading it and at what distance. A chart that cannot answer "compared to what?" is usually the wrong chart.
The default aesthetic is restraint. Start from almost nothing and add only marks that carry data. Grayscale is the baseline; color is reserved for encoding a variable or flagging one thing that matters. If an element can be erased without losing information, erase it.
Workflow for building a new visualization
- Clarify the data story. Identify the key comparison, the headline insight, and the audience. Write it in one sentence before choosing a chart type. If the data are multivariate, resist collapsing to a single variable just to simplify, because the interaction is often the point.
- Select the approach using the principles rather than habit:
- High need to compare across categories, periods, or conditions → small multiples (identical scales, identical encoding, tight spacing).
- Dense data where precise values matter → a well-set table, often beating a chart.
- Trend or shape across time → line chart with a muted or absent grid; consider a range-frame axis that spans only the actual data.
- Many metrics at once, shape mattering more than exact value → sparklines, one row per metric with the current value and delta beside it.
- Part-to-whole → bar or table, almost never a pie, and never a 3D pie.
- Causality or mechanism → put the intervention and the response in one frame and annotate the mechanism directly.
- Design with data-ink in mind. Begin minimal. Every gridline, tick, border, and label must earn its place. Push secondary elements (grids, reference lines, axes) into the background by lightening them so the data dominate; this is layering, and it lets dense displays stay readable.
- Protect integrity. Keep the lie factor near 1, meaning the size of the effect shown matches the size of the effect in the data. Use consistent baselines, do not truncate axes to exaggerate change, and never use area or volume to encode a linear quantity. Label thoroughly and cite the source, because documentation is what lets a stranger trust the evidence.
- Apply the Tufte test in
references/tufte-principles.mdbefore calling it done. For dashboards, dense displays, sparklines, or explanatory graphics, also work through the extended test inreferences/analytical-design.md.
Workflow for critiquing an existing visualization
- Check graphical integrity first. Estimate the lie factor if proportions look off. Verify baselines, scales, and intervals. Look for 3D applied to 2D data, which almost always distorts.
- Find the chartjunk. Decorative elements, heavy grids, moiré patterns, gratuitous gradients, and any "duck" where the design promotes itself over the data.
- Evaluate the data-ink ratio. Ask what can be erased and what is redundant, then say so specifically.
- Walk the six principles of analytical design (in
references/analytical-design.md). The lowest-scoring principle is usually the largest improvement opportunity. - Give specific before/after recommendations, not general praise. Name the element, name the fix, name the principle it serves.
Producing the actual artifact
When generating a chart in code, the principles translate directly: remove default chartjunk that libraries add (heavy borders, dark gridlines, drop shadows, 3D), set a grayscale palette and reserve one accent color, label series directly at the line ends rather than relying on a legend where possible, and set axes to the data range. Prefer formats that render as artifacts the user can inspect. A static, honest, well-labeled figure beats an interactive one with distortion built in.
Reference files
references/tufte-principles.md— core principles from The Visual Display of Quantitative Information: graphical excellence, integrity and the lie factor, data-ink ratio, chartjunk, small multiples, data density, multifunctioning elements, plus the seven-question Tufte test. Read when designing or critiquing any single chart.references/analytical-design.md— extensions from Envisioning Information, Visual Explanations, and Beautiful Evidence: the six principles of analytical design, sparklines, layering and separation, micro/macro design, range-frames and dot-dash plots, confections, and causality, plus the extended test. Read when designing dashboards, dense displays, sparklines, explanatory graphics, or anything multivariate.
Quick checklist
- Lie factor ≈ 1.0, honest baselines, no 3D on 2D data
- Maximum data-ink ratio; non-data marks erased
- Zero chartjunk
- Answers "compared to what?"
- Shows causality or mechanism where relevant
- Multivariate where the data warrant it, not over-reduced
- Words, numbers, and images integrated, not segregated
- Reveals both macro pattern and micro detail
- Layering: primary data dominates, secondary recedes
- Clear labeling, sources, and scales
- Appropriate data density
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.

