agentleFS
holtzyholtzy/dataviz-skills/inspiration/SKILL.md

inspiration

Skill16 starsChanged 7 days agoMITView on GitHub

Use BEFORE writing any code that draws a chart, map, plot or dashboard (D3, ggplot2, Matplotlib, geopandas, plotly, Vega…), even for a one-line request like "make a map of X", "fais-moi une carte de X", "visualise Z", and even when the work starts with fetching data. Searches curated galleries of published dataviz as one catalog (dataviz-inspiration.com, Dataviz Index) for 3–5 real references to borrow ideas from — form, annotation, palette, layout — with links back to each source. Also use when asked for chart ideas, examples or references, or to improve a chart that looks generic. Triggers: carte, graphique, visualisation, dataviz, infographie, tableau de bord, chart, map, plot, graph, figure, dashboard, choropleth.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. TakeOff-Team/claude-shortform-video-editor★ 11same name
    2. BillLucky/tuiqiao-skills★ 1same 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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start broad (family + a few bilingual keywords), then add --label to target a technique.

    line 63
  2. Distinctive:

    No hit on the topic? Drop the query and search by family + technique: the *form* matters more than the subject.

    line 64
  3. Distinctive:

    If one source is unreachable the other still answers.

    line 67
  4. Distinctive:

    If the deliverable itself has a sources, notes or colophon area (report, notebook, web page, slide notes), put the same references and …

    line 101
  5. Distinctive:

    Always cite and link back: Every reference you mention carries its original link and its gallery link, and every answer that used the …

    line 108
  6. Distinctive:

    If no source can be fetched and no cache exists, say so and carry on with your own judgment — do not invent references.

    line 113

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Inspiration

Agents draw correct but generic charts: they have no visual culture. This skill gives you one, by searching curated galleries of published visualizations as a single catalog:

SourceWhat it bringsLanguage
dataviz-inspiration.com — Yan Holtz450+ projects (NYT, Bloomberg, independent designers…), tagged by chart type and design technique, each with "what the chart does" + context. CC BY 4.0.English
Dataviz Index — WeDoData300 picks from the Buena Vista Data Club newsletter, tagged by type, theme and format (scrollytelling, data art, 3D, physical…), with an editorial comment.French

Both are read live from their public endpoints and cached for 24 h. Never copy them into a project.

Workflow

1. Frame the question before searching

Work out what the reader must see. That decides the family (it works across both sources):

The reader must see…--family
how values are spreaddistribution
a relationship between variablescorrelation
an order, a comparison of quantitiesranking
shares of a whole, hierarchypartOfAWhole
change over timeevolution
where (geography)map
flows, connections, networksflow

For method references (From Data to Viz caveats, Data Viz Catalogue, Insee and icem7 for French public-statistics style), read references/method.md.

Also note the techniques you may need (annotation, small multiples, direct labeling, highlight, bivariate coloring, uncertainty, scrollytelling…) and the medium (static or interactive).

2. Search

python3 scripts/search_viz.py "<keywords in English AND French>" --family <family> [options]

scripts/ is relative to this skill's directory. Python 3.9+, standard library only.

OptionMeaning
"query"free text over title, descriptions, author, types, labels, themes (accents and case ignored). Give keywords in both languages ("election élection turnout participation"): one gallery is English, the other French.
--family Fchart family, across sources
--type Texact chart type, repeatable (OR) — --vocab lists them (choropleth, sankey, cartographies…)
--label Ltechnique or format, repeatable (AND): annotation, small multiples, scrollytelling, 3d, data art…
--source Sdataviz-inspiration or datavizindex only
--tool T, --interactive / --no-interactive, --luminosity light|dark, --since 2022narrow down
--limit Ndefault 8
--format jsonfull records
--thumbs DIRalso download the results' thumbnails into DIR, to look at them
--vocablist families, chart types, labels and themes with counts — run it when unsure of names

Search tactics:

  • Start broad (family + a few bilingual keywords), then add --label to target a technique.
  • No hit on the topic? Drop the query and search by family + technique: the form matters more than the subject. A good migration chart can inspire an election chart.
  • Without a query, results come favorites first, then most recent.
  • If one source is unreachable the other still answers; the output says which one is missing.

3. Look before you borrow

Pick the 3–5 most relevant results. Download their thumbnails with --thumbs <scratch dir> and view them (images you can read; some are animated GIFs — you see the first frame). The text says what the designer did; the image shows how dense, how annotated, how colored it really is.

4. Present the references, then design

For each reference you keep, give the user:

  • title and author;
  • two links, always: the original work (Original) and the gallery page where it was found (Found via …). The galleries did the curation: sending readers back to them is the point;
  • the specific idea to borrow (e.g. "annotations placed directly on the peaks instead of a legend", "bivariate palette with a 3×3 key", "small multiples sorted by slope");
  • why it fits this data and this audience.

Then propose the design, saying which idea comes from which reference. Adapt the ideas — never present a copy of someone else's chart as original work.

For example:

South Gaza's services and a doubling of population — Bloomberg · original · found via dataviz-inspiration.com → borrow: a bivariate palette with a 2D key to cross two variables on one map, plus a before/after toggle to show the shift.

End with a linked credit line for each gallery you used:

References found via dataviz-inspiration.com (Yan Holtz, CC BY 4.0) and Dataviz Index (WeDoData).

If the deliverable itself has a sources, notes or colophon area (report, notebook, web page, slide notes), put the same references and credit line there too.

Rules

  • Images are not reusable. Thumbnails are screenshots of work by their authors. Look at them; never embed, ship or redistribute them.
  • Always cite and link back. Every reference you mention carries its original link and its gallery link, and every answer that used the galleries ends with the linked credit line. No reference without its links, ever.
  • Yan Holtz's catalog data is CC BY 4.0: credit it. Dataviz Index comments are WeDoData's editorial text: paraphrase them and link to the entry, do not republish them.
  • If no source can be fetched and no cache exists, say so and carry on with your own judgment — do not invent references.
  • Some entries have an empty description: rely on the context and the thumbnail.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.