Video Editing With Blender

Skip the learning curve of professional editing software. Describe what you want — cut dead footage, add smooth transitions, and sync audio in Blender style...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud-based video-editing service: it asks for a single service token, uploads user video files to a named backend, and contains no install or local privileged actions — but the source is unknown and there are a few small metadata inconsistencies you should review before installing.

Purpose & Capability

The skill advertises cloud-based Blender-style video editing and its instructions only reference uploading media, creating a session, submitting render jobs, and polling for results on a nemovideo.ai backend. The single required env var (NEMO_TOKEN) is necessary and expected for a cloud API. Note: the skill frontmatter mentions a config path (~/.config/nemovideo/) but the registry metadata lists no required config paths — a minor inconsistency.

Instruction Scope

SKILL.md stays within the editing workflow: check for NEMO_TOKEN, obtain an anonymous token if missing, create sessions, upload files, use SSE for edits, and export results. It explicitly instructs not to expose tokens. All file and network actions are directed to the stated backend (mega-api-prod.nemovideo.ai). There is no instruction to read unrelated local files or other credentials.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing will be written to disk or downloaded during installation — lowest-risk install mechanism.

Credentials

Only one credential (NEMO_TOKEN) is required and is the primary credential for the described cloud service, which is proportional. The skill will also attempt to mint an anonymous token by calling the backend if NEMO_TOKEN is absent, which is consistent with its behavior but worth noting. The earlier registry metadata omitted the config path that the frontmatter references — check whether the skill actually needs or will read ~/.config/nemovideo/.

Persistence & Privilege

always:false and no install scripts are requested. The skill does not ask to modify agent/system-wide settings or other skills. Autonomous invocation is allowed (platform default) but not combined with elevated persistence.

Assessment

This skill appears to do what it says: it uploads your videos to a named cloud backend (mega-api-prod.nemovideo.ai) for processing and requires one token (NEMO_TOKEN) or will request an anonymous token on your behalf. Before installing: confirm you are comfortable uploading media to that domain (privacy/data-retention/TOS), verify whether you prefer supplying your own NEMO_TOKEN or allow anonymous tokens, and be aware there is no visible source/homepage for the skill (owner ID only). Also note the minor metadata mismatch about a config path (~/.config/nemovideo/) — if you have sensitive data in that location, ask the publisher whether the skill reads it. If any of these are unacceptable, do not enable the skill.

Getting Started

Ready when you are. Drop your raw video clips here or describe what you want to make.

Try saying:

• "edit a 2-minute raw footage file recorded on a DSLR into a 1080p MP4"
• "cut dead footage, add smooth transitions, and sync audio in Blender style"
• "editing and assembling video clips with Blender-style sequencing and effects for indie filmmakers and motion graphics 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.

Video Editing with Blender — Edit and Export Blender Videos

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

Here's a typical use: you send a a 2-minute raw footage file recorded on a DSLR, ask for cut dead footage, add smooth transitions, and sync audio in Blender style, 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 — shorter clips under 60 seconds process significantly faster and yield cleaner results.

Matching Input to Actions

User prompts referencing video editing with blender, 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-editing-with-blender
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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)

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

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.

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

Common Workflows

Quick edit: Upload → "cut dead footage, add smooth transitions, and sync audio in Blender style" → 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 "cut dead footage, add smooth transitions, and sync audio in Blender style" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the widest compatibility across platforms.