saas-video
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.
- License 许可
- MIT
- 最近更新
- 2026-08-19
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- metadata
- { "author": "pexoai" }
- 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.
02 资源文件 12
- 参考文档README.md1.1 KB
- 参考文档references/SETUP-CHECKLIST.md2.4 KB
- 参考文档references/TROUBLESHOOTING.md12.0 KB
- 脚本scripts/_common.sh11.2 KB
- 脚本scripts/pexo-asset-get.sh2.3 KB
- 脚本scripts/pexo-chat.sh4.5 KB
- 脚本scripts/pexo-doctor.sh5.4 KB
- 脚本scripts/pexo-entitlements.sh1.6 KB
- 脚本scripts/pexo-project-create.sh1.8 KB
- 脚本scripts/pexo-project-get.sh6.9 KB
- 脚本scripts/pexo-project-list.sh1.6 KB
- 脚本scripts/pexo-upload.sh3.1 KB
03 SKILL.md 正文
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.
- Create a project:
pexo-project-create.sh "<short brief>"→ save theproject_id. - Upload any files the user gave:
pexo-upload.sh <project_id> <path>→ saveasset_id, reference it inline as<original-image>asset_id</original-image>(or<original-video>/<original-audio>). Tags are required — a bareasset_idis ignored. Pexo can't crawl URLs — download, then upload. - Send the request:
pexo-chat.sh <project_id> "<user's exact words> <asset tags>". Copy the user's words exactly; only add asset tags. - Tell the user (their language): submitted ✓ · ~15–20 min ·
https://pexo.ai/project/<project_id>. - Poll: every ≥60s run
pexo-project-get.sh <project_id>and act onnextAction:- 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, thenpexo-chat.shtheir reply); forpreview_video, runpexo-asset-get.sh <project_id> <assetId>per option, show the URLs (A/B/C), let the user pick, thenpexo-chat.sh <project_id> "<choice>" --choice <assetId>; for adocumentevent, 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
nextActionHintin 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.shduring 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."
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.
04 同仓库更多 Skills
youtube-transcript
Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com/watch?v=, youtu.be/, or similar). Supports output with or without timestamps.
youtube-thumbnail-design
YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A/B testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image
youtube-short-maker
Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: "youtube short", "make a youtube short", "shorts video", "short-form video". NOT for long-form or landscape video.
xcode-project-setup
Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or "build it in" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.
x-twitter-scraper
Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.