Generation Editing Generator

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

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud-based AI video editing service: it asks for a NEMO_TOKEN (or obtains an anonymous token) and instructs streaming uploads and render requests to a nemo-video API endpoint.

Purpose & Capability

The name/description (AI video editing) align with the declared env var (NEMO_TOKEN) and the SKILL.md, which documents endpoints for uploading, session creation, SSE, rendering, and credits. Requested config path (~/.config/nemovideo/) and attribution headers are consistent with a client for a hosted video service.

Instruction Scope

The SKILL.md instructs the agent to (a) read NEMO_TOKEN from the environment, (b) obtain an anonymous token from an external API if none is present, (c) upload user-provided media to https://mega-api-prod.nemovideo.ai, and (d) stream SSE responses, create sessions, and poll render status. These actions are expected for a cloud render service, but they do mean user media and metadata will be transmitted to a third-party endpoint and the agent will perform network calls on the user's behalf.

Install Mechanism

No install spec or code files are present (instruction-only). Nothing is written to disk by an installer as part of this skill package itself, which lowers install-time risk.

Credentials

The skill declares a single primary credential (NEMO_TOKEN), which is appropriate for an API-backed editor. Metadata also references a user config path (~/.config/nemovideo/) and the agent is asked to detect its platform/install path for attribution headers; these are plausible but do require the agent to access environment/config and determine runtime paths. Users should confirm the token's provenance before sharing and avoid using with sensitive footage if unsure.

Persistence & Privilege

The skill does not request always:true or other elevated persistent privileges. Autonomous invocation is enabled (default) but that is normal for skills. The skill does not request modification of other skills or system-wide settings.

Assessment

This skill will upload your video and related metadata to a third‑party backend (mega-api-prod.nemovideo.ai) and requires an API token (NEMO_TOKEN) or the ability to request a short-lived anonymous token. Before installing or using it: (1) Confirm you trust the nemo service and the token source; avoid uploading sensitive or private footage unless you accept the service's privacy terms. (2) If you prefer control, provide your own NEMO_TOKEN from a trusted account rather than letting the skill obtain an anonymous token. (3) Understand that the agent may read environment variables and determine install/config paths to populate attribution headers — this is expected but be cautious about shared credentials in your environment. (4) Because this is instruction-only, all execution happens via network calls from the agent to the remote API (no local binary is installed). If you want stronger guarantees, ask the skill author for a privacy/terms link or a self-hosting option before use.

Getting Started

Got raw video footage to work with? Send it over and tell me what you need — I'll take care of the AI video generation editing.

Try saying:

• "generate a 2-minute raw screen recording or phone clip into a 1080p MP4"
• "generate a polished edited video from my raw footage with cuts and transitions"
• "generating edited videos from raw footage using AI for content creators and marketers"

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.

Generation Editing Generator — Generate Edited Videos from Footage

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

Say you have a 2-minute raw screen recording or phone clip and want to generate a polished edited video from my raw 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 60 seconds produce faster and more accurate generated edits.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: generation-editing-generator
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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.

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

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a polished edited video from my raw 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.

Common Workflows

Quick edit: Upload → "generate a polished edited video from my raw 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.