visual-eli5

Generates self-contained HTML explainers with large diagrams and minimal text for any topic.

1|Updated Jul 16, 2026
One-click install
npx skills add https://github.com/sota411/codex-config --skill visual-eli5-sota411
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: visual-eli5
Source: https://github.com/sota411/codex-config/tree/main/user-skills/visual-eli5
Command: npx skills add https://github.com/sota411/codex-config --skill visual-eli5-sota411

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Explaining an unfamiliar topic to a complete beginner often produces long walls of text that are hard to absorb. This Skill turns any topic into a single self-contained HTML page built around one large visual and very few words, so the core idea is understood at a glance. ## Core Features & Use Cases - Single-file HTML output: Produces one self-contained index.html with inline CSS and SVG, no external scripts, fonts, or images, saved to a timestamped artifact directory. - Minimal visual selection: Chooses the smallest fitting representation for the topic, such as a labeled diagram, comparison table, flowchart, annotated code, diff, or chart based only on verified data. - Diagram integration and validation: Delegates formal diagrams to the diagram-design workflow, runs self_check.py, and embeds only validated SVG with accessibility attributes. - Responsive and accessible verification: Checks the result at desktop width, 390px mobile width, and 200% text zoom for overflow, overlap, and readability. - Use Case: Ask for an explanation of how DNS works, and receive a single HTML page with one large labeled diagram and a few short captions instead of a long prose answer. ## Quick Start Use $visual-eli5 to explain how DNS resolution works as a big picture with few words.

Frequently Asked Questions about visual-eli5

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a visual HTML explainer for a technical topic?▼

Invoke $visual-eli5 followed by the topic, and it produces one self-contained HTML file with a large central diagram and minimal text. The output is saved to a timestamped directory under ~/.codex/artifacts/visual-eli5/.

What visual formats can an HTML explainer use?▼

The skill picks the smallest fitting representation: labeled diagrams, comparison tables, pseudocode, flowcharts, annotated code, file trees, diffs, or charts from verified data. Mermaid is redrawn as static SVG rather than embedded as a runtime.

Does the generated HTML require external libraries or JavaScript?▼

No. The output inlines all CSS and SVG, loads no external stylesheets, fonts, scripts, or images, and avoids JavaScript and animation by default so the page works fully offline as a static document.

Can the explainer handle mobile and accessibility requirements?▼

Yes. The HTML is verified at 390px width and 200% text zoom for overflow and overlap, uses a mobile vertical layout when needed, and includes readable names, sufficient contrast, non-color cues, and visible focus states.

When should I not use a visual HTML explainer?▼

Avoid it when the topic cannot be uniquely determined from the request or conversation, since the skill asks one clarifying question first. It is also unsuitable when you need interactive widgets, quizzes, or stored progress, which it explicitly excludes.