visual-explain
/visual-explain
Explain concepts visually using ASCII diagrams, flow charts, tables, and structural maps. Use when asked to explain, compare, or show how something works.
- Author
- egregore-labs ↗
- Repository
- egregore ↗
- Licence
- MIT
- Last repository change
- 16.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 1
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 16.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
Explain concepts visually using ASCII diagrams, flow charts, tables, and structural maps. Use when asked to explain, compare, or show how something works.
Original author description
Explain concepts visually using ASCII diagrams, flow charts, tables, and structural maps. Use when asked to explain, compare, or show how something works.
How it works
- Structured UX parity
SKILL.md preview
--- name: visual-explain description: 'Explain concepts visually using ASCII diagrams, flow charts, tables, and structural maps. Use when asked to explain, compare, or show how something works.' --- <!-- generated-by: bin/codex-sync-skills.sh --> # Egregore visual-explain Adapter This adapter runs the canonical Egregore workflow for `visual-explain`. Its one maintained body is `.claude/skills/visual-explain/SKILL.md`; read that file completely and follow it here. Use the project shell and filesystem directly. Do not invoke Claude Code commands. Translate interactive choices to structured Codex question tooling when it is available; otherwise render compact numbered choices with an `Other:` option and wait for the user. ## Structured UX parity This workflow has a Claude skill with user-visible structured output. After reading `.claude/skills/visual-explain/SKILL.md`, reproduce the same visible UX in Codex: - Preserve TUI boxes, markdown tables, rich cards, browser artifact rendering, exact confirmation blocks, and "no preamble" rules from the source skill. - Use the source skill's frame width, section order, labels, status footer, and examples as the contract for the final response. - Never replace a required box/table/card/artifact view with a prose summary unless the user explicitly asks for a summary. - When the source says to output a TUI box directly, paste that box as the visible response, preferably in a `text` fenced block. - If the canonical body says the command's stdout is the card and must not be repeated, that rule assumes a host that displays command output in full; in Codex, paste the card once as the visible response in a `text` fenced block and do not print it a second time. - Never show raw JSON, raw command output, or unformatted script output when the source skill requires formatted status or rendered output. 1. Read `.claude/skills/visual-explain/SKILL.md` for the workflow details. 2. Run the referenced `bin/` scripts directly from Codex. 3. Treat graph and publish steps as best-effort unless that workflow explicitly says they are required. 4. For every external notification, follow `.claude/context/notification-consent.md`: plan without sending, then show a separate exact Send / Edit / Cancel checkpoint. Never infer notification consent from the workflow request or a batch approval. 5. Keep local-mode behavior filesystem-first and avoid graph or notification calls when `egregore.json` declares `"mode": "local"`. 6. Never call the deprecated `egregore-handoff` CLI for Egregore project handoffs.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · egregore-labs/egregore | 100 | MIT |
| egregore-labs/egregore | 100 | MIT |
Database snapshot: 13.11.2026 · package version f23af15b7791 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90pr-visual-explainer
Use when the user asks to explain a pull request visually, create an HTML walkthrough, show before-and-after behavior, or add diagrams for a PR. Triggers automatically for requests such as "explain this PR" when a visual artifact would materially improve understanding; does not… - 100plantuml-ascii
Generate ASCII art diagrams using PlantUML text mode. Use when user asks to create ASCII diagrams, text-based diagrams, terminal-friendly diagrams, or mentions plantuml ascii, text diagram, ascii art diagram. Supports: Converting PlantUML diagrams to ASCII art, Creating sequence… - 95mermaid
Render Mermaid diagrams as SVG or ASCII art using beautiful-mermaid. Use when users need to create flowcharts, sequence diagrams, state diagrams, class diagrams, or ER diagrams. Supports both graphical SVG output and terminal-friendly ASCII/Unicode output. - 95mermaid
Render Mermaid diagrams as SVG or ASCII art using beautiful-mermaid. Use when users need to create flowcharts, sequence diagrams, state diagrams, class diagrams, or ER diagrams. Supports both graphical SVG output and terminal-friendly ASCII/Unicode output. - 100ascii-schemas
Generate ASCII schemas, diagrams, and UI wireframes using Unicode box-drawing characters (wiretext conventions). Use when creating architecture diagrams, entity-relationship models, database schemas, flow charts, deployment topologies, sequence diagrams, data flow… - 100visual-explainer
Generate self-contained HTML pages that visually explain technical material — systems, code changes, plans, data. Use when the user asks for any diagram or visual explanation, when they want a slide deck or a longform document (user guide, how-to, reference page), when another…