Skip to main content
skill CX Codex

vox-explainer · dotslashsimran — Claude Code skill for explainer videos

The vox-explainer Claude Code skill makes Vox-style explainer graphics or a faceless video. It runs on requests for voiceover-led visuals, animated quotes, or stats.

MIT ★ 541 updated 2026-11-09

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add dotslashsimran/simcraft --skill vox-explainer -a claude-code
Open on GitHub

What vox-explainer does

The skill turns a voiceover into a graphic-led video, syncing each frame and highlight to the spoken words. It starts with the audio, breaks the transcript into beats, then builds a scene file and checks stills and a preview. The final render comes after approval. For a video about a company, the brand-kit skill runs first and supplies that brand’s colours, fonts, and shapes.

Setup needs npm i in ~/simcraft, the Python environment from sh ~/simcraft/skills/video/rough-cut/setup.sh, and ffmpeg. A voiceover is required for scene timing; a narration file can be used instead of a recorded take. The audio is transcribed unless existing word timings are passed with --words.

What it helps with

  • turn a voiceover into a faceless explainer video
  • sync quote and statistic animations to spoken words
  • split narration into visual beats
  • check frames and motion before the final render

Example prompts for the agent

  • Make a Vox-style explainer video from this voiceover.
  • Animate these quotes and stats to the words in the narration.
  • Turn this script and voice track into an explainer with one visual beat per idea.

How to install vox-explainer

1Skills CLI (Vercel)

npx skills add dotslashsimran/simcraft --skill vox-explainer -a claude-code

2Manually: put the files in place

~/.claude/skills/vox-explainer/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/vox-explainer/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about vox-explainer

How do I install vox-explainer in Claude Code?

Run npx skills add dotslashsimran/simcraft --skill vox-explainer -a claude-code. The skill file will be at ~/.claude/skills/vox-explainer/SKILL.md.

What does vox-explainer do?

It creates explainer graphics or a faceless video, timing frames and highlights to the voiceover. Stills and a preview are checked before the final render.

What does vox-explainer need to run?

It needs npm, the Python environment set up by rough-cut, ffmpeg, and a voiceover. Videos about a company also require running brand-kit first.

Source text

SKILL.md · MIT
---
name: vox-explainer
description: Make Vox-style explainer graphics or a full faceless explainer video, in the user's chosen "style C" (navy and red colour blocks, torn cream paper cards, condensed uppercase headlines, serif quotes, yellow highlighter, black mono label strips, light grain). Every beat, highlight and list item is timed to the exact word in the voiceover. Use when asked for a Vox-style video, explainer graphics, animated quotes or stats over a voiceover, or "make this look like Vox".
---

# Vox explainer

Setup, once: `cd ~/simcraft && npm i`. It also needs rough-cut's Python env (`sh ~/simcraft/skills/video/rough-cut/setup.sh`) for word timings, and ffmpeg.

## Steps

0. **Brand first.** If the video is for, with or about a company (a sponsor, a client, "a Devin video"), run the **brand-kit** skill for that company before anything else, show the user its board, then put `"brand": "<slug>"` in the scene. Everything switches to their colours, fonts and shapes. Build without a brand only for the user's own videos, which use style C.
1. **Voice first.** Get the voiceover before designing anything. It can be her recorded take (run rough-cut and clean-audio on it first) or a narration file. The picture is timed to the voice, never the other way round.
2. **Beat map.** Read the transcript and write one beat per idea, about 2.5–3.5 s each. For each beat, name its point in one clause. If you can't, the beat is filler. Show the beat list to the user before building.
3. **Write the scene file** (format below), next to the voiceover.
4. **Check layouts with stills** at a few seconds, and look at them:
   `python3 scripts/build.py scene.json --stills 2,6.5,11`
5. **Preview** (half size, fast). It ends with a motion check that fails if anything sits still for 0.5 s or more:
   `python3 scripts/build.py scene.json --preview`
6. After the user approves, render the **final** at full size: `python3 scripts/build.py scene.json`

Add `--words <file>` to reuse word timings you already have, such as rough-cut's `audio/words.json` or verify's `cuts/verify_vN_words.json` for a cut. Otherwise the voiceover is transcribed.

## Scene file

```json
{ "audio": "vo.mp4", "format": "16:9",
  "beats": [
    {"at": "Did", "device": "big", "bg": "red", "text": "$0", "sub": "What startups spent on SOC 2", "submark": "SOC 2", "submark_at": "SOC2"},
    {"at": "today", "device": "photo", "url": "https://example.com", "caption": "example.com, today",
     "tags": [{"text": "Same product", "at": "selling", "yellow": true, "x": 62, "y": 78}]},
    {"at": "Then", "device": "card", "label": "Their security team", "quote": true, "text": "Where's the SOC 2 report?", "mark": "SOC 2 report", "mark_at": "SOC"}
  ] }
```

- `at` is the word (or a few words) in the voiceover where the beat starts. Each beat searches after the previous one. A number means seconds.
- `mark`, `headmark` and `submark` are the phrase to highlight. It sweeps in when its first word is spoken; use `*_at` if the transcript spells it differently ("SOC2"). **Only one highlight per beat.**
- `brand` is a brand-kit slug (or folder). Leave it out for style C.
- `bg` is `a`, `b`, `paper` or `accent` (`navy`/`red` still work for style C). Alternate them. The diagonal split changes on its own each beat. Use `"flat": true` for a single colour.
- `format` is `16:9` or `9:16`. `"twos": false` turns off the 12 fps stepped motion.
- `tags` are black mono label strips (`yellow: true` for the accent). `x` and `y` are in % of the frame, and `at` is the word that brings the tag in.

