Video Editor Hire

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

Security Scan

The skill's declared purpose (cloud video editing) aligns with most of its instructions, but a few mismatches and privacy-related behaviors (anonymous token generation, required network uploads, metadata vs registry inconsistency, unknown source/no homepage) warrant caution before installing.

Purpose & Capability

Name/description match the runtime instructions: it routes uploads and editing commands to a remote video-processing API (mega-api-prod.nemovideo.ai) and requires a NEMO_TOKEN. That credential is proportional to the stated purpose. Minor incoherence: SKILL.md frontmatter lists a configPaths (~/.config/nemovideo/) but the registry metadata above shows no required config paths — the mismatch should be clarified.

Instruction Scope

Instructions tell the agent to upload user video files and to POST to several API endpoints, create and store session_id values, and auto-generate anonymous tokens if NEMO_TOKEN is not present. These network operations are expected for a cloud editor, but they involve transmitting potentially sensitive user videos to an external third-party domain. The SKILL.md also instructs the agent to suppress display of raw API responses and token values (UX-appropriate, but also reduces transparency). The instructions do not request unrelated local files or other credentials.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That minimizes install-time risk.

Credentials

Only NEMO_TOKEN is declared as required (primaryEnv). That is proportionate for a service that needs an API token. The skill will generate an anonymous token via an API call if none is present — acceptable but means the skill can operate without the user explicitly providing credentials. No other unrelated secrets are requested.

Persistence & Privilege

always is false and there is no install-time modification of other skills or system-wide settings described. The skill stores a session_id for its own use, which is normal. Autonomous invocation is allowed (platform default) but not combined with other high privileges here.

What to consider before installing

This skill appears to do what it says (send your clips to a cloud service for editing), but exercise caution before installing or using it with sensitive footage. Specific points to consider: - It will upload your raw video files to mega-api-prod.nemovideo.ai. Only use it for content you’re comfortable sending to a third party. Check the service’s privacy policy and retention rules if possible. - If you don’t provide a NEMO_TOKEN, the skill will obtain an anonymous token automatically and proceed — this reduces user control over credentials and auditing. If you have an account, prefer supplying your own token. - The SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) but the registry summary did not — ask the publisher to clarify whether the skill will read/write local config files. - The package has no homepage or visible publisher information; if trust matters, ask the publisher for a homepage, privacy policy, or documentation before use. - Test first with non-sensitive short clips to confirm behavior (uploads, returned URLs, headers) and verify the download URL and retention behavior. If you need help drafting questions to ask the publisher (privacy, retention, how tokens/sessions are stored), tell me and I can suggest them.

Getting Started

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

Try saying:

• "edit my raw footage"
• "export 1080p MP4"
• "cut the pauses, add background music,"

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.

Video Editor Hire — Edit and Export Finished Videos

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

Here's a typical use: you send a a 2-minute unedited interview recording, ask for cut the pauses, add background music, and export a clean final cut, 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 — breaking long footage into shorter scenes speeds up processing and gives you more control over each segment.

Matching Input to Actions

User prompts referencing video editor hire, 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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	video-editor-hire
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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 the pauses, add background music, and export a clean 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the pauses, add background music, and export a clean 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 for widest compatibility across platforms and devices.