Best Product Video

Skip the learning curve of professional editing software. Describe what you want — cut the best moments, add background music, and show the product from mult...

Security Scan

The skill broadly matches a cloud video-editing integration, but there are small inconsistencies about required credentials and a few instructions (detecting install paths, local file uploads) that you should understand before installing.

Purpose & Capability

Name and description claim a cloud-based AI video editor and the SKILL.md describes calls to a nemo video API at mega-api-prod.nemovideo.ai — that aligns. However the registry metadata marks NEMO_TOKEN as required and lists a config path (~/.config/nemovideo/), while the runtime instructions explicitly provide an anonymous-token fallback (generate UUID + POST /api/auth/anonymous-token). Declaring NEMO_TOKEN as required but also documenting an anonymous fallback is inconsistent and worth clarifying.

Instruction Scope

Instructions direct the agent to create sessions, upload user-provided media, stream SSE responses, poll render status, and include specific attribution headers — all coherent for a video-rendering integration. They also tell the agent to detect an install path to set X-Skill-Platform and to accept local file paths for multipart uploads. Detecting install paths implies reading agent filesystem locations (e.g., ~/.clawhub/ or ~/.cursor/skills/) which is not strictly necessary for functionality and should be clarified; the upload instructions assume the agent can access user-specified local file paths or URLs.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. Nothing will be downloaded or extracted by the skill itself.

Credentials

Only NEMO_TOKEN is requested as a primary credential (proportional for an API-based service). However the registry lists it as required while SKILL.md documents creating a temporary anonymous token if NEMO_TOKEN is absent — this mismatch is suspicious. Also metadata lists a config path (~/.config/nemovideo/) that the runtime instructions never require reading. Clarify whether a persistent secret is actually necessary or if anonymous tokens are intended.

Persistence & Privilege

always is false and the skill has no install-time persistence. It does request a session token from the service (normal for this use). The skill does not request to modify other skills or system-wide settings.

What to consider before installing

This skill appears to be a normal cloud video-editing integration, but check two things before installing: (1) credential intent — the registry says NEMO_TOKEN is required but the SKILL.md also explains how to obtain a temporary anonymous token; ask the author whether you need to set a permanent NEMO_TOKEN (which would grant the skill long-lived API access) or whether anonymous tokens are sufficient; (2) privacy of uploads — the skill will upload user media to https://mega-api-prod.nemovideo.ai (including potentially large or sensitive product clips), so confirm you are comfortable sending that content to this external service and review its terms/privacy. Also be aware the instructions ask the agent to inspect install paths to set an attribution header; if you prefer, ask for a version of the skill that does not attempt to read local filesystem paths. If you need higher assurance, request the service's official homepage, a maintainer contact, or source code for the integration.

Getting Started

Share your product footage and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "create my product footage"
• "export 1080p MP4"
• "cut the best moments, add background"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Best Product Video — Create and Export Product Videos

Drop your product footage in the chat and tell me what you need. I'll handle the AI video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a three product photos and a 30-second demo clip, ask for cut the best moments, add background music, and show the product from multiple angles, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — clean white or neutral backgrounds make AI enhancement significantly more effective.

Matching Input to Actions

User prompts referencing best 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is best-product-video, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the best moments, add background music, and show the product from multiple angles" — 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 Amazon, Shopify, and social platforms.

Common Workflows

Quick edit: Upload → "cut the best moments, add background music, and show the product from multiple angles" → 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.