chart-integrity
Skill12 starsChanged 38 days agoMITView on GitHub
Use when creating, revising, or critiquing a chart, dashboard, or KPI display that makes a quantitative comparison someone will act on. Covers honest comparison and rendered checks; leave palette, marks, and library mechanics to the medium's own skill. Skip decorative graphics and diagrams with no data.
In this repository4 other files it gives its agents.
- improve-codebase-architectureSkill
- performance-tradeoffSkill
- prose-qualitySkill
- skill-auditSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 18
Use real data; label any synthetic data as synthetic.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Chart integrity
What survives a capable model is integrity slips and unchecked rendering, not chart-type choice. Check:
- Comparable inputs. Same definition, unit, population, denominator, and window on both sides. Mark or drop a partial current period beside complete ones; never draw it as a decline. Don't connect across missing intervals.
- Magnitude. Show the base with relative change ("100 → 110, +10%"). Label percentage points vs percent. Length encodings start at zero; a non-zero line axis is fine when disclosed.
- Claims. Titles state only what the data supports; no causal verbs for observational data. Name the interval type when showing uncertainty; don't rank estimates whose intervals make the order unstable. Declare top-N, filtered, or excluded subsets.
- Visible by default. Units, active filters, source and as-of date, and material caveats sit on or beside the chart, not in hover only. Captions and alt text match the active filtered state. KPIs carry a comparator (prior, target, or trend).
- Look at it. Render at delivery size and each viewport you ship. Inspect for clipped or colliding labels, legends over data, illegible ticks, inconsistent panel scales, and color as the only carrier of meaning. Fix and re-render. If you could not render, say so.
A request for "Tufte" or "clean" style means dense, honest evidence: plain background, plain type, direct labels. Skip stock styling (cream paper, serif fonts, a muted red accent) applied for looks.
Use real data; label any synthetic data as synthetic.
For critique, lead with what misleads, then what impairs reading, then craft. Skip items that pass.
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.

