startup-video — Claude Code skill: what it does, how to install
The startup-video Claude Code skill turns a startup brief or website into a branded video. It covers homepage intros, fundraising decks, and social posts.
MIT 114 installs ★ 835 updated 2026-08-20
npx skills add pexoai/pexo-skills --skill startup-video -a claude-codeWhat startup-video does
The skill sends a startup brief or website to Pexo, where the service writes the script, creates shots, selects models, and assembles a finished video with music. Files go through pexo-upload.sh; Pexo cannot crawl a URL, so a site must be downloaded before upload.
The flow creates a project, submits the request, checks progress with pexo-project-get.sh, and fetches the result through pexo-asset-get.sh. A preview_video event supports choosing A, B, or C, while revisions stay in the same project. The setup needs PEXO_API_KEY, PEXO_BASE_URL, curl, jq, and file; rendering also uses Pexo credits.
What it helps with
- create a startup intro video from a brief
- prepare a homepage brand video
- make a video for a fundraising deck
- upload source images or videos to a project
- revise an existing startup video
Example prompts for the agent
- Create an intro video for our startup from this company brief.
- Make a homepage video from
homepage-brief.txt. - Revise the current project with different music and a shorter cut.
How to install startup-video
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill startup-video -a claude-code2Manually: put the files in place
~/.claude/skills/startup-video/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/startup-video/
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill startup-video -a codex2Manually: put the files in place
.agents/skills/startup-video/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill startup-video -a cursor2Manually: put the files in place
.cursor/skills/startup-video/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pexoai/pexo-skills skills/startup-video2Manually: put the files in place
.github/skills/startup-video/SKILL.md1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill startup-video -a gemini-cli2Platform CLI
gemini skills install https://github.com/pexoai/pexo-skills --path skills/startup-videoManually: put the files in place
.devin/skills/startup-video/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill startup-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 startup-video
How do I install startup-video in Claude Code?
Run npx skills add pexoai/pexo-skills --skill startup-video -a claude-code, then check ~/.claude/skills/startup-video/SKILL.md.
What does startup-video do?
It sends a startup brief to Pexo. Pexo handles the script, shots, model selection, and music, then returns a finished video; later changes reuse the same project.
What does startup-video need to work?
It needs a Pexo account, PEXO_API_KEY, PEXO_BASE_URL, curl, jq, and file, plus Pexo credits. First-run setup uses ~/.pexo/config.
Source text
SKILL.md · MIT
---
name: startup-video
description: >
Make a video for your startup with Pexo. Describe your company, product, or vision (or paste your
site) and Pexo writes the script, generates the shots, picks the models, and returns a finished,
publish-ready startup video with music — for your homepage, fundraising deck, or social channels.
Use for startup brand and intro videos: "startup video", "video for my startup", "company intro
video", "about us video". NOT for paid 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
---
# Startup Video — Pexo
**Pexo:** https://pexo.ai — get an API key, watch your project render, and buy credits there.
Make a finished brand or intro video for your startup. You relay the founder's brief — or your
website — to the hosted Pexo agent and deliver the result; Pexo writes the script, generates the
shots, and assembles a polished startup 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 30-second intro video for our startup — a marketplace for local farmers."
```bash
pid=$(pexo-project-create.sh "startup intro video")
pexo-chat.sh "$pid" "Make a 30-second intro video for our startup — a marketplace for local farmers."
# 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