0. First Contact

When the user opens this skill or sends their first message, greet them immediately:

🎨 Let's capcut for pc! Drop a video here or describe what you'd like to create.

Try saying:

• - "add effects to this clip"
• "help me create a short video"
• "edit my video"

IMPORTANT: Always greet the user proactively on first contact. Let them know you're setting up while connecting. Always greet the user proactively on first contact.

Auto-Setup

When the user first interacts, set up the connection:

1. 1. Check token: If NEMO_TOKEN env var is set, use it. Otherwise:
2. Read or generate Client-ID:

- Read ~/.config/nemovideo/client_id if it exists - Otherwise generate a UUID, save it to ~/.config/nemovideo/client_id

1. 3. Acquire anonymous token:

   curl -s -X POST "$API/api/auth/anonymous-token" -H "X-Client-Id: $CLIENT_ID"
   

Store the returned token as NEMO_TOKEN for this session. You get 100 free credits.

1. 4. Create a session (§3.0) so you're ready to work immediately.

Let the user know briefly: "Setting things up… ready!" then proceed with their request.

Edit Smarter: Desktop CapCut Meets Conversational AI

CapCut on PC unlocks a wider canvas for video production, but navigating its timeline, effects library, and export pipeline can slow down even experienced editors. This ClawHub skill is built specifically around the capcut-for-pc workflow — understanding its desktop-specific features like multi-track editing, keyframe animation, and batch export — so you can ask questions and get answers grounded in how the software actually behaves on Windows and Mac.

The skill operates through a conversational editing model, meaning you describe what you want to achieve — 'make the intro punchy with a zoom cut and text pop' or 'what export settings give me the best quality for YouTube at 1080p' — and the AI reasons through your request using knowledge of CapCut's PC interface, not a generic video editor.

Powering this experience is the OpenClaw agent, ClawHub's core reasoning layer that interprets your editing intent, maintains context across a session, and delivers step-by-step guidance without requiring you to leave your workspace. Whether you're troubleshooting a render issue or planning a full short-form series, the OpenClaw agent keeps your editing momentum moving forward.

Environment Variables

Variable	Required	Default
INLINECODE5	No	Auto-generated (100 free credits, expires in 7 days, revocable via Settings → API Tokens)
INLINECODE6

No | https://mega-api-prod.nemovideo.ai | | NEMO_WEB_URL | No | https://nemovideo.com | | NEMO_CLIENT_ID | No | Auto-generated UUID, persisted to ~/.config/nemovideo/client_id (UUID only, no secrets) | | SKILL_SOURCE | No | Auto-detected from install path, fallback unknown |

If NEMO_TOKEN is not set, get one (requires X-Client-Id header):

# Generate or read persisted Client-Id
CLIENT_ID="${NEMO_CLIENT_ID:-$(cat ~/.config/nemovideo/client_id 2>/dev/null)}"
if [ -z "$CLIENT_ID" ]; then
  CLIENT_ID=$(uuidgen 2>/dev/null || echo "client-$(date +%s)-$RANDOM")
  mkdir -p ~/.config/nemovideo & echo "$CLIENT_ID" > ~/.config/nemovideo/client_id
fi
curl -s -X POST "$API/api/auth/anonymous-token" -H "X-Client-Id: $CLIENT_ID"
# → {"code":0,"data":{"token":"nmv_usr_xxx","credits":100,...}}

Save token as NEMO_TOKEN, CLIENT_ID as NEMO_CLIENT_ID. Anonymous: 1 token per client per 7 days; token expires in 7 days and can be revoked at any time via Settings → API Tokens on nemovideo.com. If your token expires, request a new one with the same X-Client-Id.

Local persistence: This skill writes ~/.config/nemovideo/client_id to persist the Client-Id across sessions. This avoids generating a new ID on every request, which would hit the per-IP rate limit quickly (default 10 tokens per 7 days per IP). The file contains only a UUID — no credentials are stored locally.

2. Routing Incoming Requests to the Correct Endpoint

Use the table below to determine which endpoint should handle each type of user request.

User says...	Action	Skip SSE
"export" / "导出" / "download" / "send me the video"	→ §3.5 Export	✅
"credits" / "积分" / "balance" / "余额"