| Device | Use for | Fields |
|---|---|---|
| `big` | One huge statement or number | `text`, `sub`, `mark`/`submark` |
| `card` | Torn paper card: a quote, a question, a claim | `label`, `head`, `text`, `quote`, `mark`/`headmark`, `width`, `tilt` |
| `stat` | A number counting up | `value`, `prefix`, `suffix`, `sub` |
| `photo` | Real evidence: a screenshot, document or photo, pinned like a print with a slow push-in | `img` or `url` (captured automatically), `caption`, `width`, `ratio`, `tilt` |
| `cutout` | An object dropped onto the colour blocks | `img` (transparent PNG; make one with the image-gen skill using `--cutout`), `size`, `x`, `tilt` |
| `list` | Numbered points, each landing on its word | `items`, `items_at`, `label` |
| `chart` | A line that draws itself | `points`, `label`, `end_label`, `draw_ms` |

## Rules (her taste plus the research)

With a brand kit, the brand's colours, fonts and edges replace style C's. The rules below about pace, pictures, evidence and motion still apply.

- **One idea per frame. Huge type.** Strict palette: navy #1E2B3A, red #C7302B, cream #F2EAD8, ink, yellow #F5C518. No purple, no cute illustrations, no old-Mac frames.
- **Mix in pictures.** All-text reads as a slideshow, and she has called that out before. Use a `photo` with a real screenshot or document every few beats. For things that can't be screenshotted, make cut-outs with image-gen. Generated images never contain text; all type is set in code.
- **Real evidence must be real.** Never present a generated image as a document, a screenshot or a quote.
- **Nothing freezes.** Every beat slowly pushes in, and the motion check enforces it.
- No whooshes. If sound effects are added, use only small paper or UI sounds.

Research, design reasoning and what each choice fixes: [reference.md](reference.md).

© dotslashsimran · MIT · dotslashsimran/simcraft

Similar skills

SKILL.md skills catalog →

vox-explainer by other authors comes first.

vox-explainer charlie947 vox-explainer is a Claude Code skill that turns a sourced script into a short documentary-style video with code-made motion graphics, built in HTML and exported as MP4. CX Codex +1 3,800installs vox-explainer heygen-com vox-explainer builds collage-style 60 to 90 second HyperFrames explainer videos from a topic or supplied documents. CX Codex +1 772installs vox-video-director modelstudioai vox-video-director is a Claude Code skill that turns a single topic into a finished Vox-style video with collage animation, narration, music and captions. CX Codex +1 161installs vox-director Alisa0808 The vox-director skill turns a single topic into a finished paper-collage explainer or ad: script, poster keyframes, motion, voice-over, music and captions. It runs on the Atlas Cloud API plus local ffmpeg. CX Codex +1 ★ 3,014repo stars higgsfield-video-explainer higgsfield-ai The higgsfield-video-explainer Claude Code skill routes the legacy video-explainer workflow to Higgsfield’s illustrated process. It activates when explicitly invoked or when continuing that existing workflow. CX Codex +1 162,100installs plannotator-visual-explainer backnotprop plannotator-visual-explainer is a Claude Code skill that creates HTML visualizations of plans, PR explainers, architecture diagrams, and slide decks in Plannotator's dark theme. CX Codex +1 15,100installs papercraft-stop-motion-explainer MiniMax-AI This skill turns a topic into a production plan for a papercraft stop-motion explainer: characters, sets, prompts and a storyboard. CX Codex +1 3,700installs paper-collage-explainer-generator MiniMax-AI paper-collage-explainer-generator is a skill that turns text, ideas, or story beats into stop-motion paper-collage animations with visual metaphors and video clips. CX Codex +1 3,600installs

From the same set24

The whole set →
skill-router The skill-router Claude Code skill selects a matching skill or builds a sequence for a task. It kicks in when a request is vague or could call for several skills. CX Codex +1 ★ 541repo stars bisect-anything The bisect-anything Claude Code skill tracks a regression to a commit, dependency version, or config value. It activates for requests to find what broke a test or when a problem began. CX Codex +1 ★ 541repo stars scripted-screencast The scripted-screencast Claude Code skill turns scripted browser actions into a product demo video with cursor effects, zooms, and captions. It activates for screencast requests and rerenders after interface changes. CX Codex +1 ★ 541repo stars security-threat-model The security-threat-model Claude Code skill maps threats from an app’s code and tests the highest risks locally. It activates for requests about STRIDE, app security reviews, or vulnerabilities before launch. CX Codex +1 ★ 541repo stars benchmark-honestly The benchmark-honestly Claude Code skill checks performance measurements and compares code versions. It activates for benchmark requests, load tests, latency percentiles, or claims that a change made code faster. CX Codex +1 ★ 541repo stars flaky-test-killer The flaky-test-killer Claude Code skill tracks down flaky-test causes and helps fix them at the root. It stresses the test and compares failure rates before and after the change. CX Codex +1 ★ 541repo stars reverse-engineer-video The reverse-engineer-video Claude Code skill breaks down a reference clip into shots, camera moves and editing beats. Invoke it to inspect a cut, plan a remake or compare one with the original. CX Codex +1 ★ 541repo stars system-design-from-scratch system-design-from-scratch — a skill for Claude Code that builds minimal distributed architectures, verifies invariants under simulated node failures, and stress-tests them with real metrics. CX Codex +1 ★ 541repo stars

Project sponsors

Companies that keep this analytics open