graphics
Skill2 starsChanged 9 days agoApache-2.0View on GitHub
Shared machinery for diagrams, infographics and charts, for the other skills (notes) and directly. Use when a STRUCTURAL picture from a ready template is needed - a list, a comparison, SWOT, a funnel, a roadmap, a hierarchy - or a chart from real data with considered typography; or when another skill reaches the step "draw a diagram / chart" and is choosing the tool.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- g-cqd/skillstheir own version, first seen Oct 23, 2026
- IamK77/Skilltheir own version, first seen Oct 12, 2026
- bloxy-studios/shorts-studiotheir own version, first seen Oct 1, 2026
- MyAiFreedomSystems/incredagentstheir own version, first seen Aug 14, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- g-cqd/skills★ 2same name
- IamK77/Skill★ 2same name
- bloxy-studios/shorts-studio★ 0same name
- MyAiFreedomSystems/incredagents★ 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 repository20 other files it gives its agents.
- browserSkill
- clean-memorySkill
- codebase-designSkill
- commitSkill
- desktopSkill
- grillingSkill
- implementSkill
- latexSkill
- memory-reviewSkill
- mistakeSkill
- notesSkill
- pdfSkill
- routerSkill
- setupSkill
- skill-quality-suiteSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- vault-indexSkill
- videoSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
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 63
No picture is embedded unchecked: render, look at it (Read a PNG snapshot, or read the SVG), and only then hand it to the calling skill.
“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
graphics: diagrams and charts
One tool for two different jobs: structural infographics from a template (list, steps,
comparison, SWOT, funnel, hierarchy) and charts from real data (comparison, series, before/
after). The first is a vendored library (AntV Infographic), fully offline. The second is our own
generators (chart_paired.py, chart_bars.py). Everything lives in this skill; nothing is
fetched from other repositories at run time.
This skill does not decide where the finished picture goes or in what format: the calling
skill knows that (notes embeds ![[...].svg] in Obsidian). graphics is responsible only for
producing the picture and making sure it does not lie.
Scripts: ${CLAUDE_PLUGIN_ROOT}/skills/graphics/scripts (written <scripts> below and in the references):
scripts/chrome_selfcheck.py, scripts/extract_svg.py, scripts/chart_paired.py, scripts/chart_bars.py.
Choosing the tool
| Need | How | Reference |
| List / comparison / SWOT / funnel / roadmap / hierarchy: structure, not data | AntV Infographic (vendored), DSL to SVG in headless Chrome | references/antv-infographic.md |
| Before/after, paired samples, real units per record | scripts/chart_paired.py (no Chrome) | references/chart-generators.md |
| Comparing categories, dashboard pace, ranking, KPIs | scripts/chart_bars.py (no Chrome) | references/chart-generators.md |
| Color, curves, continuous geometry (no template) | a hand-made generator (Python + SVG) | ${CLAUDE_PLUGIN_ROOT}/skills/notes/references/diagrams.md |
| Flowchart / ER / UML / BPMN | Mermaid / PlantUML | outside this skill |
Self-check: before the first picture of a session, not before each
Looking at the finished render (always required, below) catches a wrong picture. It does not
catch a silently broken tool: Chrome not found, --dump-dom taking the page before the render
finished, the vendored library not running (for example a BOM lost on a version update, see
references/antv-infographic.md). Such a tool returns a plausible but empty or cut result, and
looking at it shows nothing. So a known reference goes through the same pipeline before this
session's real renders are trusted:
uv run --no-project "<scripts>/chrome_selfcheck.py"Chrome or Edge is found automatically (--chrome <path> to override). Exit 0: the pipeline is
healthy and works fully offline. Non-zero: do not trust this session's renders until the cause is
fixed (the message names what broke). --skip-vendor checks only the base pipeline (Chrome +
--dump-dom + extract_svg.py).
Rendering and extracting the SVG
scripts/extract_svg.py pulls <svg>...</svg> (nested svg icons included) out of a
chrome --headless --dump-dom dump. Shared by AntV Infographic and any other DSL or HTML render
that puts its result in a container. The full recipe (HTML wrapper, Chrome flags,
--virtual-time-budget) is in references/antv-infographic.md.
Checking the result: always required
No picture is embedded unchecked: render, look at it (Read a PNG snapshot, or read the SVG),
and only then hand it to the calling skill. A defect turns up almost every time. What to check and
in what order: ${CLAUDE_PLUGIN_ROOT}/skills/notes/references/diagrams.md, section "Checking"; it applies to any
picture, whatever its source.
References
references/antv-infographic.md: the DSL, template categories, the render recipereferences/chart-generators.md:chart_paired.py/chart_bars.py, the two reading paces
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.