Video Editor Background

Turn a 30-second talking-head video clip into 1080p background-swapped videos just by typing what you need. Whether it's replacing messy backgrounds in talki...

Security Scan

The skill's cloud-based video-editing actions match its description, but inconsistent metadata about config paths and the behavior of token creation/storage (plus uploading user videos to a third‑party endpoint) create unexplained risks you should review before installing.

Purpose & Capability

The name and description (cloud background-replacement) align with the API calls and upload/export workflow in SKILL.md. However the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) not declared in the registry metadata — an informational mismatch that could indicate incomplete or inconsistent packaging.

Instruction Scope

Runbook instructions are focused on session creation, SSE editing, uploads and exports to mega-api-prod.nemovideo.ai, which fits the stated purpose. They do require the agent to upload user video files and to generate/store session tokens. There are no explicit instructions to read unrelated system files or other environment variables, but the frontmatter's configPaths suggests potential local config access that is not clearly documented in the registry.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest install risk. Nothing is being downloaded or written by an installer step in the registry.

Credentials

Only a single credential (NEMO_TOKEN) is declared, which is proportionate for an API-based video service. The SKILL.md also instructs creating an anonymous token via the service and re-using it as NEMO_TOKEN; how/where that token is stored is not specified. The frontmatter again mentions a config path that would grant file-system access to user config if used — this is not justified in the registry.

Persistence & Privilege

The skill does not request always:true, does not claim elevated platform privileges, and does not instruct modifying other skills or system-wide settings. Persisting a session_id or an anonymous token for the service is expected for this workflow, but the storage mechanism is unspecified.

What to consider before installing

This skill appears to do what it says (upload a clip to a cloud service, edit, and return a rendered file) but there are a few things to check before installing: 1) Understand privacy/retention — your videos will be uploaded to mega-api-prod.nemovideo.ai; ask the publisher for a privacy/retention policy and whether uploads are encrypted at rest/in transit. 2) Verify token handling — the skill can generate and reuse an anonymous NEMO_TOKEN; confirm where and how that token and session_id are stored and whether it reuses existing tokens or writes them to disk. 3) Ask about the config path inconsistency — the SKILL.md frontmatter references ~/.config/nemovideo/, but the registry did not declare that; ask if the skill will read/write that path and why. 4) Use a limited-scope or ephemeral token (not a shared/high-privilege credential) and avoid sending sensitive footage until you trust the service. 5) If you need higher assurance, request more detail from the publisher (service domain ownership, privacy policy, expected headers/attribution, and whether uploads are shared with third parties).

Getting Started

Share your video clips and I'll get started on AI background replacement. Or just tell me what you're thinking.

Try saying:

• "replace my video clips"
• "export 1080p MP4"
• "remove my background and replace it"

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.

Video Editor Background — Replace Backgrounds in Video Clips

This tool takes your video clips and runs AI background replacement through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 30-second talking-head video clip and want to remove my background and replace it with a clean office scene — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: solid clothing colors help the AI separate you from the background more accurately.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	video-editor-background
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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)

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

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.

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 → "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.

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.