Editor Generation Generator

generate raw video footage into auto-edited videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for automatical...

Security Scan

The skill's stated purpose (auto-editing videos) mostly matches its instructions, but there are inconsistent/deeper claims about accessing a local config path and a few minor mismatches that merit caution before installation.

Purpose & Capability

Name/description, declared required env var (NEMO_TOKEN), and the runtime instructions all describe a video-editing API backend — this is coherent. However, the SKILL.md frontmatter requests a config path (~/.config/nemovideo/) while the registry metadata at the top lists no required config paths; that mismatch is unexplained and suggests the skill may try to read local config files that are not necessary for a simple API client.

Instruction Scope

Instructions instruct the agent to use NEMO_TOKEN if present or obtain an anonymous token by POSTing to the public nemo API (network calls expected). They also direct the agent to read the skill's YAML frontmatter at runtime and to detect install paths on disk (e.g., ~/.clawhub/, ~/.cursor/skills/) to set attribution headers. Reading install paths and (potentially) ~/.config/nemovideo/ expands scope beyond pure API calls and could expose local configuration or secrets if present.

Install Mechanism

No install spec or code files are present; this is instruction-only. That minimizes on-disk persistence and installation risk.

Credentials

The single required env var (NEMO_TOKEN) is appropriate for a backend service. But the SKILL.md implies reading a local config directory (~/.config/nemovideo/) which could contain credentials or other sensitive data; that access is not justified by the stated purpose and conflicts with the declared registry requirements. The skill also offers to obtain an anonymous token via the public API if no token exists, which is reasonable but means the skill will perform network auth flows autonomously.

Persistence & Privilege

always:false and no install means the skill won't be force-included or persistently installed. However, the skill is allowed to be invoked autonomously (default), and combined with the instruction to read local paths/configs, that increases potential blast radius if the agent runs the skill without user oversight.

What to consider before installing

This skill appears to legitimately integrate with a NemoVideo API and needs a NEMO_TOKEN, which is expected. Before installing: 1) Confirm whether the skill really needs access to your ~/.config/nemovideo/ directory (the registry metadata and the SKILL.md disagree). If you have sensitive files or credentials there, avoid granting access. 2) Understand that if no NEMO_TOKEN is present the skill will call the public API to obtain an anonymous token (network activity). 3) Because the skill may check local install paths and config, consider running it in a restricted environment or denying access to local config directories until you verify the backend (the skill's source/homepage is missing). 4) If you need higher assurance, ask the publisher for source code or a trustworthy homepage and clarification about why local config access is required.

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 editor generation.

Try saying:

• "generate a 2-minute unedited screen recording into a 1080p MP4"
• "generate a fully edited version with cuts, transitions, and titles"
• "automatically generating edited videos from raw footage for content creators"

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.

Editor Generation Generator — Generate Edited Videos Automatically

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

Say you have a 2-minute unedited screen recording and want to generate a fully edited version with cuts, transitions, and titles — 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 focused edits.

Matching Input to Actions

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

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

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

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

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.

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

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.

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)

Common Workflows

Quick edit: Upload → "generate a fully edited version with cuts, transitions, and titles" → 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 fully edited version with cuts, transitions, and titles" — 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.