launch-video · pexoai — Claude Code skill: what it does, how to install
Skill for Claude Code that delegates startup launch video creation to the Pexo API. Generates finished promotional clips with music directly from a product pitch or asset files.
MIT 114 installs ★ 835 updated 2026-08-20
npx skills add pexoai/pexo-skills --skill launch-video -a claude-codeWhat launch-video does
The skill sends your verbatim prompt, screenshots, or local media to Pexo, which scripts scenes, generates visual shots, and mixes background audio. It acts strictly as a relay, leaving creative decisions to the backend agent.
Execution relies on local curl, jq, and file binaries, alongside valid credentials in ~/.pexo/config containing PEXO_API_KEY and PEXO_BASE_URL. Rendering consumes paid Pexo credits. Because the backend cannot crawl live URLs directly, web pages and demo shots must be downloaded locally before running the upload script.
Video processing takes around 15–20 minutes, tracked through a polling script every 60 seconds. Revisions reuse the existing project_id to preserve server context. If rendering exceeds 30 minutes, the agent pauses to ask whether to keep polling.
What it helps with
- produce a launch video with music for Product Hunt or landing pages
- generate a startup promo from a written pitch and interface screenshots
- submit revisions to an existing video without discarding project context
- upload local media assets directly to the Pexo rendering pipeline
Example prompts for the agent
- Make a 45-second launch video for our SaaS that writes meeting notes automatically
- Generate a product launch video using the screenshot in hero.png
- Update the video in our current project: change the background track and shorten the intro
How to install launch-video
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill launch-video -a claude-code2Manually: put the files in place
~/.claude/skills/launch-video/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/launch-video/
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill launch-video -a codex2Manually: put the files in place
.agents/skills/launch-video/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill launch-video -a cursor2Manually: put the files in place
.cursor/skills/launch-video/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pexoai/pexo-skills skills/launch-video2Manually: put the files in place
.github/skills/launch-video/SKILL.md1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill launch-video -a gemini-cli2Platform CLI
gemini skills install https://github.com/pexoai/pexo-skills --path skills/launch-videoManually: put the files in place
.devin/skills/launch-video/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill launch-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 launch-video
How do I install launch-video in Claude Code?
Run npx skills add pexoai/pexo-skills --skill launch-video -a claude-code. The skill file is placed in ~/.claude/skills/launch-video/SKILL.md.
What does launch-video do?
It registers a video task on Pexo, uploads reference media, monitors generation progress, and delivers a finished download link.
What is required to run launch-video?
You need curl, jq, file, an active account with credits on pexo.ai, and an API key stored in ~/.pexo/config.
Source text
SKILL.md · MIT
---
name: launch-video
description: >
Make a launch video for your startup or product with Pexo. Describe your product (or paste your
landing-page URL or a screenshot) and Pexo writes the script, generates every shot, picks the
models, and returns a finished, publish-ready launch video with music — built for Product Hunt,
your landing page, or launch-day socials. Use for product and startup launches: "launch video",
"product launch video", "make a launch video", "launch day video". NOT for ongoing ad campaigns
(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
---
# Launch Video — Pexo
**Pexo:** https://pexo.ai — get an API key, watch your project render, and buy credits there.
Make a finished launch video for a product or startup. You relay the founder's pitch — or a
landing-page URL or screenshot — to the hosted Pexo agent and deliver the result; Pexo writes the
script, generates the shots, and assembles a launch-ready video with music.
## 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 45-second launch video for our SaaS that writes meeting notes automatically."
```bash
pid=$(pexo-project-create.sh "SaaS launch video")
pexo-chat.sh "$pid" "Make a 45-second launch video for our SaaS that writes meeting notes automatically."
# 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 Marketing and content →launch-video by other authors comes first.