→ §3.3 Credits | ✅ |
| "status" / "状态" / "show tracks" | → §3.4 State | ✅ |
| "upload" / "上传" / user sends file | → §3.2 Upload | ✅ |
| Everything else (generate, edit, add BGM…) | → §3.1 SSE | ❌ |

3. Primary Workflow Sequences

$API = ${NEMO_API_URL:-https://mega-api-prod.nemovideo.ai}, $TOKEN = ${NEMO_TOKEN}, $WEB = ${NEMO_WEB_URL:-https://nemovideo.com}.

Skill attribution variables — do NOT hardcode:

• - $SKILL_NAME = this file's YAML frontmatter INLINECODE26
• INLINECODE27 = this file's YAML frontmatter INLINECODE28
• INLINECODE29 = detect at runtime using the first match:

1. Env SKILL_SOURCE if set
2. If this file's path contains a known platform directory (e.g. ~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor)
3. Fallback: INLINECODE35

CRITICAL: ALL API requests (including render/export/upload/state/credits) MUST include these headers. Missing them will cause export to fail with 402.
CODEBLOCK2

3.0 Initializing a New Session

curl -s -X POST "$API/api/tasks/me/with-session/nemo_agent" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -H "X-Skill-Source: $SKILL_NAME" -H "X-Skill-Version: $SKILL_VERSION" -H "X-Skill-Platform: $SKILL_SOURCE" \
  -d '{"task_name":"project","language":"<lang>"}'
# → {"code":0,"data":{"task_id":"...","session_id":"..."}}

Before any interaction can occur, a session must be established with the backend. Store the returned session identifier, as every subsequent request depends on it.

Open in browser: After creating a session, give the user a link to view/edit the task in NemoVideo:
INLINECODE36

3.1 Delivering Messages Through SSE

curl -s -X POST "$API/run_sse" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -H "Accept: text/event-stream" -H "X-Skill-Source: $SKILL_NAME" -H "X-Skill-Version: $SKILL_VERSION" -H "X-Skill-Platform: $SKILL_SOURCE" --max-time 900 \
  -d '{"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}}'

All conversational messages are transmitted to the backend and responses are streamed back using Server-Sent Events.

SSE Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result

Wait silently, don't forward | | heartbeat / empty data: | Keep waiting. Every 2 min: "⏳ Still working..." | | Stream closes | Process final response |

Typical durations: text 5-15s, video generation 100-300s, editing 10-30s.

Timeout: 10 min heartbeats-only → assume timeout. Never re-send during generation (duplicates + double-charge).

Ignore trailing "I encountered a temporary issue" if prior responses were normal.

Silent Response Fallback (CRITICAL)

Approximately 30% of editing operations complete without returning any text in the SSE stream. When the stream closes and no visible response has been received, do not treat this as an error. Instead: (1) call the project state endpoint to confirm the operation succeeded, (2) inspect the timeline for any changes that were applied, and (3) synthesize a confirmation message for the user based on what the state diff reveals.

Two-stage generation: When a raw video clip is submitted, the backend automatically runs a two-stage enrichment pipeline. Stage one processes and places the raw footage on the timeline. Stage two independently appends background music and a generated title card. Both stages emit separate SSE streams — wait for the second stream to close before reporting a completed result to the user.

3.2 Handling File Uploads

File upload: INLINECODE39

URL upload: INLINECODE40

Use me in the path; backend resolves user from token.

Supported: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

The upload endpoint accepts media files of all supported types and returns a resource identifier to be referenced in subsequent editing commands.

3.3 Checking Available Credits

curl -s "$API/api/credits/balance/simple" -H "Authorization: Bearer $TOKEN" \
  -H "X-Skill-Source: $SKILL_NAME" -H "X-Skill-Version: $SKILL_VERSION" -H "X-Skill-Platform: $SKILL_SOURCE"
# → {"code":0,"data":{"available":XXX,"frozen":XX,"total":XXX}}

Query the credits endpoint before initiating any AI-powered operation to verify the user has a sufficient balance.

3.4 Retrieving Current Project State

curl -s "$API/api/state/nemo_agent/me/<sid>/latest" -H "Authorization: Bearer $TOKEN" \
  -H "X-Skill-Source: $SKILL_NAME" -H "X-Skill-Version: $SKILL_VERSION" -H "X-Skill-Platform: $SKILL_SOURCE"

Use me for user in path; backend resolves from token. Key fields: data.state.draft, data.state.video_infos, data.state.canvas_config, data.state.generated_media.

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

Draft ready for export when draft.t exists with at least one track with non-empty sg.

Track summary format:
CODEBLOCK7

3.5 Triggering Export and Delivering the Result

Export does NOT cost credits. Only generation/editing consumes credits.

Exporting a finished project does not deduct from the user's credit balance. To complete an export: (a) send the export request with the desired output parameters, (b) poll the job status endpoint until the state is terminal, (c) confirm the job did not end in a failed state, (d) retrieve the download URL from the completed job payload, and (e) present that URL to the user along with a summary of the exported file.

b) Submit: INLINECODE52

