Ai Video Editor Change Background

Skip the learning curve of professional editing software. Describe what you want — remove my background and replace it with a clean office scene — and get ba...

Security Scan

The skill's required token, endpoints, and runtime instructions are consistent with a cloud video-background-replacement service; nothing in the manifest asks for unrelated credentials or installs arbitrary code, but you should be aware it uploads your videos to an external service and will obtain/hold a short-lived token if none is provided.

Purpose & Capability

The skill claims to perform cloud-based video background replacement and requires a single service credential (NEMO_TOKEN) and references a nemo video API host — this is proportionate. Minor inconsistency: the top-level registry metadata lists no required config paths, but the SKILL.md frontmatter declares a configPaths entry (~/.config/nemovideo/). This mismatch is likely benign (metadata divergence) but should be corrected for clarity.

Instruction Scope

Runtime instructions are focused on creating/using a session, uploading videos, starting renders, and handling SSE event streams — all expected for this purpose. They instruct the agent to POST files and metadata to the nemovideo API and to generate an anonymous token if NEMO_TOKEN is absent. This involves transmitting user video files and derived metadata to an external service, which is expected but has privacy implications. The instructions do not direct the agent to read unrelated system credentials or arbitrary files.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is downloaded or written by an installer. That lowers risk compared to skills that install binaries or fetch archives from arbitrary URLs.

Credentials

Only one credential (NEMO_TOKEN) is required and is the declared primary credential. The SKILL.md documents a fallback anonymous-token flow (POST to the service to obtain a short-lived token) which explains why no other credentials are requested. There are no unrelated SECRET/TOKEN env vars requested.

Persistence & Privilege

The skill does not request 'always: true' and does not declare any privileged persistence or modification of other skills. It can invoke autonomously (the platform default), which is normal; there is no evidence it alters other skills or system-wide configs.

Assessment

This skill appears to be what it says: a cloud-based video background replacer that needs a NEMO_TOKEN or will request a short-lived anonymous token and will upload your videos to nemo's API. Before installing/using: (1) confirm the domain (mega-api-prod.nemovideo.ai) and the service's privacy/TOS if you will upload sensitive footage, (2) decide whether to provide your own NEMO_TOKEN (more control) or allow the skill to create an anonymous token, (3) be aware the skill will send full media files off‑device — don't use it for confidential content unless you trust the provider, and (4) note the small metadata mismatch (configPaths declared in SKILL.md but not in the registry) — ask the publisher to correct the manifest for clarity.

Getting Started

Send me your video clips and I'll handle the AI background replacement. Or just describe what you're after.

Try saying:

• "replace a 30-second talking-head clip shot at home into a 1080p MP4"
• "remove my background and replace it with a clean office scene"
• "replacing messy home backgrounds in video recordings for content creators"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

AI Video Editor Change Background — Replace Video Backgrounds with AI

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

Here's a typical use: you send a a 30-second talking-head clip shot at home, ask for remove my background and replace it with a clean office scene, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — solid or contrasting clothing helps the AI detect your outline more accurately.

Matching Input to Actions

User prompts referencing ai video editor change 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 ai-video-editor-change-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).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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.

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)

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 for widest compatibility.

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.