Free To Editor

Turn a 3-minute unedited interview recording into 1080p polished edited clips just by typing what you need. Whether it's editing raw footage into a finished...

Security Scan

The skill's requirements and runtime instructions line up with a cloud-based video editing service: it reasonably needs a NEMO_TOKEN, uploads user video to the nemo backend, and has no unexpected credential or install requirements.

Purpose & Capability

The skill is an AI-assisted video editor that communicates with nemo-backed APIs; requiring a NEMO_TOKEN and using upload/render endpoints is consistent with that purpose. No unrelated credentials or binaries are requested.

Instruction Scope

Instructions describe obtaining/using a session token, uploading video, streaming SSE edits, polling render status, and returning download URLs — all within the stated editing workflow. The runtime guidance to auto-create an anonymous token and to preserve session_id is expected. Note: the frontmatter instructs auto-detecting an install path to set X-Skill-Platform, which implies the agent may read its environment/install path; this is plausible but worth awareness.

Install Mechanism

There is no install specification and no code files — the skill is instruction-only, which is the lowest-risk install posture.

Credentials

The only declared credential is NEMO_TOKEN (primaryEnv), which is proportional to a cloud video service. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported 'required config paths: none' — this mismatch should be clarified (the skill may read that config directory).

Persistence & Privilege

The skill is not force-included (always:false) and does not request elevated platform privileges. It instructs keeping session tokens for workflow operation, which is normal for a stateful cloud integration.

Assessment

This skill appears coherent for a cloud video editing service: it needs a NEMO_TOKEN and will upload your raw video to mega-api-prod.nemovideo.ai for processing. Before installing, confirm you trust that domain and its privacy terms (videos and audio will leave your machine). Note the SKILL.md can auto-create an anonymous token (100 free credits, 7-day expiry) and may read/detect an install path or config directory (~/.config/nemovideo/) — the registry metadata earlier omitted that config path, so ask the publisher to confirm whether the skill will read or store files in that directory. Finally, avoid providing unrelated secrets; only NEMO_TOKEN is required by this skill.

Getting Started

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

Try saying:

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

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.

Free to Editor — Edit and Export Finished Videos

This tool takes your raw video footage and runs AI-assisted video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 3-minute unedited interview recording and want to cut out the pauses, add background music, and export a clean final cut — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 2 minutes process significantly faster and give cleaner AI cut results.

Matching Input to Actions

User prompts referencing free to editor, 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	free-to-editor
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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)

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute 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

Common Workflows

Quick edit: Upload → "cut out 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 out 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 with H.264 codec for the widest compatibility across platforms.