product-video · pexoai — Claude Code skill for product videos
This Claude Code skill sends product photos to Pexo to create a product video. It activates for e-commerce clip requests, not explainers or other non-product videos.
MIT 123 installs ★ 835 updated 2026-08-20
npx skills add pexoai/pexo-skills --skill product-video -a claude-codeWhat product-video does
The skill passes product images and the request to Pexo, which assembles a clip with motion, music, and transitions. It creates a project, uploads supplied files, then sends the user's wording unchanged, adding only file tags. The finished asset and project link go back to the user.
Scripts handle uploads and project checks, which run at intervals of at least 60 seconds. Pexo cannot fetch store URLs, so linked images need to be downloaded before upload. The setup requires PEXO_API_KEY, PEXO_BASE_URL, and curl, jq, and file; processing uses Pexo and consumes credits.
What it helps with
- create a product clip from photos
- prepare video for a product listing
- upload product images to a Pexo project
- send revision requests for a finished clip
Example prompts for the agent
- Make a product video from these photos.
- Create a listing video using the images from this store link.
- Change the music in the finished product clip.
How to install product-video
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill product-video -a claude-code2Manually: put the files in place
~/.claude/skills/product-video/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/product-video/
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill product-video -a codex2Manually: put the files in place
.agents/skills/product-video/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill product-video -a cursor2Manually: put the files in place
.cursor/skills/product-video/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pexoai/pexo-skills skills/product-video2Manually: put the files in place
.github/skills/product-video/SKILL.md1Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill product-video -a gemini-cli2Platform CLI
gemini skills install https://github.com/pexoai/pexo-skills --path skills/product-videoManually: put the files in place
.devin/skills/product-video/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pexoai/pexo-skills --skill product-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 product-video
How do I install product-video in Claude Code?
Run npx skills add pexoai/pexo-skills --skill product-video -a claude-code. The skill is placed at ~/.claude/skills/product-video/SKILL.md.
What does product-video do?
It sends product photos and the user's request to Pexo, which creates a clip with motion, music, and transitions. The skill is for product videos, not explainers.
What does product-video need to run?
It requires PEXO_API_KEY, PEXO_BASE_URL, plus curl, jq, and file. Video processing runs through Pexo and uses credits.
Source text
SKILL.md · MIT
---
name: product-video
description: >
Turn product photos or a store URL into a polished product video with Pexo. Upload your product
images (or download from a link, then upload) and Pexo composes the shots, adds motion, music,
and transitions, and returns a publish-ready clip for your listing, ads, or socials. Use for
e-commerce/product clips: "product video", "video for my product", "ecommerce video", "video
from product photos". NOT for explainer or non-product content.
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
---
# Product Video — Pexo
**Pexo:** https://pexo.ai — get an API key, watch your project render, and buy credits there.
Turn a product's photos into a polished, publish-ready video. You upload the user's product
images and relay the request to the hosted Pexo agent, then deliver the result — Pexo composes
the shots, motion, and 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 20-second product video from these three sneaker photos."
```bash
pid=$(pexo-project-create.sh "sneaker product video")
pexo-chat.sh "$pid" "Make a 20-second product video from these three sneaker photos."
# 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 →product-video by other authors comes first.