explainer-video · pexoai — Claude Code skill: what it does, how to install
Claude Code skill creates narrated explainer videos and tutorials via Pexo. Runs when requested to generate a product walkthrough or tutorial video.
MIT 122 installs ★ 835 updated 2026-08-20
npx skills add pexoai/pexo-skills --skill explainer-video -a claude-codeWhat explainer-video does
The skill writes scripts, generates visuals shot by shot, adds text-to-speech voiceovers, and assembles captions. It requires PEXO_API_KEY, PEXO_BASE_URL in ~/.pexo/config, plus curl, jq, and file runtimes. Without credit balance on the account, video rendering fails.
The agent initializes projects via pexo-project-create.sh, uploads assets, and polls status every 60 seconds. Revisions reuse the existing project ID to preserve server-side context.
What it helps with
- generate an explainer video from text prompt
- add voiceover and captions to visual content
- upload files to a Pexo project via CLI
- tweak a rendered video using feedback
Example prompts for the agent
- Explain how our app works in a 60-second video
- Create a tutorial video for this process
- Make the video shorter and change the music
How to install explainer-video
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill explainer-video -a claude-code2Manually: put the files in place
~/.claude/skills/explainer-video/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/explainer-video/
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill explainer-video -a codex2Manually: put the files in place
.agents/skills/explainer-video/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill explainer-video -a cursor2Manually: put the files in place
.cursor/skills/explainer-video/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pexoai/pexo-skills skills/explainer-video2Manually: put the files in place
.github/skills/explainer-video/SKILL.md1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill explainer-video -a gemini-cli2Platform CLI
gemini skills install https://github.com/pexoai/pexo-skills --path skills/explainer-videoManually: put the files in place
.devin/skills/explainer-video/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill explainer-video -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about explainer-video
How to install explainer-video in Claude Code?
Run npx skills add pexoai/pexo-skills --skill explainer-video -a claude-code, then refer to ~/.claude/skills/explainer-video/SKILL.md.
What does explainer-video do?
It relays your topic to Pexo, which generates a script, shot-by-shot visuals, voiceover, and captions into a finished video.
What is needed to run explainer-video?
You need PEXO_API_KEY, PEXO_BASE_URL, and the curl, jq, and file utilities.
Source text
SKILL.md · MIT
---
name: explainer-video
description: >
Create an explainer video with narration using Pexo. Describe your product, concept, or process
and Pexo writes the script, generates visuals shot by shot, adds TTS voiceover and captions, and
assembles a clear, finished explainer. Use for explainer/tutorial content: "explainer video",
"explain this as a video", "tutorial video", "how it works video". NOT for ads or promos (use
the video-ad skill).
homepage: https://pexo.ai
repository: https://github.com/pexoai/pexo-skills
version: "0.1.0"
requires:
env: [PEXO_API_KEY, PEXO_BASE_URL]
runtime: [curl, jq, file]
metadata:
author: pexoai
---
# Explainer Video — Pexo
**Pexo:** https://pexo.ai — get an API key, watch your project render, and buy credits there.
Produce a clear, narrated explainer video. You relay the user's topic to the hosted Pexo agent
and deliver the result; Pexo writes the script, generates the visuals shot by shot, and adds
voiceover and captions.
## Your role: relay, don't create
Create a project, send the user's request **verbatim**, poll, deliver. Pexo's backend handles
all creative work — scriptwriting, model choice, prompts, music. Adding your own direction
(duration, style, models the user didn't ask for) overrides its judgment and produces worse
videos.
## Config
`~/.pexo/config`:
```
PEXO_BASE_URL="https://pexo.ai"
PEXO_API_KEY="sk-<your-api-key>"
```
**No account / first run →** read `references/SETUP-CHECKLIST.md` and walk the user through it — it carries the signup flow with the **invite code that grants new users bonus credits**, plus how to create the config above. **Config error →** run `scripts/pexo-doctor.sh` and follow its output.
## Workflow
Scripts live in this skill's `scripts/`. Reply to the user in their language.
1. **Create a project:** `pexo-project-create.sh "<short brief>"` → save the `project_id`.
2. **Upload any files** the user gave: `pexo-upload.sh <project_id> <path>` → save `asset_id`,
reference it inline as `<original-image>asset_id</original-image>` (or `<original-video>` /
`<original-audio>`). Tags are required — a bare `asset_id` is ignored. Pexo can't crawl URLs —
download, then upload.
3. **Send the request:** `pexo-chat.sh <project_id> "<user's exact words> <asset tags>"`.
Copy the user's words exactly; only add asset tags.
4. **Tell the user** (their language): submitted ✓ · ~15–20 min · `https://pexo.ai/project/<project_id>`.
5. **Poll:** every ≥60s run `pexo-project-get.sh <project_id>` and act on `nextAction`:
- **WAIT** → keep polling; every ~5 polls send a one-line update with the project link.
- **RESPOND** → handle each event in `recentMessages`: relay Pexo's text (wait for the
user's answer if it asked, then `pexo-chat.sh` their reply); for `preview_video`, run
`pexo-asset-get.sh <project_id> <assetId>` per option, show the URLs (A/B/C), let the user
pick, then `pexo-chat.sh <project_id> "<choice>" --choice <assetId>`; for a `document`
event, mention it to the user.
- **DELIVER** → `pexo-asset-get.sh <project_id> <final assetId>`, then send the user the
**full** asset URL as plain text — all `?…` query params, never truncated or wrapped in
markdown — plus the project link.
- **FAILED** → explain `nextActionHint` in plain terms and offer to retry.
- **RECONNECT** → `pexo-chat.sh <project_id> "continue"`, tell the user the connection
dropped and you're resuming, then keep polling.
- Never call `pexo-chat.sh` during WAIT — it triggers duplicate production.
- **Taking too long** → if it's been >30 min and still WAIT, tell the user (with the project
link + `https://pexo.ai/connect/openclaw`) it's running long; ask whether to keep waiting or
stop. Don't poll forever.
## Revisions
After delivery, the user's tweaks ("make it shorter", "new music", "different shot") reuse the
**same** project: `pexo-chat.sh <project_id> "<their feedback>"`, then poll again (step 5). Never
create a new project for a revision — it throws away Pexo's server-side context.
## Credits
If a script fails with "Credits balance" / "Insufficient credits": if the error carries a
purchase link, pass it to the user; otherwise tell them to add credits at `https://pexo.ai/home`
→ Credits → Buy Credits. Retry after they confirm.
## Example
User: "Explain how our budgeting app works in a 60-second video."
```bash
pid=$(pexo-project-create.sh "budgeting app explainer")
pexo-chat.sh "$pid" "Explain how our budgeting app works in a 60-second video."
# Tell the user: submitted, ~15–20 min, https://pexo.ai/project/$pid
# Poll pexo-project-get.sh "$pid" until nextAction is DELIVER, then deliver the asset URL.
```
## Scripts
| Script | Usage | Returns |
|---|---|---|
| `pexo-project-create.sh` | `"<brief>"` | `project_id` |
| `pexo-upload.sh` | `<project_id> <file>` | `asset_id` |
| `pexo-chat.sh` | `<project_id> "<message>" [--choice <id>]` | ack (async) |
| `pexo-project-get.sh` | `<project_id>` | JSON: `nextAction`, `recentMessages` |
| `pexo-asset-get.sh` | `<project_id> <asset_id>` | JSON with `url` |
| `pexo-doctor.sh` | — | setup diagnostic |
Error codes and edge cases → `references/TROUBLESHOOTING.md`.
© pexoai · MIT · pexoai/pexo-skills
Similar skills
All skills for AI and ML →explainer-video by other authors comes first.