Editor Modi

Skip the learning curve of professional editing software. Describe what you want — cut out silences, add transitions, and export a clean final video — and ge...

Security Scan

The skill's behaviour is mostly coherent for a cloud video-editing service, but small inconsistencies in its metadata and instructions that ask the agent to inspect local install/config paths — plus the automatic upload of potentially sensitive videos to an external API — warrant caution.

Purpose & Capability

Name/description match the runtime instructions: the skill routes uploads and edit commands to a remote video-editing API and requires a NEMO_TOKEN. However there's an inconsistency: the registry metadata reported 'Required config paths: none' but the SKILL.md frontmatter lists a config path (~/.config/nemovideo/). That mismatch is unexplained but plausibly harmless (may indicate stale metadata).

Instruction Scope

The instructions direct the agent to upload user video files (up to 500MB) and call multiple external endpoints at mega-api-prod.nemovideo.ai — coherent for a cloud editor. But the doc also instructs the agent to detect the local install path to set an X-Skill-Platform header and references a local config path in YAML frontmatter. Detecting install paths or reading ~/.config may require the agent to inspect the filesystem, which is not strictly necessary for editing and broadens the scope of data the agent might access. The skill also instructs creating anonymous tokens when NEMO_TOKEN is absent (fine), but overall the runtime guidance gives the agent discretion to poll state, stream SSE, and upload files — all reasonable for the feature but worth explicit consent.

Install Mechanism

No install spec and no code files — instruction-only skill. This minimizes installation risk because nothing is written to disk by the skill package itself.

Credentials

The skill only declares a single credential (NEMO_TOKEN) which is appropriate for a third-party API. However the SKILL.md frontmatter also references a config path (~/.config/nemovideo/) not declared in the registry summary; if the agent attempts to read that path it would access local user configuration beyond a single token. Consider this mismatch a potential overreach until clarified.

Persistence & Privilege

The skill is not forced-always and can be invoked by the user; it does not request any platform-level persistence or modification of other skills. Autonomous invocation is allowed by default but is not combined with any other high-risk privileges here.

What to consider before installing

This skill appears to be a cloud video editor that uploads your footage to a third-party API and requires a NEMO_TOKEN. Before installing or using it: 1) Understand that any video you upload will leave your device and be processed on mega-api-prod.nemovideo.ai — don't upload sensitive or private footage unless you trust the service and its privacy policy. 2) Ask the publisher to clarify the config-path reference (~/.config/nemovideo/) and whether the agent will read local files or only use the provided token; limit filesystem access if possible. 3) If you don't want to share a persistent token, use the anonymous token flow but recognize it still sends files to the same external endpoint. 4) Verify the third-party domain and service reputation outside the skill (official docs, TLS cert, privacy/retention policy). If you need lower-risk testing, exercise the skill with non-sensitive short sample clips first.

Getting Started

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

Try saying:

• "edit a 2-minute unedited screen recording into a 1080p MP4"
• "cut out silences, add transitions, and export a clean final video"
• "editing raw footage into polished videos quickly for content creators"

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.

Editor Modi — Edit and Export Polished Videos

Send me your raw video footage 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 unedited screen recording, type "cut out silences, add transitions, and export a clean final video", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

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

Matching Input to Actions

User prompts referencing editor modi, 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 editor-modi, 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).

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)

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

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

Common Workflows

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