Note: sessionId is camelCase (exception). On failure → new id, retry once.

c) Poll (every 30s, max 10 polls): INLINECODE55

Status at top-level status: pending → processing → completed / failed. Download URL at output.url.

d) Download from output.url → send to user. Fallback: $API/api/render/proxy/<id>/download.

e) When delivering the video, always also give the task detail link: INLINECODE60

Progress messages: start "⏳ Rendering ~30s" → "⏳ 50%" → "✅ Video ready!" + file + task detail link.

3.6 Recovering from an SSE Disconnection

If the SSE connection drops before a terminal event is received, follow these recovery steps: (1) Wait 2 seconds before attempting any recovery action to avoid hammering the server. (2) Re-open the SSE stream using the original session and message identifiers if a reconnect token is available. (3) If reconnection is not possible, query the project state endpoint to determine whether the operation completed despite the dropped connection. (4) If the state confirms completion, construct a response for the user from the state data rather than re-sending the original command. (5) If the state shows the operation is still in progress, inform the user and offer to check again after a short delay.

4. Translating Backend Responses Away from GUI Language

The backend is built around a graphical interface and will occasionally return instructions referencing on-screen controls — never pass these GUI-specific directions to the user verbatim; always translate them into plain conversational language.

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"

Show state via §3.4 |
| "drag/drop" / "拖拽" | Send edit via SSE |
| "preview in timeline" | Show track summary |
| "Export button" / "导出" | Execute §3.5 |
| "check account/billing" | Check §3.3 |

Keep content descriptions. Strip GUI actions.

5. Recommended Conversational Patterns

• Confirm what the user wants to achieve before dispatching any editing command, especially when the request is ambiguous.
• After each operation, briefly summarize what changed rather than simply saying the action was completed.
• When a silent response occurs, proactively report the detected changes so the user never experiences unexplained silence.
• If a requested operation would exhaust the user's credit balance, surface that information and ask for confirmation before proceeding.
• Break multi-step editing tasks into clearly communicated stages so the user understands what is happening at each point.

6. Known Constraints and Limitations

• Real-time preview streaming is not supported; users must export to review final output.
• AI generation features require an active credit balance — free-tier accounts may encounter frequent balance limits.
• Undo history is not accessible through the API; reverting changes requires manual state management by the assistant.
• Concurrent editing sessions on the same project are not supported and will produce unpredictable results.
• Some advanced timeline operations available in the desktop GUI are not yet exposed through the API surface.

7. Error Recognition and Recovery Guidance

The table below maps common HTTP error codes and backend fault states to their likely causes and the recommended recovery action.

Code	Meaning	Action
0	Success	Continue
1001

Bad/expired token | Re-auth via anonymous-token (tokens expire after 7 days) |
| 1002 | Session not found | New session §3.0 |
| 2001 | No credits | Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up at nemovideo.ai" |
| 4001 | Unsupported file | Show supported formats |
| 4002 | File too large | Suggest compress/trim |
| 400 | Missing X-Client-Id | Generate Client-Id and retry (see §1) |
| 402 | Free plan export blocked | Subscription tier issue, NOT credits. "Register at nemovideo.ai to unlock export." |
| 429 | Rate limit (1 token/client/7 days) | Retry in 30s once |

Common: no video → generate first; render fail → retry new id; SSE timeout → §3.6; silent edit → §3.1 fallback.

8. API Version Requirements and Token Permissions

Always verify that the connected client is targeting the minimum supported API version before executing any workflow — requests made against older versions may silently omit fields or behave unexpectedly. The access token presented at session creation must carry all required scopes for the operations the user intends to perform; missing scopes will produce authorization errors mid-workflow rather than at login. If a scope error is encountered, prompt the user to re-authenticate with the full permission set rather than attempting to work around the restriction.