Generator Editing Generator

Skip the learning curve of professional editing software. Describe what you want — re-edit the generated video to reorder scenes and adjust pacing — and get...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud-based video re-editing service: it needs a single service token, calls a specific API, and has no install-time code to run locally.

Purpose & Capability

The name/description describe cloud video re-editing and the SKILL.md only requires a NEMO_TOKEN and interaction with nemovideo.ai endpoints — these are consistent with the stated purpose (uploading videos, creating sessions, SSE for edits, and exporting). No unrelated credentials or binaries are requested.

Instruction Scope

Instructions are focused on session creation, SSE messaging, uploads, exports, polling, and presenting backend events to the user. They also instruct reading the skill frontmatter and detecting install path (~/.clawhub, ~/.cursor) and mention a local config path (~/.config/nemovideo/). Reading those local paths is reasonable for attribution but is notable because it requires filesystem access.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is downloaded or written by an installer. This minimizes install-time risk.

Credentials

Only one required environment variable (NEMO_TOKEN) is declared and used as the bearer token for the service; this is proportional. Minor inconsistency: the top-level metadata in the registry reported no required config paths, while the SKILL.md frontmatter lists a config path (~/.config/nemovideo/). That mismatch should be verified but does not itself indicate extra credential access.

Persistence & Privilege

The skill is not marked always:true and does not request elevated platform privileges. It does create sessions and polls job status on the remote service, but it does not request or claim to modify other skills or global agent configuration.

Assessment

This skill uploads user video files to a remote service (mega-api-prod.nemovideo.ai) and requires a NEMO_TOKEN bearer token to operate. If you do not provide a token the skill will request an anonymous token from the service and use it for operations (the token is time-limited per the docs). Before installing: 1) Confirm you trust nemovideo.ai and understand their privacy/retention policy for uploaded media. 2) Recognize that providing NEMO_TOKEN grants the skill full API access to that account — treat it like any other service credential. 3) Note the skill may read local paths (~/.config/nemovideo/ and install-paths) for attribution; if you have sensitive data in those locations, verify what will be read. 4) There is a small metadata mismatch about required config paths between the registry summary and the SKILL.md frontmatter — you may want to confirm which is authoritative. Overall the skill appears internally consistent for a cloud video re-editing integration, but only install if you trust the remote service and are comfortable uploading your media.

Getting Started

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

Try saying:

• "edit my AI-generated video clips"
• "export 1080p MP4"
• "re-edit the generated video to reorder"

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.

Generator Editing Generator — Edit and Re-Export Generated Videos

Send me your AI-generated video clips and describe the result you want. The AI generator re-editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 60-second AI-generated product video, type "re-edit the generated video to reorder scenes and adjust pacing", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter generated clips re-render faster — split long videos before editing.

Matching Input to Actions

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

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

• X-Skill-Source: generator-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.

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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.

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 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)

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 → "re-edit the generated video to reorder scenes and adjust pacing" → Download MP4. Takes 30-60 seconds 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 "re-edit the generated video to reorder scenes and adjust pacing" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, WebM, AVI for the smoothest experience.

Export as MP4 for widest compatibility.