Opus Ai Video Editor Job

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

Security Scan

The skill's declared purpose (cloud video editing) matches most of its instructions, but there are small inconsistencies (metadata vs registry) and some privacy/operational behaviors you should understand before using it.

Purpose & Capability

The skill claims to perform cloud video editing and requires a single API token (NEMO_TOKEN). That aligns with the listed API endpoints and upload/export workflow. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that the registry metadata did not declare — a minor incoherence about required config access.

Instruction Scope

Instructions are focused on connecting to a remote API, creating sessions, uploading media, streaming SSE events, and polling render status — all coherent with video-editing. The skill also instructs the agent to detect install path (e.g., ~/.clawhub/, ~/.cursor/skills/) to set an X-Skill-Platform header, which implies reading installation paths/locations; that file-system inspection is not declared in the top-level registry and is worth clarifying. The instructions tell the agent to upload user videos to a third-party backend (mega-api-prod.nemovideo.ai) — expected for this service but a privacy risk.

Install Mechanism

There is no install spec and no code files — this is instruction-only, so nothing is downloaded or installed by default. That reduces supply-chain risk.

Credentials

Only one env var is required (NEMO_TOKEN), which is appropriate for an API-backed editor. The skill will also auto-request an anonymous token from the remote API if NEMO_TOKEN is not present; this is functional but means uploads can proceed without an explicit long-lived credential. The SKILL.md also references a config path (~/.config/nemovideo/) in its metadata but the registry listed no required config paths — inconsistent declaration.

Persistence & Privilege

The skill is not always-enabled and does not request persistent platform privileges. It does not attempt to modify other skills or system-wide settings in the instructions provided.

What to consider before installing

This skill appears to do what it says (upload your video to a cloud backend for automated editing), but check a few things before using it: 1) Confirm you trust the domain (mega-api-prod.nemovideo.ai) and understand that your videos will be uploaded to that third party — don’t send sensitive footage unless you accept that. 2) Prefer providing a limited-scope or short-lived NEMO_TOKEN you control; if you don’t have one the skill will obtain an anonymous token for you automatically (functional but may still upload your data). 3) Ask the author to clarify the config path mention (~/.config/nemovideo/) and the install-path detection used to set X-Skill-Platform — those imply the agent may read install/config locations, which wasn’t declared elsewhere. 4) Because there is no source or homepage, consider requesting the service privacy/terms and a way to review or revoke tokens. If any of these points are unacceptable, do not install or provide your credentials.

Getting Started

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

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "cut the best highlights, add captions,"

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.

Opus AI Video Editor — Edit and Export Videos Automatically

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

Here's a typical use: you send a a 10-minute raw interview recording, ask for cut the best highlights, add captions, and export a 60-second clip, 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 source clips under 5 minutes produce the most accurate AI edits.

Matching Input to Actions

User prompts referencing opus ai video editor job, 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 opus-ai-video-editor-job, 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 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

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.

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)

Common Workflows

Quick edit: Upload → "cut the best highlights, add captions, and export a 60-second clip" → 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 the best highlights, add captions, and export a 60-second clip" — 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 across all platforms.