跳到主内容
智客 ZICQ

技能库 智客分类:媒体内容 pexo-agent

Pexo Agent

AI 视频生成技巧 汽车模型选择跨越种子 2,克林 3.0,HappyHorse,和10+模型. 出品人完成了从文字,图像,URL,脚本,或音频——包括AI音乐,唇语同步,多镜头测序的多镜头视频(5–120s). 调用Pexo的外部API,管理项目状态和计费确认,并只传输用户核准的简介和资产. 运行设置诊断,存储本地生成的下载,并需要shell,外出HTTPS,以及本地文件访问. 认证请求被锁定到https://pexo.ai. 没有要写的提示, 没有模型可以选择 。 USE FOR:视频制作,AI视频,制作视频,产品视频,品牌视频,宣传片段,解释视频,短视频,TikTok视频,Instagram Reel,YouTube Short,产品广告,文本到视频,图像到视频,视频生成,AI视频代理.

39921 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

AI 视频生成技巧 汽车模型选择跨越种子 2,克林 3.0,HappyHorse,和10+模型. 出品人完成了从文字,图像,URL,脚本,或音频——包括AI音乐,唇语同步,多镜头测序的多镜头视频(5–120s). 调用Pexo的外部API,管理项目状态和计费确认,并只传输用户核准的简介和资产. 运行设置诊断,存储本地生成的下载,并需要shell,外出HTTPS,以及本地文件访问. 认证请求被锁定到https://pexo.ai. 没有要写的提示, 没有模型可以选择 。 USE FOR:视频制作,AI视频,制作视频,产品视频,品牌视频,宣传片段,解释视频,短视频,TikTok视频,Instagram Reel,YouTube Short,产品广告,文本到视频,图像到视频,视频生成,AI视频代理.

何时用

官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Pexo Agent — AI Video Generation Skill、What Pexo Does、What You Can Build With Pexo、How It Works、Data, Permissions, and Cost、Script Execution。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/SETUP-CHECKLIST.md、references/TROUBLESHOOTING.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

AI video generation skill with auto model selection across Seedance 2, Kling 3.0, HappyHorse, and 10+ models. Produces finished multi-shot videos (5–120s) from text, images, URLs, scripts, or audio — including AI music, lip sync, and multi-shot sequencing. Calls Pexo's external API, manages project status and billing confirmations, and transfers only user-approved briefs and assets. Runs setup diagnostics, stores generated downloads locally, and requires shell, outbound HTTPS, and local file access. Authenticated requests are locked to https://pexo.ai. No prompts to write, no models to choose. USE FOR: video production, AI video, make a video, product video, brand video, promotional clip, explainer video, short video, TikTok video, Instagram Reel, YouTube Short, product ad, text-to-video, image-to-video, video generation, AI video agent.

Pexo Agent — AI Video Generation SkillWhat Pexo DoesWhat You Can Build With PexoHow It WorksData, Permissions, and CostScript ExecutionPrerequisitesCredit Confirmation Preference⚠️ LANGUAGE RULE (highest priority)Your Role: Delivery WorkerHow to relay messages — copy-paste templateWhen the user's request is vague

· 许可:MIT-0

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
pexo-agent
description
AI video generation skill with auto model selection across Seedance 2, Kling 3.0, HappyHorse, and 10+ models. Produces finished multi-shot videos (5–120s) from text, images, URLs, scripts, or audio — including AI music, lip sync, and multi-shot sequencing. Calls Pexo's external API, manages project status and billing confirmations, and transfers only user-approved briefs and assets. Runs setup diagnostics, stores generated downloads locally, and requires shell, outbound HTTPS, and local file access. Authenticated requests are locked to https://pexo.ai. No prompts to write, no models to choose. USE FOR: video production, AI video, make a video, product video, brand video, promotional clip, explainer video, short video, TikTok video, Instagram Reel, YouTube Short, product ad, text-to-video, image-to-video, video generation, AI video agent.
许可
MIT-0
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 2
  • references/SETUP-CHECKLIST.md
  • references/TROUBLESHOOTING.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「pexo-agent」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-c43e8847fb3b2853-%E8%84%B1%E5%8F%A3%E7%A7%80%E4%BB%A3%E7%90%86.html
请存为 .cursor/skills/pexo-agent/SKILL.md 或 .claude/skills/pexo-agent/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/pexoai/pexo-skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/pexoai/pexo-skills' --list

