Video Editing With

Get edited video clips ready to post, without touching a single slider. Upload your raw video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "c...

Security Scan

The skill's requirements and runtime instructions are internally consistent with a cloud video-editing service: it needs a NEMO_TOKEN and directs uploads/edits to nemo-video endpoints, but there are a few minor inconsistencies and privacy considerations to review before installing.

Purpose & Capability

Name/description claim cloud-based video editing; SKILL.md instructs calls to nemovideo.ai endpoints and upload/render flows and requires a NEMO_TOKEN. Requesting a single service token is proportional and expected for this purpose.

Instruction Scope

Instructions are focused on creating a session, uploading media, interacting via SSE, polling render status, and returning download URLs — all within the stated editing workflow. The SKILL.md also describes deriving attribution headers (including detecting install path to set X-Skill-Platform), which implies the agent might inspect filesystem paths; this is not strictly necessary for core editing and is a minor scope expansion worth noting.

Install Mechanism

No install spec and no code files — instruction-only skill. That minimizes on-disk risk. All runtime behavior is API calls to a remote service.

Credentials

Only NEMO_TOKEN is declared as required and is used as the Bearer auth for service API calls. The skill also describes an anonymous-token flow to obtain a temporary token, which reduces need for long-lived secrets. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that could imply reading/writing local config; the registry summary earlier did not list config paths — this mismatch should be clarified.

Persistence & Privilege

Skill is not always-enabled and does not request elevated or cross-skill privileges. It does instruct saving session_id for job tracking (ephemeral). The referenced config path in the frontmatter could enable storing config locally if implemented; confirm whether the skill will create or modify files under ~/.config/nemovideo/ before installing.

Assessment

This skill appears to do what it says: it uploads your video files to a nemo-video service and returns edited exports using a NEMO_TOKEN. Before installing: 1) Confirm you trust the domain (mega-api-prod.nemovideo.ai) and review its privacy/storage policy because your raw videos will be uploaded off-device. 2) Use the anonymous-token flow or a disposable token rather than a long-lived production credential. 3) Ask the publisher whether the skill will read or write ~/.config/nemovideo/ (frontmatter mentions it but registry metadata did not); if you don’t want local files created, decline or sandbox the skill. 4) Monitor network activity/logs the first time you use it to ensure headers and endpoints match the documentation. These checks should reduce privacy risk; otherwise the package is internally coherent.

Getting Started

Share your raw video clips and I'll get started on AI-assisted editing. Or just tell me what you're thinking.

Try saying:

• "edit my raw video clips"
• "export 1080p MP4"
• "cut the pauses, add background music,"

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 Editing With AI — Edit and Export Polished Videos

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

A quick example: upload a 3-minute uncut screen recording, type "cut the pauses, add background music, and export as a 1-minute highlight", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 2 minutes process significantly faster.

Matching Input to Actions

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

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

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the pauses, add background music, and export as a 1-minute highlight" — 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 → "cut the pauses, add background music, and export as a 1-minute highlight" → 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.