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

/display-quantitative-information

@3323bc9
Run it yourself

Design, critique, or implement quantitative graphics, scientific figures, dashboards, and evidence tables. Use for display choice, scale/encoding integrity, uncertainty, and accessible chart handoff. Do not use for decorative illustration or general data cleaning without a quantitative display.

Use this Skill: https://skilld.dev/gh/tristanmanchester/agent-skills/display-quantitative-information

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

referencesintegrity-audit.md

≈782 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Integrity Audit

Run integrity checks before cosmetic redesign. The most dangerous charts often look polished.

Core questions

  1. What is the claim or comparison?
  2. What is the numerical effect in the data?
  3. What visual effect does the graphic show?
  4. Are the visual and numerical effects proportional?
  5. What context would change the interpretation: denominator, sample size, time window, baseline, uncertainty, source, transformation, inflation, population, exposure, or filter?

Baselines and scales

Bars and columns encode magnitude by length, so a visible zero baseline is usually required. If the meaningful story is deviation from a reference, use a dot plot, interval plot, slope chart, or difference chart instead of a truncated bar.

Line charts and scatterplots do not always require zero baselines, but the chosen range must not exaggerate trivial variation or hide important variation. Label transformations, log scales, index bases, breaks, and independent panel scales.

Lie factor

When a visual effect can be measured, compute:

lie factor = visual percent change / data percent change

Values near 1 are visually proportional. Large departures suggest exaggeration or understatement. Opposite signs indicate a severe reversal of meaning. Use scripts/lie_factor.py or the lie-factor fields in assets/chart-spec-template.json.

Area, volume, and pictorial scaling

If a one-dimensional quantity is encoded with area or volume, check whether the displayed area or volume is actually proportional to the number. Scaling both height and width by the data value squares the apparent effect; scaling height, width, and depth cubes it.

Prefer position or length for precise quantitative comparison unless the area is the actual measured phenomenon.

Denominators and exposure

Counts often need denominators. Crime, defects, cases, emissions, failures, claims, clicks, and incidents may require rates per population, units, time, exposure, tests, or opportunities. Maps are especially prone to confusing raw counts with population density.

Context and omitted comparisons

A graphic may distort by omission. Check whether the time window, comparison group, benchmark, seasonal cycle, historical range, or uncertainty range is too narrow for the claim. Add context where it changes interpretation.

Uncertainty and sample size

Show uncertainty when data are estimates, samples, forecasts, simulations, measurements, model outputs, or small-n comparisons. Use intervals, bands, raw points, sample sizes, sensitivity panels, or notes. Label what the interval means.

Checklist for existing charts

  • Axis labels and units are visible.
  • Baseline and scale choices match the encoding.
  • Same scales are used across comparable panels, unless clearly labeled otherwise.
  • Source, sample, filters, denominator, and time window are available.
  • Visual dimensions are proportional to numerical quantities.
  • Aggregation does not hide distribution or outliers central to the claim.
  • Color is not the only way to identify important groups.
  • Decorative marks do not overpower evidence.

Source: SKILL.md on GitHub

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 alerts1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The skill is safe to use and adheres to best practices for data visualization auditing. It provides analytical scripts to evaluate chart integrity based on Tufte's principles. All scripts use only the Python standard library, do not perform network requests, and do not access sensitive system files. A minor risk is documented regarding the attack surface for indirect prompt injection when processing untrusted user data.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

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

Last checked against GitHub 2 weeks ago.

Steadyupdated last month
Other metadata
compatibility
Bundled helpers require Python 3.10+ and use the standard library. The SVG renderer is a first-pass tool, not a full plotting or accessibility-validation system.
metadata
{
  "version": "2.1.0",
  "reviewed": "2026-09-13",
  "source-note": "Tufte-informed methods adapted from previously supplied study material; source book text and images are not bundled. No missing licence terms have been reconstructed."
}

README badge

README badge for tristanmanchester/agent-skills/display-quantitative-information