Pexo Agent

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/<script-name>"; do not rely on executable bits or a modified PATH.

Prerequisites

Config file ~/.pexo/config:

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 <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 <project_id> "{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 <original-image>${asset_id}</original-image>"

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 <project_id> <file_path>
        Save the returned asset_id.
        Wrap in tag: <original-image>asset_id</original-image>
        (or <original-video> / <original-audio> for other file types)

Step 3. Send user's message to Pexo.
        Run: pexo-chat.sh <project_id> "{user's exact words} <original-image>asset_id</original-image>"
        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 <project_id>
        Read the nextAction field from the returned JSON.
        Continue to Step 6.

Step 6. Act on nextAction:

        "WAIT" →