Product Video

Get polished product videos ready to post, without touching a single slider. Upload your product images or footage (MP4, MOV, JPG, PNG, up to 500MB), say som...

Security Scan

The skill's requirements and runtime instructions are coherent with its stated purpose (uploading media and driving a cloud video-rendering API); nothing requested is disproportionate or unrelated to creating product videos.

Purpose & Capability

The skill is a cloud-backed product-video creation helper and only asks the agent to talk to nemovideo.ai and to use a single service token (NEMO_TOKEN). The declared metadata (NEMO_TOKEN, config path) aligns with interacting with a backend video service and with uploading/downloading media.

Instruction Scope

Instructions describe creating sessions, uploading user-provided media, posting SSE messages, polling render status, and returning download URLs — all within the expected scope. Two small points to note: (1) the agent is instructed to detect an install path (~/.clawhub, ~/.cursor) to set an attribution header (this requires reading the local filesystem), and (2) uploads reference local file paths for multipart posts (expected for uploading user files). Both are consistent with the skill's purpose but mean the agent will access files the user supplies and may probe a couple of well-known paths.

Install Mechanism

There is no install spec (instruction-only), so nothing is written to disk by the skill itself. This is the lowest-risk install model.

Credentials

The only declared credential is NEMO_TOKEN, which is proportionate for a cloud API. However, the SKILL.md includes a fallback anonymous-token flow when NEMO_TOKEN is absent, so the registry's 'required env var' claim is stricter than the runtime instructions; this is a mild inconsistency but not a security red flag. The metadata also references a config path (~/.config/nemovideo/) which is plausible but not strictly necessary based on the instructions.

Persistence & Privilege

The skill does not request always:true and is instruction-only. It does not modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) but not combined with any broad or unrelated credential access.

Assessment

This skill sends any media you provide to mega-api-prod.nemovideo.ai for cloud rendering and will use either your NEMO_TOKEN (if present) or obtain a short-lived anonymous token. Before installing or using it, confirm you are comfortable uploading the images/video (no sensitive content), and avoid pasting long-lived secrets unless you trust the provider. Note the small inconsistency: the registry marks NEMO_TOKEN as required, but the runtime flow can obtain an anonymous token if none is present. If you plan to provide your own NEMO_TOKEN, ensure it is scoped appropriately. Finally, review the service’s privacy/terms (where available) and be aware the agent may check a couple of local paths to set an attribution header — this only probes known install locations and is used for telemetry/attribution according to the instructions.

Getting Started

Got product images or footage to work with? Send it over and tell me what you need — I'll take care of the AI video creation.

Try saying:

• "create five product photos and a logo file into a 1080p MP4"
• "create a 30-second product showcase video with background music and text overlays"
• "creating product showcase videos for e-commerce and social media for e-commerce sellers and marketers"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Product Video — Create and Export Product Videos

This tool takes your product images or footage and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have five product photos and a logo file and want to create a 30-second product showcase video with background music and text overlays — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: using a plain or white background in your product photos gives the AI cleaner results.

Matching Input to Actions

User prompts referencing product video, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

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	❌

Cloud Render Pipeline Details

Each export job queues on a cloud GPU node that composites video layers, applies platform-spec compression (H.264, up to 1080x1920), and returns a download URL within 30-90 seconds. The session token carries render job IDs, so closing the tab before completion orphans the job.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: product-video
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

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

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute export workflow

Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

Error Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

Common Workflows

Quick edit: Upload → "create a 30-second product showcase video with background music and text overlays" → Download MP4. Takes 1-2 minutes for a 30-second clip.

Batch style: Upload multiple files in one session. Process them one by one with different instructions. Each gets its own render.

Iterative: Start with a rough cut, preview the result, then refine. The session keeps your timeline state so you can keep tweaking.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a 30-second product showcase video with background music and text overlays" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, JPG, PNG for the smoothest experience.

Export as MP4 for widest compatibility across e-commerce platforms and social media.