infographic-creator
Skill0 starsChanged 3 months agoMITView on GitHub
Designs the layout, color strategy, and narrative structure of data-driven infographics. Use when creating infographics, visual summaries, one-page data reports, or combining multiple data points into a single visual.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- vansvost-arch/claude-skillstheir own version, first seen Oct 15, 2026
- cosZone/astro-koharutheir own version, first seen Oct 8, 2026
- antvis/Infographictheir own version, first seen Oct 8, 2026
- stefanomartiradonna/claude-skillstheir own version, first seen Aug 14, 2026
- brunohapp/skills-de-infograficotheir own version, first seen Aug 6, 2026
- ElyzeSolutions/skillstheir own version, first seen Aug 6, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- antvis/Infographic★ 7ksame name
- cosZone/astro-koharu★ 470same name
- ninehills/skills★ 280same name
- ElyzeSolutions/skills★ 1same name
- zhangdszq/vk-skills★ 1same name
- brunohapp/skills-de-infografico★ 0same name
- stefanomartiradonna/claude-skills★ 0same name
- vansvost-arch/claude-skills★ 0same 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.
- dashboard-designSkill
- data-storytellerSkill
- data-visualizationSkill
- table-designSkill
- visualization-reviewSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
All shared rules in ../../assets/core-standards.md apply.
- Distinctive: line 15
No fluffy designs, garish oversized numbers, or cartoonish graphics.
- Very specific: line 27
Follow the branding workflow in ../../assets/core-standards.md (brand assets, light-color substitution, dark-background reversal, 10% rule).
- Distinctive: line 30
Use preattentive attributes (color, size, position) to guide the audience through the storyboard.
- Distinctive: line 33
Verify deterministically — do not eyeball contrast:
- Distinctive: line 38
Add redundant encoding; draft alt text per panel for web output.
- Distinctive: line 41
Run the "where are your eyes drawn?" test on each panel and the whole.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Infographic Creator
The user's request: "$ARGUMENTS"
Critical Constraints
All shared rules in ../../assets/core-standards.md apply. Infographic-specific additions:
- An infographic must tell a cohesive, structured story — not a disjointed collection of facts.
- No fluffy designs, garish oversized numbers, or cartoonish graphics. Infographics must inform.
- Memorability tradeoff: for public-facing infographics where recall matters more than precision, selective embellishment (icons, distinctive forms) is acceptable — but data encodings (bar lengths, positions, slopes) must remain accurate.
Instructions
Step 1: Understand Context and Storyboard
Articulate the "3-minute story" — the narrative distilling the "so-what." Storyboard with a beginning, middle, and end; chunk related facts. Use the context-capture framework in references/audience-context.md.
Step 2: Choose Displays and Maximize Data-Ink
Simple text for 1–2 key numbers, zero-baseline bars for comparisons, lines for trends. Strip clutter. Apply the hierarchy rules in ../data-visualization/references/design-principles.md.
Step 3: Apply Branding and Color
Follow the branding workflow in ../../assets/core-standards.md (brand assets, light-color substitution, dark-background reversal, 10% rule).
Step 4: Focus Attention and Apply Text
Use preattentive attributes (color, size, position) to guide the audience through the storyboard. One insight per panel, action title per chart, annotations next to the data, consistent margins.
Step 5: Accessibility Check
Verify deterministically — do not eyeball contrast:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/check_contrast.py" '#FG' '#BG'
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/check_palette.py" '#hex1,#hex2,...'Add redundant encoding; draft alt text per panel for web output.
Step 6: Validate
Run the "where are your eyes drawn?" test on each panel and the whole. If the gaze misses the focal point, return to Step 4.
Step 7: Generate Output
Produce the infographic in the user's preferred format. After generating, run the visualization-review skill on the output (P0 checks at minimum).
Troubleshooting
"Make it cool with 3D elements and lots of graphics": 3D skews data. Offer strategic brand colors, clean alignment, and quality typography instead.
Overwhelming and chaotic: revert to the 10% rule — only the single most important data point per section gets the highlight color.
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.

