Free Generation Editing

Skip the learning curve of professional editing software. Describe what you want — generate a new edited video from my footage with cuts and transitions — an...

Security Scan

The skill's runtime instructions mostly match a cloud video-editing service, but there are inconsistencies (a config path declared in the skill frontmatter that isn't in the registry metadata) and a few telemetry/fingerprinting behaviours worth noting before installing.

Purpose & Capability

Name/description align with the actions in SKILL.md (upload clips, create sessions, render/export). Requesting a single service token (NEMO_TOKEN) is appropriate for a cloud video-editing backend. However, the SKILL.md frontmatter lists a required config path (~/.config/nemovideo/) which the registry metadata earlier claimed was 'none' — this mismatch is incoherent and worth clarifying.

Instruction Scope

Instructions are focused on interacting with the remote API (session creation, SSE chat, upload, export). They do not ask the agent to read arbitrary local files beyond user-provided uploads. The skill requires adding three attribution headers to every request (X-Skill-Source, X-Skill-Version, X-Skill-Platform), which is unusual because it forces the agent to reveal skill identity/version and attempts to auto-detect install platform — this is effectively telemetry/fingerprinting and should be called out.

Install Mechanism

Instruction-only skill with no install spec or code to write on disk; lowest install risk. There is no package download or binary installation.

Credentials

The skill declares a single primary credential (NEMO_TOKEN), which is proportionate for a cloud API. The inconsistency about the config path (~/.config/nemovideo/) raises a concern: if present, that path could contain local tokens or config and was not listed in the registry metadata — clarify whether the agent will read that path and why.

Persistence & Privilege

The skill does not request always:true and does not claim to modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) but not combined with additional privileged requests.

What to consider before installing

This skill appears to implement a cloud video-editing workflow and only needs one API token (NEMO_TOKEN), which is reasonable. Before installing: 1) Confirm whether the agent will read ~/.config/nemovideo/ (the SKILL.md frontmatter mentions it but the registry did not) — that directory could contain tokens or config. 2) Understand that every request includes attribution headers (skill name/version and a platform fingerprint) which may reveal usage metadata to the backend. 3) If you don't want to provide a persistent NEMO_TOKEN, the skill supports obtaining an anonymous short-lived token, which reduces long-term exposure. 4) Verify the remote host (mega-api-prod.nemovideo.ai) and review its privacy/terms for uploaded media and retention. If you need absolute caution, avoid providing a long-lived NEMO_TOKEN and use the anonymous flow or skip installing.

Getting Started

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

Try saying:

• "generate my video clips"
• "export 1080p MP4"
• "generate a new edited video from"

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.

Free Generation Editing — Generate Edited Videos From Footage

This tool takes your video clips and runs AI video generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 60-second raw video clip and want to generate a new edited video from my footage with cuts and transitions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter source clips under 2 minutes yield faster and more accurate generation results.

Matching Input to Actions

User prompts referencing free generation editing, 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-generation-editing
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

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 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 → "generate a new edited video from my footage with cuts and transitions" → 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 "generate a new edited video from my footage with cuts and transitions" — 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.