visual-explainer
Skill34 starsChanged 20 days agoMITView on GitHub
Generate a single self-contained HTML page that visually explains a system, a plan, a comparison, or a set of data. Use for "/visual-explainer", "make a diagram of", "show this visually", or when a complex table or architecture would land better as a styled page.
27 other projects use a version of this.
Adopted by
Most recently taken up by
- mhylle/claude-skills-collectiontheir own version, first seen Nov 8, 2026
- tsukhani/jclawtheir own version, first seen Nov 5, 2026
- maxbuildog/skillstheir own version, first seen Nov 1, 2026
- coco-research/cocotheir own version, first seen Nov 1, 2026
- lubshad/skillstheir own version, first seen Nov 1, 2026
- fuadnafiz98/skillstheir own version, first seen Oct 15, 2026
Used with
Projects with it also use verification-before-completion.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OpenAISkillverification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Also in 3 projects that use this
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- vercel-labs/vgpu★ 2.6ksame name
- coco-research/coco★ 797same name
- jamditis/claude-skills-journalism★ 449same name
- luanmorenommaciel/agentspec★ 256same name
- tsukhani/jclaw★ 42same name
- mhylle/claude-skills-collection★ 20same name
- parthjshah95/visual-planning-skills★ 14same name
- jscraik/Agent-Skills★ 9same name
- alexandergirardet/visual-explainer★ 4same name
- sublimotion/agent-aiops-on-aws★ 4same name
17 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 repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-agentSkill
- build-listSkill
- chart-tufteSkill
- councilSkill
- design-precheckSkill
- document-exportSkill
- handoverSkill
- index-memorySkill
- log-decisionSkill
- mcp-debugSkill
- meeting-prepSkill
- memory-debtSkill
- merge-contactsSkill
- morning-briefSkill
- post-callSkill
- reflectSkill
- setupSkill
- system-auditSkill
- tasksSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
1
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 15
All CSS inline in a <style> block.
- Very specific: line 18
Grade any chart: If the page holds a quantitative chart (bar, line, scatter, area), run /chart-tufte on it and fix what it flags before …
- Distinctive: line 26
Prefer this over a large ASCII table (four or more rows, or three or more columns).
“Common” is measured: kept by at least 6 in 10 of the 25 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
Visual Explainer
Produce one standalone HTML file that explains something clearly. Good for architecture overviews, plan reviews, before/after comparisons, timelines, and dashboards.
Steps
- Clarify the subject and the audience. What is being explained, and who reads it? That sets the depth.
- Choose the form: a flow diagram, a comparison table, a timeline, a layered architecture, a metric dashboard.
- Build one self-contained
.htmlfile:- All CSS inline in a
<style>block. No external stylesheets, no CDN links, no network dependencies. The file must open correctly offline by double-clicking it. - Readable typography, generous spacing, a restrained palette.
- Content-first: the explanation carries the page, decoration supports it.
- All CSS inline in a
- Grade any chart. If the page holds a quantitative chart (bar, line, scatter, area), run
/chart-tufteon it and fix what it flags before saving. - Save to
reports/(create the directory if needed) asYYYY-MM-DD-<slug>.html. - Tell the user the path so they can open it.
Principles
- Self-contained or it does not count. One file, opens offline.
- The page answers a question. Lead with that answer, same as any other output.
- Prefer this over a large ASCII table (four or more rows, or three or more columns).
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.