Ultimate Video

Skip the learning curve of professional editing software. Describe what you want — trim silences, add transitions, and export a polished final cut — and get...

Security Scan

The skill is internally consistent with a cloud video-editing connector: it requires/uses a NEMO_TOKEN (and can obtain an anonymous token), uploads video files to nemovideo's API, and has no installer — but the publisher is unknown, there is a small metadata mismatch, and you should review privacy before uploading content.

Purpose & Capability

The name/description (cloud video editing, trimming, transitions, export) match the runtime instructions: POST/UPLOAD/EXPORT endpoints, SSE for edits, and file uploads. Requesting a NEMO_TOKEN is coherent with a remote API service authentication need.

Instruction Scope

Instructions instruct the agent to read NEMO_TOKEN (if present), otherwise obtain an anonymous token by POSTing to the service and then create sessions, upload files (up to 500MB), drive SSE edit flows, and poll export status. This is within the domain of a cloud video-editing skill but does mean user video files and metadata will be uploaded to a third-party endpoint (mega-api-prod.nemovideo.ai). The skill explicitly says not to expose tokens in UI output.

Install Mechanism

No install steps or code are present (instruction-only). That minimizes local disk/write risk. There is no download or execution of third-party code described.

Credentials

Only NEMO_TOKEN is required/declared and is the primary credential — appropriate for this service. The skill will generate an anonymous token if none is provided. Minor inconsistency: the registry summary listed no required config paths, but the SKILL.md YAML frontmatter references a config path (~/.config/nemovideo/). This is likely benign but worth noting.

Persistence & Privilege

always is false and there is no install or persistent system modification. The skill can be invoked autonomously (normal default) but it does not request elevated or system-wide privileges.

Assessment

This skill behaves like a cloud-based video editor: it will upload your video files and use a NEMO_TOKEN (or obtain an anonymous token for you) to call mega-api-prod.nemovideo.ai. Before installing/using it, confirm you are comfortable with third-party processing of your videos (sensitive footage should not be uploaded). The publisher/homepage are not provided here — consider verifying the service domain, checking a privacy policy/terms, and optionally supplying your own NEMO_TOKEN rather than relying on an anonymous token. The small metadata mismatch (declared config path in SKILL.md vs registry fields) is not a functional red flag but worth asking the publisher about if provenance matters. If you need higher assurance, request a homepage, privacy policy, and source or prefer a skill from a known provider.

Getting Started

Got raw video footage to work with? Send it over and tell me what you need — I'll take care of the AI video enhancement.

Try saying:

• "create a 2-minute unedited screen recording into a 1080p MP4"
• "trim silences, add transitions, and export a polished final cut"
• "turning raw footage into a fully edited, ready-to-publish video for content creators and marketers"

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.

Ultimate Video — Edit and Export Complete Videos

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

A quick example: upload a 2-minute unedited screen recording, type "trim silences, add transitions, and export a polished final cut", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: splitting long recordings into segments before uploading speeds up processing.

Matching Input to Actions

User prompts referencing ultimate video, 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 ultimate-video, 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)

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim silences, add transitions, and export a polished final cut" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the best balance of quality and file size.

Common Workflows

Quick edit: Upload → "trim silences, add transitions, and export a polished final cut" → 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.