Skip to main content
skill CX Codex

saas-video — Claude Code skill: SaaS videos and installation

The saas-video Claude Code skill sends SaaS product details to Pexo to produce a demo or explainer video. Give the agent a description, app URL, or screenshot; Pexo creates the visuals and adds narration and captions.

MIT 116 installs ★ 835 updated 2026-08-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add pexoai/pexo-skills --skill saas-video -a claude-code
Open on GitHub

What saas-video does

The skill submits a SaaS video request to Pexo and retrieves the finished result. Pexo writes the script, generates visuals, then adds narration and captions. It does not record a live screen session.

Scripts create a project, upload supplied files, send the request, and fetch the result while the agent checks the project's status. Pexo cannot fetch app pages from a URL, so download the page content before uploading it. The setup needs PEXO_API_KEY, PEXO_BASE_URL, curl, jq, and file; video generation runs through Pexo.

What it helps with

  • make a SaaS product demo video
  • create an explainer for an app landing page
  • turn app screenshots into video visuals
  • add narration and captions to a generated product video

Example prompts for the agent

  • Make a demo video for our SaaS product from this description: …
  • Create an explainer video for our app using this screenshot.
  • Make a product video from this app URL: …

How to install saas-video

1Skills CLI (Vercel)

npx skills add pexoai/pexo-skills --skill saas-video -a claude-code

2Manually: put the files in place

~/.claude/skills/saas-video/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/saas-video/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about saas-video

How do I install saas-video in Claude Code?

Run npx skills add pexoai/pexo-skills --skill saas-video -a claude-code. The skill file is at ~/.claude/skills/saas-video/SKILL.md.

What does saas-video do?

It sends a SaaS video request to Pexo, which writes the script, generates visuals, and adds narration and captions. The result is a finished video, not a live screen recording.

What does saas-video need to run?

Set PEXO_API_KEY and PEXO_BASE_URL, and have curl, jq, and file available. Pexo handles video generation; credits can be bought through the service.

Source text

SKILL.md · MIT
---
name: saas-video
description: >
  Make a SaaS demo or explainer video with Pexo. Describe your software (or paste your app URL or a
  screenshot) and Pexo writes the script, generates the visuals, picks the models, adds narration
  and captions, and returns a finished, publish-ready video — for your landing page, onboarding, or
  sales. Use for SaaS and software videos: "saas video", "saas demo video", "software demo", "app
  explainer video". NOT for live screen recording — Pexo generates the visuals.
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
---

# SaaS Video — Pexo

**Pexo:** https://pexo.ai — get an API key, watch your project render, and buy credits there.

Make a finished SaaS demo or explainer video. You relay a description of the software — or its URL
or a screenshot — to the hosted Pexo agent and deliver the result; Pexo writes the script,
generates the visuals, and adds narration and captions.

## 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 60-second demo video for our SaaS that automates expense reports."

```bash
pid=$(pexo-project-create.sh "SaaS demo video")
pexo-chat.sh "$pid" "Make a 60-second demo video for our SaaS that automates expense reports."
# 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 →

From the same set20

The whole set →
explainer-video Claude Code skill creates narrated explainer videos and tutorials via Pexo. Runs when requested to generate a product walkthrough or tutorial video. CX Codex +1 122installs video-ad Automates generating promotional video ads through the Pexo service using a product description or brief. CX Codex +1 120installs youtube-short-maker youtube-short-maker — a skill for Claude Code and Codex that dispatches video prompts to the hosted Pexo pipeline to produce 9:16 YouTube Shorts. Renders complete short-form clips with music and captions in 15–20 minutes. CX Codex +1 118installs make-a-video 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. CX Codex +1 117installs tiktok-video-ad tiktok-video-ad — a skill for Claude Code relays briefs to Pexo to create vertical 9:16 ads with native audio. Triggers on requests for TikTok video creative. CX Codex +1 117installs startup-video 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. CX Codex +1 114installs launch-video Delegates startup launch video creation to the Pexo API. Generates finished promotional clips with music directly from a product pitch or asset files. CX Codex +1 114installs founder-video 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. CX Codex +1 111installs

Project sponsors

Companies that keep this analytics open