infographic
Skill0 starsChanged 20 days agoMITView on GitHub
Create evidence-based infographics, visual explainers, research posters, charts, timelines and social carousels, including layouts that embed Mermaid, technical figures, and CSS-animated SVG sequenced infographics (icon pop, staggered stats, draw-on connectors, tabular-nums, prefers-reduced-motion). Use when asked to make an animated infographic, sequenced reveal, stagger icons and stats, communicate a sourced claim visually, compose a data story, annotate authentic evidence, critique an infographic or adapt it for web, print, slides or social. Deliver motion as SVG only, not video or MP4. Bundled helpers cover PNG from SVG, optional themed Mermaid export, build_animated_svg.py, and raster prefs when API keys exist.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- CatCatUncle/openworkbuddytheir own version, first seen Nov 5, 2026
- arnaugonzalez/infographic-post-skilltheir own version, first seen Nov 1, 2026
- magnus919/agent-skillstheir own version, first seen Nov 1, 2026
- ArnavPuri/designskillstheir own version, first seen Nov 1, 2026
- duncan-buildroom/profit-room-skillstheir own version, first seen Oct 13, 2026
- ZJU-REAL/Easeltheir own version, first seen Oct 13, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- ZJU-REAL/Easel★ 4.5ksame name
- claude-office-skills/skills★ 433same name
- CatCatUncle/openworkbuddy★ 398same name
- magnus919/agent-skills★ 172same name
- duncan-buildroom/profit-room-skills★ 18same name
- jincai/openclaw-skills★ 18same name
- ArnavPuri/designskills★ 17same name
- costiash/eliviz★ 7same name
- remybroun/infographic★ 3same name
- amigoscode/skills★ 1same name
3 more not listed
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 repository57 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/comments.mdcCursor rule
- .cursor/rules/commit-messages.mdcCursor rule
- .cursor/rules/git-workflow.mdcCursor rule
- .cursor/rules/manage-stack.mdcCursor rule
- .cursor/rules/no-worktrees.mdcCursor rule
- manage-stackSkill
- convert-as-skillSkill
- create-agentSkill
- create-agents-mdSkill
- create-commandSkill
- create-hookSkill
- create-ruleSkill
- create-skillSkill
- retrospectiveSkill
- super-architectureSkill
- super-cachingSkill
- super-elixirSkill
- super-nodejsSkill
- super-protobufSkill
- super-tech-blueprintSkill
- atomic-semantic-commitSkill
- code-reviewSkill
- create-bruno-collectionSkill
- create-documentationSkill
- create-ticketsSkill
- ready-specSkill
- write-adrSkill
- write-changelogSkill
- write-mr-descriptionSkill
- write-planSkill
- write-postmortemSkill
- write-runbookSkill
- noslopSkill
- output-saversSkill
- safe-refactorSkill
- tddSkill
- verifySkill
- get-movingSkill
- later-listSkill
- standupSkill
- challenge-meSkill
- codebase-learnerSkill
- researchSkill
- second-opinionSkill
- traceSkill
- color-kitSkill
- design-system-kitSkill
- diagramSkill
- product-polish-workflowSkill
- prototype-wireframeSkill
- ui-ux-kitSkill
- evidenceSkill
- find-skillsSkill
- handoffSkill
- rumblingSkill
- use-levistackSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
1
Distinctive
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
- Distinctive: line 76
Start with surface router when the deliverable could be a poster, deck, cover, social package, or declarative DSL export.
- Very specific: line 148
Run python3 -m unittest discover -s <infographic-skill>/scripts -p 'test_*.py' for checks in scripts/test_render_bars.py, …
“Common” is measured: kept by at least 6 in 10 of the 10 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
Give the reader a clear claim and a visible path to its evidence. Composition must clarify the relationship, not make weak evidence look certain.
Callable catalog skills are listed in frontmatter metadata.invokes (and related_skills for discovery). Load a companion skill when its when line matches the task. This skill still owns evidence, layout, and delivery.
Start with surface router when the deliverable could be a poster, deck, cover, social package, or declarative DSL export.
Planning flow: design spec workflow → layout types → design specification template. Long sources also use structured content and project artifacts.
Define and source the claim
Read the supplied material and existing brand guidance. Record the reader, bounded takeaway, surface, final reading size and output paths in the brief. Infer routine choices and proceed within the task. Ask only when a missing fact changes the claim. Keep project assets outside this installed skill.
Read evidence before designing. Record source locators, dates or revisions, transforms, uncertainty and reuse rights. Separate sourced facts, reproducible measurements, editorial inference, unknowns and synthetic examples. Put important limits beside the claim in the artifact. An unsupported factual claim must be corrected, sourced or marked unknown before factual delivery. Missing records do not mean zero or absence. association does not prove cause. Verify time-sensitive facts from current primary sources when available and disclose inaccessible evidence.
Use synthetic values only for a requested mockup, visibly labeled in the asset. A model-generated chart, quote, screenshot or plausible curve is not evidence. Use real captures for product claims, retaining state and capture context. Generated illustration can explain a metaphor. Keep factual marks, exact text and numbers in deterministic editable layers.
Choose the visual relationship
| Work | Read |
| Pick poster vs deck vs cover vs social vs declarative path | Surface router |
| Keyword-led layout and mood for drafts | Layout mood catalog, data/layout-keywords.json |
| Multi-section source before build | Structured content |
| Confirm before raster or painted output | Confirmation gates |
| Prefs, backends, API raster CLI | Raster Python |
| Fresh stats or research poster | Research quality bars |
| Reading deck or raster slide batch | Slide deck surfaces |
| Social post, thread, or article package | Social X surfaces |
| Article or deck cover hero | Cover hero surfaces |
| Optional declarative infographic DSL | Declarative infographic syntax |
| Sequenced animated SVG (no video encode) | Animated SVG sequenced, Choreography |
| Layout type pick and wireframe planning | Layout types, Design spec workflow |
| Comparison, evidence lanes, network, map, timeline or batch layout | Composition |
| Mermaid, flow, architecture or schema figure inside the layout | Technical figures, Technical figure package |
| Numeric marks, scales, denominators and transformations | Data graphics |
| Responsive web, poster, print, slides, social or motion | Formats |
| Poster colors, Mermaid theme on embedded figures | Visual theming |
| PNG from SVG, themed Mermaid raster for layout slots | Figure exports |
| Critique, repair or final inspection | Review |
| Schedule copy with the image, scheduler payloads | Publishing gate |
| Rights, attribution, public or client release | Publication boundaries |
| Example prompts and agent default | Prompt recipes, agents/openai.yaml |
Choose a dominant relationship before styling. Comparable values need a common frame. Dates need honest spacing or an explicit categorical sequence. Links and spatial position need defined meanings. Explain the reading order and layout briefly, then build. A local preview is a review artifact, not an automatic permission gate.
Compute chart geometry from retained data and transformations. Check units, period, population, denominator, missing values, totals, rounding and uncertainty. Bars use a zero baseline. Area encodings scale area rather than radius. Preserve comparison scales across related panels. Keep raw and derived data distinct, and do not invent confidence intervals or missing values.
Compose and produce
Reuse the project's fonts, semantic colors, and design tokens when the repo defines them. A single graphic can use a small local style. Keep copy plain and exact: preserve citations, quantities, units and uncertainty in labels and captions.
Build exact charts and labels with editable SVG, HTML, a plotting tool or an appropriate layout source. Keep its data and generator. Use existing local tools first. Follow the format guide and installed tool help. Do not depend on a remote renderer or guess helper APIs. Report the exact missing dependency, blocked export and check that could not run. Preserve useful source and accessible text. Do not upload private material as an automatic fallback.
Recompose each requested aspect ratio instead of stretching it. Keep caveats and sources attached when panels reflow or a carousel page is shared alone. Verify current platform limits before claiming compliance. A familiar aspect ratio alone proves nothing about current upload rules.
Check and deliver
Run the review against the actual source and delivered file. First repair claims, calculations and inaccessible essential information. Then refine the layout. Inspect at the expected feed width, presentation distance or physical print size. For web, check narrow layouts, zoom and keyboard/touch access to interactive detail. Use measured contrast evidence before claiming a contrast pass. Supply labels or patterns alongside hue and an accessible description or data table.
For motion, keep every claim and caveat available in a complete still. Follow sequenced infographic choreography for tier order, pacing, and final hold. Declare step order and timing, avoid rapid flashes, and inspect the encoded first/final frames and meaningful steps. Test reduced motion in SVG/HTML and provide controls for long or interactive playback. Pair animated SVG with a still. Motion cannot be the only way to read a fact. Do not ship MP4 or GIF as the primary deliverable from this skill.
Inspect the exact exports: SVG structure and live text, PNG dimensions and background, PDF page size and fonts, or the actual native source in its editor where relevant. A parser pass cannot prove visual quality or editor behavior. After repairs, regenerate and inspect the affected file. For compression, preserve originals and compare bytes and readability.
Deliver editable source, data and generator where used, requested exports, accessible text, the source/transform ledger and a receipt listing dimensions, versions, render commands, checks run and remaining limits. Report critique findings as observed problems with concrete fixes, not invented quality scores. Keep delivery local unless publication was requested. An authorized publishing flow receives the exact asset, copy, alt text and destination for its own checks. When copy ships with the image, run publishing gate and publication boundaries.
Tools and examples
scripts/render_bars.py INPUT.json OUTPUT.svgbuilds an original zero-baseline bar figure with sources and a text equivalent. It supports nonnegative comparable values only. Use it for that chart, not as a template for every infographic.scripts/png_from_svg.py INPUT.svg OUTPUT.png --width 1200rasterizes a layout or bar SVG with localrsvg-convert.scripts/export_figure.py png|png-strict|mermaid-theme|mermaid-svg|themesdelegates themed Mermaid and strict static SVG checks to optional export scripts whenLEVISTACK_DIAGRAM_SCRIPTSor the default sibling path is set.scripts/sibling_diagram.pyresolves that path.scripts/image_generate.pyloadsinfographic.prefs.json/infographic.extend.md, lists raster backends, resolvespreferred_raster_backend, and calls image APIs when keys are set. Useagent-nativewhen the host should call its own image tool. See raster Python.scripts/build_animated_svg.py INPUT.json OUTPUT.svgwrites a self-contained sequenced infographic with CSS keyframes andprefers-reduced-motion. See animated SVG sequenced and UPSTREAM.md.evals/sample-bars.jsonis visibly synthetic sample data.evals/cases.jsoncovers research, archival, timeline, chart, screenshot, carousel and critique requests, plus boundary cases.examples/cfo-capacity/brief.mdis a fictional worked campaign brief (convergence layout, optional technical figure).references/prompt-recipes.mdlists starter prompts.agents/openai.yamlandagents/README.mdpackage the default prompt for agent hosts.
Run python3 -m unittest discover -s <infographic-skill>/scripts -p 'test_*.py' for checks in scripts/test_render_bars.py, scripts/test_export_figure.py, scripts/test_image_generate.py, and scripts/test_build_animated_svg.py. Exercise the request cases against the selected workflow and record observed checks separately from pending tool checks.
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.

