make-a-video · pexoai — Claude Code skill for making videos
The make-a-video Claude Code skill turns a written idea into a finished video through Pexo. It activates for requests to create a new video, not to edit an existing one.
MIT 117 installs ★ 835 updated 2026-08-20
npx skills add pexoai/pexo-skills --skill make-a-video -a claude-codeWhat make-a-video does
The skill sends the user's request to Pexo, a hosted service that handles the script, shot and model choices, music, subtitles, and editing. The agent opens a project, submits the request, tracks its progress, then returns the finished asset and project link.
It needs PEXO_API_KEY, PEXO_BASE_URL, and the curl, jq, and file utilities. Video generation uses Pexo credits, which can be purchased through the service. If the request includes files, the skill uploads them to the project; URLs must be downloaded first because Pexo cannot fetch them directly.
Revisions go to the existing project. The workflow also handles preview choices and can resume after a dropped connection.
What it helps with
- turn a written idea into a finished video
- upload user-provided files to a Pexo project
- retrieve the finished video and project link
- revise a video in its existing project
Example prompts for the agent
- Make a video about the launch of our coffee subscription.
- Create a short video from this idea: “How to choose a houseplant”.
- Use the attached images to make a video about our product.
How to install make-a-video
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill make-a-video -a claude-code2Manually: put the files in place
~/.claude/skills/make-a-video/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/make-a-video/
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill make-a-video -a codex2Manually: put the files in place
.agents/skills/make-a-video/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill make-a-video -a cursor2Manually: put the files in place
.cursor/skills/make-a-video/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pexoai/pexo-skills skills/make-a-video2Manually: put the files in place
.github/skills/make-a-video/SKILL.md1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill make-a-video -a gemini-cli2Platform CLI
gemini skills install https://github.com/pexoai/pexo-skills --path skills/make-a-videoManually: put the files in place
.devin/skills/make-a-video/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill make-a-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 make-a-video
How do I install make-a-video in Claude Code?
Run npx skills add pexoai/pexo-skills --skill make-a-video -a claude-code. The skill file is placed at ~/.claude/skills/make-a-video/SKILL.md.
What does make-a-video do?
It sends a new-video request to Pexo, which handles the script, visuals, music, subtitles, and edit. The skill is for creating videos, not editing existing footage.
What does make-a-video need to run?
Set PEXO_API_KEY and PEXO_BASE_URL, and install curl, jq, and file. Pexo video generation also uses credits.
Source text
SKILL.md · MIT
---
name: make-a-video
description: >
Make a complete video from a simple idea with Pexo. Describe what you want in plain words and
Pexo handles everything — script, shots, model selection, music, subtitles, and final editing —
and returns a publish-ready video. Use when the user just wants to make a video: "make a video",
"make me a video about X", "create a video", "I need a video for ...". NOT for editing a video
they already have.
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
---
# Make a Video — Pexo
**Pexo:** https://pexo.ai — get an API key, watch your project render, and buy credits there.
Make a finished video from a plain-language idea. You pass the user's request to the hosted Pexo
agent verbatim and deliver the result — Pexo does the script, shot selection, models, music, and
editing end to end.
## 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: "Make a 30-second video about our new coffee subscription."
```bash
pid=$(pexo-project-create.sh "coffee subscription promo")
pexo-chat.sh "$pid" "Make a 30-second video about our new coffee subscription."
# 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
SKILL.md skills catalog →make-a-video by other authors comes first.