Editor Hiring

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

Security Scan

The skill's requests and runtime instructions are internally consistent with a cloud video-editing service, but the package has minor metadata inconsistencies, an unknown source, and will upload user media to an external API — review privacy/billing implications before use.

Purpose & Capability

The skill is described as a cloud video-editing assistant and only requests a single API credential (NEMO_TOKEN), which matches that purpose. However, the SKILL.md includes a required config path (~/.config/nemovideo/) in its internal metadata while the registry summary lists no required config paths — this mismatch in declared metadata should be clarified. The skill also derives attribution headers from an install path that doesn't exist in an instruction-only package (minor inconsistency).

Instruction Scope

Runtime instructions direct the agent to obtain or reuse a NEMO_TOKEN, create a session, upload user video files (up to 500MB), and call render/export endpoints on mega-api-prod.nemovideo.ai. All of these actions are consistent with the stated editing purpose. Important: the instructions explicitly require sending user media and auth tokens to an external service and instruct the agent to save session identifiers; this is expected behavior but has privacy and billing implications.

Install Mechanism

No install spec or third-party downloads are present (instruction-only). That minimizes code-install risk. The skill relies entirely on network API calls rather than installing binaries.

Credentials

Only one credential (NEMO_TOKEN) is declared as required/primary, which is proportionate for a remote editing API. Be aware that this token authorizes uploads, session creation, and exports (and may be tied to credits/billing). The SKILL.md's internal metadata also references a config path (~/.config/nemovideo/) not declared in the registry, which is a small inconsistency to confirm.

Persistence & Privilege

The skill is not force-included (always: false) and is user-invocable. It asks to save session_id for workflow continuity but does not request elevated system privileges or modify other skills' configs. Autonomous invocation is allowed by default but not combined here with unusual privileges.

Assessment

This skill appears to do what it says: it will upload your raw video files to a remote service (mega-api-prod.nemovideo.ai) and use a NEMO_TOKEN to create sessions, edit, and export results. Before installing or using it, consider: 1) Source and trust — the skill has no homepage and the publisher is unknown; verify the service and its privacy/billing terms. 2) Privacy — any video you upload will leave your device; do not upload sensitive content unless you trust the service. 3) Credential scope — the NEMO_TOKEN grants upload/render access and may consume credits or incur charges; prefer limited-scope or anonymous tokens when available. 4) Metadata mismatch — SKILL.md references a config path (~/.config/nemovideo/) that the registry does not list; confirm where session tokens and state are stored. If you need higher assurance, request the service's documentation or a published homepage before proceeding.

Getting Started

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

Try saying:

• "edit a 3-minute unedited interview recording into a 1080p MP4"
• "cut out pauses, add transitions, and export a clean final video"
• "replacing a human editor with AI to produce ready-to-publish videos for content creators and small business owners"

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.

Editor Hiring — Edit Videos Without Hiring Editors

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

A quick example: upload a 3-minute unedited interview recording, type "cut out pauses, 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 2 minutes process significantly faster and use fewer credits.

Matching Input to Actions

User prompts referencing editor hiring, 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-hiring, 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut out pauses, 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 across platforms and clients.

Common Workflows

Quick edit: Upload → "cut out pauses, 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.