Video Background

content creators, remote workers, marketers replace video clips into background-replaced videos using this skill. Accepts MP4, MOV, AVI, WebM up to 500MB, re...

Security Scan

The skill's requests and runtime instructions are consistent with its stated purpose (cloud video background replacement) and it only asks for a single service token and a small config path, but it will upload user video files to an external API so you should review privacy/ownership before use.

Purpose & Capability

Name/description (remote video background replacement) match the declared requirements: a single service token (NEMO_TOKEN) and a nemovideo config path. No unrelated credentials, binaries, or surprising capabilities are requested.

Instruction Scope

SKILL.md instructs the agent to read NEMO_TOKEN (or obtain an anonymous token from the nemovideo API), create a session, upload videos, stream SSE responses, and poll render status — all expected for a cloud render workflow. It mentions detecting install path and a config directory (~/.config/nemovideo/) which implies inspecting user environment; this is plausible to set attribution headers or persist session info but is worth noting.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is downloaded or written by an installer. Lowest-risk category for install mechanism.

Credentials

Only one required environment variable (NEMO_TOKEN) is declared as the primary credential. The skill documents falling back to an anonymous token flow if none is present. The declared config path (~/.config/nemovideo/) is consistent with a client that may persist session info; the requested env/config access is proportionate to the stated service.

Persistence & Privilege

Skill is not forced-always, and allows normal autonomous invocation. It does not request system-wide or other-skills configuration changes; session tokens are used for the remote service only.

Assessment

This skill appears to do what it says: it will upload your videos to an external service (mega-api-prod.nemovideo.ai) and use a NEMO_TOKEN (or obtain a 7-day anonymous token) to run cloud GPU rendering. Before installing/using it: (1) confirm you trust the external service and review its privacy/terms (you are uploading potentially sensitive media); (2) avoid supplying long-lived personal credentials unless you trust the operator — use the anonymous token flow if you prefer temporary access; (3) be aware the skill may read/write a small config directory (~/.config/nemovideo/) to store session data and may detect the agent install path for attribution headers; (4) do not upload content you cannot share. If you need higher assurance, ask the publisher for source code or a reputable homepage and verify the API domain and TLS certificate.

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the AI background replacement.

Try saying:

• "replace a 30-second talking-head clip shot in a messy room into a 1080p MP4"
• "remove my background and replace it with a clean office scene"
• "replacing or removing video backgrounds without a green screen for content creators, remote workers, 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.

Video Background — Remove and Replace Video Backgrounds

Send me your video clips and describe the result you want. The AI background replacement runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 30-second talking-head clip shot in a messy room, type "remove my background and replace it with a clean office scene", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: steady camera shots produce cleaner background removal with fewer edge artifacts.

Matching Input to Actions

User prompts referencing video background, 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-background, 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).

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

Error Handling

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 credits in your account"
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 or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the 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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "remove my background and replace it with a clean office scene" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the best balance of quality and file size.

Common Workflows

Quick edit: Upload → "remove my background and replace it with a clean office scene" → Download MP4. Takes 30-60 seconds 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.