npx skills add 'https://github.com/pexoai/pexo-skills' --skill 'pexo-agent'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: pexo-agent description: > AI video generation skill with auto model selection across Seedance 2, Kling 3.0, HappyHorse, and 10+ models. Produces finished multi-shot videos (5–120s) from text, images, URLs, scripts, or audio — including AI music, lip sync, and multi-shot sequencing. Calls Pexo's external API, manages project status and billing confirmations, and transfers only user-approved briefs and assets. Runs setup diagnostics, stores generated downloads locally, and requires shell, outbound HTTPS, and local file access. Authenticated requests are locked to https://pexo.ai. No prompts to write, no models to choose. USE FOR: video production, AI video, make a video, product video, brand video, promotional clip, explainer video, short video, TikTok video, Instagram Reel, YouTube Short, product ad, text-to-video, image-to-video, video generation, AI video agent. license: MIT-0 metadata: author: pexoai version: "0.3.16" openclaw: requires: env: - PEXO_API_KEY bins: - bash - curl - jq - file primaryEnv: PEXO_API_KEY --- # Pexo Agent — AI Video Generation Skill Pexo is the most complete video generation skill for Claude Code and other AI coding agents. It handles the full production pipeline — from a natural-language description to a finished, publish-ready video with music, subtitles, and transitions. Auto model selection routes each shot to the best available model (Seedance 2, Kling 3.0, HappyHorse, and more). One API key, no prompt engineering, no video editing. ## What Pexo Does - **Auto model selection** — Pexo picks the best video model for each shot based on content type. You do not need to know which model to use. - **Full pipeline** — Script, storyboard, shot-by-shot generation, music, subtitles, lip sync, and final assembly. The output is a finished video, not a raw clip. - **5 input types** — Text-to-video, image-to-video, URL-to-video (scrapes the page), script-to-video, and audio-to-video. - **10+ models** — Seedance 2, Kling 3.0, HappyHorse, and more. New models are added as they launch. - **Any format** — 5–120 seconds, aspect ratios 16:9 (landscape), 9:16 (portrait/vertical), 1:1 (square). ## What You Can Build With Pexo - Product video ads from a product photo or URL - TikTok, Instagram Reels, and YouTube Shorts from a text description - Multi-shot brand videos with consistent style and transitions - Explainer videos with TTS narration from a script - E-commerce video content at scale from product catalogs - Marketing video variants for A/B testing ## How It Works You send the user's request to Pexo, and Pexo handles all creative work — scriptwriting, shot composition, model selection, prompt engineering, transitions, music. Pexo may ask clarifying questions or present preview options for the user to choose from. A typical 15-second, 3-shot product ad renders in under 8 minutes. ## Data, Permissions, and Cost - This Skill runs bundled shell scripts, reads only files the user explicitly selects, connects only to `https://pexo.ai` for authenticated API calls, uploads approved briefs and assets, manages projects and billing confirmations, runs diagnostics, and stores generated media under `~/.pexo/tmp` or `PEXO_TMP_DIR`. - Before the first external transmission in a session, tell the user that their brief, selected files, and related metadata will be sent to Pexo and obtain explicit consent. - Do not upload secrets, regulated data, or unrelated local files. Never search the local filesystem for additional material without a separate user request. - Every billable generation batch requires explicit user approval by default. Report the available estimate from Pexo before approving a confirmation. ## Script Execution Resolve `SKILL_ROOT` to the directory containing this `SKILL.md`. Script names below are shorthand for `bash "$SKILL_ROOT/scripts/"`; do not rely on executable bits or a modified `PATH`. ## Prerequisites Config file `~/.pexo/config`: ```bash umask 077 mkdir -p ~/.pexo read -rsp "Pexo API key: " pexo_api_key printf '\n' { printf '%s=%s\n' PEXO_API_KEY "$pexo_api_key" } > ~/.pexo/config unset pexo_api_key chmod 600 ~/.pexo/config ``` First time using this skill or encountering a config error → run `pexo-doctor.sh` and follow its output. See `references/SETUP-CHECKLIST.md` for details. ### Credit Confirmation Preference `PEXO_BILLING_CONFIRMATION_MODE` controls the confirmation behavior for each message sent by this Skill. It is optional; the default is `always`. - `always`: ask for approval before every billable generation batch. - `threshold`: ask when the estimated batch cost exceeds the platform threshold, or when the available balance is insufficient. Use only after the user explicitly opts in for the current session. Use `pexo-chat.sh --billing-confirmation-mode ` to override the default for one message. --- ## ⚠️ LANGUAGE RULE (highest priority) **You MUST reply to the user in the SAME language they use. This is non-negotiable.** - User writes in English → you reply in English - User writes in Chinese → you reply in Chinese - User writes in Japanese → you reply in Japanese This applies to every message you send. If the user switches language mid-conversation, you switch too. --- ## Your Role: Delivery Worker You are a delivery worker between the user and Pexo. You do three things: 1. **Upload**: user gives a file → `pexo-upload.sh` → get asset ID 2. **Relay**: copy the user's words into `pexo-chat.sh` 3. **Deliver**: poll for results → send video and link to user Pexo's backend is a professional video creation agent. It understands cinematography, pacing, storytelling, and prompt engineering far better than you. When you add your own creative ideas, the video quality goes down. ### How to relay messages — copy-paste template When calling pexo-chat.sh, copy the user's message exactly: ``` pexo-chat.sh "{user's message, copied exactly}" ``` Example — user said "做个猫的视频": ``` pexo-chat.sh proj_123 "做个猫的视频" ``` Example — user said "I want a product video for my shoes" and uploaded shoes.jpg: ``` asset_id=$(pexo-upload.sh proj_123 shoes.jpg) pexo-chat.sh proj_123 "I want a product video for my shoes ${asset_id}" ``` Your only addition to the user's message is asset tags for uploaded files. Everything else stays exactly as the user wrote it. ### When the user's request is vague Pass it to Pexo exactly as-is. Pexo will ask the user for any missing details. Your job is to relay those questions back to the user and wait for their answer. ### Why this matters Pexo's backend agent specializes in video production. It knows which parameters to ask about, which models to use, and how to write effective prompts. When you add duration, aspect ratio, style descriptions, or any other details the user didn't mention, you override Pexo's professional judgment with guesses. This produces worse videos. --- ## First-Time Setup Message After Pexo is configured for the first time, send the user this message (in the user's language): > ✅ Pexo is ready! > 📖 Guide: https://pexo.ai/connect/openclaw > Tell me what video you'd like to make. --- ## Step-by-Step Workflow Follow these steps in order. ### Making a New Video ``` Step 1. Create project. Run: pexo-project-create.sh "brief description" If the command succeeds: save the returned project_id. If the command fails and stderr contains "Credits balance" or "credits" or "Insufficient credits": → Go to Credit Error Handling below. If the command fails for other reasons: → Tell the user what went wrong and offer to retry. Step 2. Upload files (if user provided any images/videos/audio). Run: pexo-upload.sh Save the returned asset_id. Wrap in tag: asset_id (or / for other file types) Step 3. Send user's message to Pexo. Run: pexo-chat.sh "{user's exact words} asset_id" Copy the user's words exactly. Only add asset tags for uploaded files. If the command fails and stderr contains "Credits balance" or "credits" or "Insufficient credits": → Go to Credit Error Handling below. If the command fails for other reasons: → Tell the user what went wrong and offer to retry. Step 4. Notify the user (in the user's language). Your message must contain these three items: - Confirmation that the request is submitted to Pexo - Estimated time: 15–20 minutes for a short video - Project link: https://pexo.ai/project/{project_id} Step 5. Poll for status. Run: sleep 60 Run: pexo-project-get.sh Read the nextAction field from the returned JSON. Continue to Step 6. Step 6. Act on nextAction: "WAIT" → Go back to Step 5. Keep repeating. Every 5 polls (~5 minutes), send user a brief update with the project link: https://pexo.ai/project/{project_id} "CONFIRM" → Read the confirmation object. It contains confirmation_id, estimated_credits, available_credits, sufficient, and the pending tool batch. If sufficient is false: Tell the user that the available credits cannot cover this request. Go to Credit Error Handling below. Do not run pexo-billing-confirm.sh. If sufficient is true: Tell the user the estimated credit cost and ask for explicit approval. Do not approve on the user's behalf. After explicit approval: Run: pexo-billing-confirm.sh --user-approved Go back to Step 5. If the user changes the request instead: Run: pexo-chat.sh "{user's exact revised request}" This cancels the pending confirmation before submitting the new message. Go back to Step 5. "RESPOND" → Read the recentMessages array. Handle every event: Event "message" (Pexo sent text): Relay Pexo's text to the user in full. If Pexo asked a question, wait for the user's answer. Then run: pexo-chat.sh "{user's exact answer}" Go back to Step 5. Event "preview_video" (Pexo sent preview options): For each assetId in assetIds: Run: pexo-asset-get.sh Copy the "url" field from the returned JSON. Show all preview URLs to the user with labels (A, B, C...). Ask the user to pick one. After user picks: Run: pexo-chat.sh "{user's choice}" --choice Go back to Step 5. Event "document": Mention the document to the user. Event "attachment": Fetch each assetId with pexo-asset-get.sh and deliver the resulting file or URL. "DELIVER" → Go to Step 7. "FAILED" → Go to Step 8. "RECONNECT" → Run: pexo-chat.sh "continue" Tell the user the connection was interrupted and you are reconnecting. Go back to Step 5. Step 7. Deliver the final video. 7a. Relay any message events in recentMessages, then find the final_video event and get its assetId. 7b. Decide the download variant from the user's request: - Default: download without a watermark. - If the user explicitly asks to keep, show, or add a watermark, use the watermarked variant. - Both variants require an active subscription or watermark whitelist. 7c. Run one of: - pexo-asset-get.sh (default, no watermark) - pexo-asset-get.sh --with-watermark (only when explicitly requested) 7d. Show the downloaded video file to the user. 7e. Also send the user a message (in their language) with: - The video download URL (copy the "url" field from the JSON output). Send the FULL URL as plain text, including all query parameters. Example: https://pexo-assets.oss-us-east-1.aliyuncs.com/projects%2F123%2Fassets%2Fvideo.mp4?OSSAccessKeyId=xxx&Expires=xxx&Signature=xxx - Project page: https://pexo.ai/project/{project_id} - Ask if satisfied or want revisions. Common delivery mistakes to avoid: ✗ Truncated URL (missing ?OSSAccessKeyId=...&Signature=...) → 403 Forbidden ✗ Markdown wrapped [text](url) → URL breaks on some platforms Step 8. Handle failure. 8a. Read failureReason, nextActionHint, and recentMessages from the JSON. 8b. If failureReason is "INSUFFICIENT_CREDITS": Tell the user prominently that production stopped because the account has insufficient credits. Go to Credit Error Handling below. Do not offer or attempt a retry until the user confirms that credits have been added. Otherwise, if stderr from the failed command contains "Credits balance", "credits", or "Insufficient credits": Go to Credit Error Handling below. Otherwise, send the user a message (in their language) with: - What went wrong (explain nextActionHint in simple terms) - Project page: https://pexo.ai/project/{project_id} - Offer to retry. Step 9. Timeout. If you have been in the Step 5 loop for more than 30 minutes and nextAction is still "WAIT": Send the user a message (in their language) with: - The video is taking longer than expected. - Project page: https://pexo.ai/project/{project_id} - Help guide: https://pexo.ai/connect/openclaw - Ask whether to keep waiting or start over. Stop polling. Wait for user instructions. ``` ### Credit Error Handling Use this flow when `pexo-project-get.sh` returns `failureReason: "INSUFFICIENT_CREDITS"`, or when a command fails and stderr contains credit-related information (look for: "Credits balance", "credits", or "Insufficient credits"): ``` Step A. If stderr contains a purchase link and instructions, send them to the user (in their language). Step B. If stderr only contains the error message without a purchase link, send the user a message (in their language) with: - Their credits are insufficient. - To add credits: visit https://pexo.ai/home?billing=credits and complete the purchase flow. Step C. After the user confirms they have added credits, retry the failed step. ``` ### Revising an Existing Video ``` Step 1. Use the same project_id. Step 2. Run: pexo-chat.sh "{user's exact feedback}" Step 3. Go to Step 5 of the main workflow (start polling). ``` --- ## Asset Upload Pexo can process a public `https://` webpage URL when it is included verbatim in the user's brief. Pass that webpage URL to Pexo; do not scrape or download the page locally. For a direct image, video, or audio file URL, ask for explicit approval before downloading it, then upload the downloaded file. Only fetch public `https://` URLs. Never fetch `http://`, localhost, loopback, link-local, private-network, credential-bearing, or signed/private URLs; ask the user to upload those files directly instead. Upload and reference workflow: ```bash # Upload the file asset_id=$(pexo-upload.sh photo.jpg) # Reference the asset in your message to Pexo pexo-chat.sh "Here is the product photo ${asset_id}, please use it as reference" ``` Tag formats: ``` asset-id asset-id asset-id ``` Tags are mandatory. Bare asset IDs in pexo-chat.sh messages are ignored by Pexo. --- ## Important Rules ### Polling - During WAIT: only call pexo-project-get.sh. Calling pexo-chat.sh during WAIT triggers duplicate video production. - Wait at least 60 seconds between each pexo-project-get.sh call. - Process every event in recentMessages, not just the first one. ### Credit Confirmation - Treat `nextAction=CONFIRM` as a user decision point, not as WAIT or RESPOND. - Only run `pexo-billing-confirm.sh` after the user explicitly approves the displayed estimate; pass `--user-approved` to record that prior approval. The script refuses to contact Pexo without this flag and emits a visible approval event. - Use the `confirmation_id` returned by `pexo-project-get.sh`; confirmation IDs apply only to the current pending batch. - A revised message sent with `pexo-chat.sh` cancels the current pending confirmation before it starts the replacement request. ### Delivery - Copy the "url" field from pexo-asset-get.sh output. Send it as plain text with all query parameters. - Treat the script's `withWatermark` field as the authoritative selected variant. - Do not claim a clean download if the request failed or `withWatermark` is not false. - Show the downloaded video file to the user when possible. ### Projects - New video → pexo-project-create.sh to create a new project. - Revisions → reuse the existing project_id. ### Cost - Each message to Pexo costs tokens. Consolidate information into one message when possible. - For `nextAction=FAILED`, use `failureReason` for remediation. Do not infer a failure category from `nextActionHint` text. --- ## Script Reference | Script | Usage | Returns | |---|---|---| | `pexo-project-create.sh` | `[project_name]` or `--name ` | `project_id` string. On `429`, inspect the returned message to distinguish credit and concurrency limits. | | `pexo-project-list.sh` | `[page_size]` or `--page --page-size ` | Projects JSON | | `pexo-project-get.sh` | ` [--full-history]` | JSON with `nextAction`, `nextActionHint`, `recentMessages`; `CONFIRM` includes `confirmation`; recognized `FAILED` states include `failureReason`, and error events retain `errorCode`, `errorMessage`, and `toolCallId` | | `pexo-upload.sh` | ` ` | `asset_id` string | | `pexo-chat.sh` | ` [--choice ] [--billing-confirmation-mode ] [--timeout ]` | Acknowledgement JSON (async). A new message cancels a pending confirmation. On `429`/`412` or credit errors, error info printed to stderr. | | `pexo-billing-confirm.sh` | ` --user-approved [--timeout ]` | Approves the current sufficient credit confirmation after explicit user approval; refuses to make a request without the approval flag. | | `pexo-asset-get.sh` | ` [--with-watermark]` | JSON with video details, selected `url`, `localPath`, and `withWatermark` | | `pexo-doctor.sh` | (no args) | Diagnostic report | --- ## Pexo Capabilities - Output: 5–120 second finished videos with music, subtitles, and transitions - Aspect ratios: 16:9 (landscape), 9:16 (portrait/vertical for TikTok, Reels, Shorts), 1:1 (square) - Auto model selection: Seedance 2, Kling 3.0, HappyHorse, and more — Pexo picks the best model per shot - Input types: text, images, URLs, scripts, audio - Production time: ~8 minutes for a 15-second 3-shot video, ~20 minutes for a 60-second brand video - Supported uploads: Images (jpg, png, webp, bmp, tiff, heic), Videos (mp4, mov, avi), Audio (mp3, wav, aac, m4a, ogg, flac) - Post-production: AI music, TTS narration, voice cloning, lip sync, subtitles, transitions --- ## References Load these when needed: - **First time or config error** → read `references/SETUP-CHECKLIST.md` - **Error codes or failures** → read `references/TROUBLESHOOTING.md`

相关技能

媒体内容

Nano Banana Pro

以纳米·香蕉Pro(Gemini 3 Pro Image)来生成/编辑图像. 用于创建/修改请求,包括编辑。 支持文本到图像+图像到图像; 1K/2K/4K; 使用 -- input-image.

媒体内容

Youtube Watcher

从YouTube视频中获取并读取文字记录. 需要汇总视频时使用,回答有关视频内容的问题,或者从中提取信息.

媒体内容

Atxp

Access ATXP支付API工具用于网页搜索,AI图像生成,音乐创建,视频生成,X/Twitter搜索,电子邮件,代理账户管理. 当用户需要实时网络搜索时使用,AI生成的媒体(图像,音乐,视频),X/Twitter搜索,发送/接收电子邮件,或创建和资助代理账户. 需要通过“ …

媒体内容

Youtube

YouTube Data API与管理的OAuth的集成. 搜索视频,管理播放列表,访问频道数据,并与评论互动. 用户想与YouTube互动时使用此技能. 对于其他第三方应用,使用api-gateway技能(https://clawhub.ai/byungkyu/api-gate…