Skip to content
Back to skills

Visual Explainer

ASecurity

Build polished visual explainers as zo.space pages. Creates public routes at /explain/[slug] and keeps each explainer shareable at a stable URL.

  • 11 stars
  • 0 votes
  • 1 copy
  • 36 views
  • Added September 10, 2026
designbashreact

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 10, 2026

npx -y skills add luokai0/ai-agent-skills-by-luo-kai --skill visual-explainer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Visual Explainer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Visual Explainer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/luokai0-visual-explainer/badge)](https://www.skillsdirectory.com/skills/luokai0-visual-explainer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: visual-explainer
description: Build polished visual explainers as zo.space pages. Creates public routes at /explain/[slug] and keeps each explainer shareable at a stable URL.
compatibility: Created for Zo Computer
metadata:
  author: skeletorjs
---

# Visual Explainer (Zo)

Use this skill when the user asks for a visual explanation, architecture breakdown, implementation walkthrough, roadmap, comparison, or technical explainer page.

This Zo-native version publishes explainers to zo.space route paths:
- `/explain/<slug>` for each explainer page
- optional `/explain` index page that links to all explainers

## Required Behavior

1. Always publish explainers as zo.space page routes via `update_space_route`.
2. Route path format is always `/explain/<slug>`.
3. Default to `public=True` unless the user explicitly asks for private visibility.
4. After each publish/update, run `get_space_errors` and fix issues before proceeding.
5. Respond with the live URL: `https://<handle>.zo.space/explain/<slug>`.

## Workflow

1. Convert the requested title/topic into a URL-safe slug.
2. Create or update route `/explain/<slug>` with a self-contained React page.
3. Use a clear visual system:
- Distinctive typography (avoid default stacks)
- Strong color direction with CSS variables
- At least one meaningful visual (diagram section, timeline, system map, or comparison grid)
- Mobile-responsive layout
4. If this is part of a series, also update `/explain` with links to recent explainers.
5. Validate with `get_space_errors`.

## Route Template

Start from `assets/explainer-page.tsx` and adapt content per topic.

## Fast Slug Helper

Use `scripts/slugify.sh`:

```bash
bash Skills/visual-explainer/scripts/slugify.sh "My Explainer Title"
```

Files in this skill

  • DISPLAY.json69 B
  • SKILL.md1.7 KB
  • assets/explainer-page.tsx3.3 KB
  • scripts/slugify.sh417 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.