founder-video — Claude Code skill: what it does, how to install
founder-video — a skill for Claude Code that turns a founder’s story, product, or pitch into a video. It handles founder content for fundraising, Product Hunt, or a personal brand.
MIT 111 installs ★ 835 updated 2026-08-20
npx skills add pexoai/pexo-skills --skill founder-video -a claude-codeWhat founder-video does
The skill sends a founder’s story or pitch to Pexo, which writes a script, generates shots, and assembles a finished video with music. The request can describe the product or point to a website; Pexo cannot fetch URLs, so supplied files must be downloaded and uploaded to the project.
It creates a project, submits the request, tracks progress, and returns the finished video link. Runtime requirements are PEXO_API_KEY, PEXO_BASE_URL, curl, jq, and file. Video generation uses Pexo credits, which can be bought in the Credits section at https://pexo.ai/home. The skill is for founder content, not paid ad campaigns.
What it helps with
- turn a founder’s story into a product video
- prepare a founder pitch video for fundraising
- make a founder story video for Product Hunt
- create a video for a founder’s personal brand
Example prompts for the agent
- Make a video about the founder from this story: …
- Create a pitch video for Product Hunt from this product description: …
- Turn the text on this website into a founder video: …
How to install founder-video
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill founder-video -a claude-code2Manually: put the files in place
~/.claude/skills/founder-video/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/founder-video/
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill founder-video -a codex2Manually: put the files in place
.agents/skills/founder-video/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill founder-video -a cursor2Manually: put the files in place
.cursor/skills/founder-video/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pexoai/pexo-skills skills/founder-video2Manually: put the files in place
.github/skills/founder-video/SKILL.md1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill founder-video -a gemini-cli2Platform CLI
gemini skills install https://github.com/pexoai/pexo-skills --path skills/founder-videoManually: put the files in place
.devin/skills/founder-video/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill founder-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 founder-video
How do I install founder-video in Claude Code?
Run npx skills add pexoai/pexo-skills --skill founder-video -a claude-code. The skill file will be at ~/.claude/skills/founder-video/SKILL.md.
What does founder-video do?
It sends a founder’s story, product, or pitch to Pexo. Pexo creates the script and shots, assembles a video with music, and returns the finished asset.
What does founder-video need to run?
It requires PEXO_API_KEY, PEXO_BASE_URL, curl, jq, and file. Video generation also uses Pexo credits.
Source text
SKILL.md · MIT
---
name: founder-video
description: >
Make a founder video with Pexo — built for solo founders and small teams. Describe your story,
product, or pitch (or paste your site) and Pexo writes the script, generates the shots, picks the
models, and returns a finished, publish-ready founder video with music — for fundraising, Product
Hunt, or your personal brand. Use for founder content: "founder video", "solo founder video",
"founder pitch video", "founder story". 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
---
# Founder Video — Pexo
**Pexo:** https://pexo.ai — get an API key, watch your project render, and buy credits there.
Make a finished founder video — built for solo founders and small teams. You relay the founder's
story or pitch to the hosted Pexo agent and deliver the result; Pexo writes the script, generates
the shots, and assembles a personal, polished 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 founder pitch video for my solo SaaS that turns notes into flashcards."
```bash
pid=$(pexo-project-create.sh "founder pitch video")
pexo-chat.sh "$pid" "Make a 30-second founder pitch video for my solo SaaS that turns notes into flashcards."
# 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