Nemo Video Online

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

Security Scan

The skill's requirements and runtime instructions mostly match a cloud video-editing service, but there are a few inconsistencies and privacy/operational choices (automatic token minting & advice to hide tokens, mismatched metadata) that warrant caution before installing.

Purpose & Capability

The skill name/description (cloud video editing) aligns with the single required credential (NEMO_TOKEN) and the documented API endpoints. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — this mismatch should be clarified.

Instruction Scope

Instructions are detailed and confined to interacting with the nemo-api endpoints (auth, upload, SSE, render, credits, state). Concerns: (1) the skill directs the agent to auto-obtain an anonymous NEMO_TOKEN if none is present, then says not to show raw API responses or token values to the user — hiding tokens reduces transparency; (2) it instructs storing a session_id but does not specify where or for how long (in-memory vs disk), which affects persistence and privacy; (3) it requires detecting install paths to set attribution headers, potentially reading filesystem paths to decide X-Skill-Platform. No instructions request unrelated files or other credentials.

Install Mechanism

There is no install spec and no code files—this is instruction-only, so nothing will be written to disk by an install step. That lowers supply-chain risk.

Credentials

Only NEMO_TOKEN is declared and used; that is proportionate for a third-party cloud service. The automated anonymous-token flow (POST to the vendor endpoint to receive a token) is reasonable but combined with the instruction to not display token values may be undesirable for users who want transparency. The frontmatter's configPaths value (present in SKILL.md) is not reflected in registry metadata, which may indicate sloppy metadata or unstated file access expectations.

Persistence & Privilege

The skill is not always-enabled and does not request special platform privileges. It asks to store a session_id for ongoing requests (normal for session-based APIs) but does not request modifying other skills or system-wide settings.

What to consider before installing

This skill appears to be a straightforward remote video-editing integration, but check these before installing: (1) Understand where and how the skill stores credentials/session IDs — ask the maintainer whether the token/session are persisted to disk and where; (2) The skill will automatically request an anonymous NEMO_TOKEN from a third-party endpoint if none is set and the instructions explicitly say not to show tokens — if you prefer control, set your own NEMO_TOKEN rather than allowing automatic minting; (3) Uploading sends your video content to nemo's servers — review the vendor's privacy/retention policy before sending sensitive material; (4) Clarify the configPaths mismatch (SKILL.md lists ~/.config/nemovideo/) to confirm whether the skill will read or write files under that path; (5) If you need higher assurance, request source code or a privacy/security statement from the publisher, or run uploads with non-sensitive test videos first.

Getting Started

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

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "trim the video, add subtitles, and"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Nemo Video Online — Edit and Export Videos Online

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

A quick example: upload a 2-minute screen recording or phone video, type "trim the video, add subtitles, and export as MP4", and you'll get a 1080p MP4 back in roughly 30-90 seconds. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process noticeably faster.

Matching Input to Actions

User prompts referencing nemo video online, 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.

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

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

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

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.

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

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)

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 → "trim the video, add subtitles, and export as MP4" → Download MP4. Takes 30-90 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 "trim the video, add subtitles, and export as MP4" — 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 platforms.