visual-explainer
Skill0 starsChanged 4 months agoMITView on GitHub
Create a self-contained HTML explainer for systems, workflows, diagrams, timelines, comparisons, or data-heavy summaries when plain terminal text would be painful to read. Use when the output naturally wants a visual artifact instead of chat prose.
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
- chacosoldier/compabobtheir own version, first seen Oct 23, 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
- chacosoldier/compabob★ 34same name
- mhylle/claude-skills-collection★ 20same name
- parthjshah95/visual-planning-skills★ 14same name
- jscraik/Agent-Skills★ 9same name
- alexandergirardet/visual-explainer★ 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 repository37 other files it gives its agents.
- adr-logSkill
- adversarial-reviewSkill
- ai-writing-detoxSkill
- autonomous-video-pipelineSkill
- browser-tutorial-videoSkill
- codex-execution-packSkill
- continuity-ledgerSkill
- github-mobile-opsSkill
- github-seoSkill
- idea-validationSkill
- illustration-promptSkill
- issue-control-loopSkill
- justdoitSkill
- lazy-seniorSkill
- long-context-dispatchSkill
- openclaw-councilSkill
- parallel-worktreesSkill
- playwrightSkill
- product-councilSkill
- product-shapingSkill
- public-artifact-laneSkill
- readme-generatorSkill
- screenshotSkill
- session-to-postSkill
- spec-bundleSkill
- spreadsheetSkill
- spreadsheet-tabular-analysisSkill
- spreadsheet-xlsx-editSkill
- tool-scoutSkill
- transcribe-basicSkill
- transcribe-diarizeSkill
- transcribeSkill
- triage-findingSkill
- video-builderSkill
- video-render-runSkill
- video-spec-builderSkill
- work-shapingSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
4
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 10
Do not use when: a short plain-text answer would already communicate the structure clearly.
- Distinctive: line 22
Prefer semantic HTML and a useful first screen over generic dashboard sludge.
- Distinctive: line 24
Use Mermaid only when automatic layout helps more than it hurts.
- Distinctive: line 25
If the user asked for a wide table or large structured comparison, render it in HTML instead of pasting a painful terminal table.
“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
Metadata
- Trigger when: the best output is a browser-readable HTML artifact rather than a wall of text.
- Do not use when: a short plain-text answer would already communicate the structure clearly.
Skill Purpose
Show structure visually through a single portable HTML artifact so complex systems, tables, and flows become readable at a glance instead of buried in chat.
Instructions
- Choose the right visualization type first. Use
~/.codex/skills/visual-explainer/references/routing.mdif you need help selecting between architecture, timeline, comparison, table, or other visual forms. - Build one self-contained HTML artifact with one clear visual direction. Reuse templates from
~/.codex/skills/visual-explainer/assets/templateswhen they help, and validate against~/.codex/skills/visual-explainer/references/style-rules.mdand~/.codex/skills/visual-explainer/references/quality-checks.mdbefore delivery. - Save the file to a sensible workspace path, open or inspect it when possible, and return the path plus a short note about what the artifact shows.
Non-Negotiable Acceptance Criteria
- Prefer semantic HTML and a useful first screen over generic dashboard sludge.
- The output is one self-contained
.htmlfile unless the user explicitly asked for a multi-file artifact. - Use Mermaid only when automatic layout helps more than it hurts.
- If the user asked for a wide table or large structured comparison, render it in HTML instead of pasting a painful terminal table.
Output
- The HTML file path.
- A short description of what the explainer shows and how it is organized.
- Any note about template reuse, browser inspection, or unresolved visual caveats.
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.