Free Generator Editor

Skip the learning curve of professional editing software. Describe what you want — generate a video from my images and edit it with transitions and music — a...

Security Scan

The skill largely matches a cloud video-editing purpose, but there are several inconsistencies and surprising behaviors (token auto-provisioning, mismatched config-path metadata, automatic backend connection and platform-detection via install path) that warrant caution before installing.

Purpose & Capability

The described purpose (cloud-based video generation/editing) aligns with the HTTP endpoints and operations in SKILL.md. Requesting a NEMO_TOKEN is reasonable for this service. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — an internal inconsistency. Also the skill declares NEMO_TOKEN as required but includes a fallback flow that auto-obtains an anonymous token if none is present; that mismatch between 'required' and implemented behavior should be clarified.

Instruction Scope

The runtime instructions direct the agent to automatically connect to the remote backend on first use, to POST for an anonymous token if NEMO_TOKEN is not set, to upload user media (up to 500MB), to poll and handle SSE streams, and to persist a session_id for subsequent requests. These actions are consistent with a cloud editor but are non-trivial: they involve network calls and uploading user files to a third-party domain (mega-api-prod.nemovideo.ai). The instructions also say to detect the install path to set X-Skill-Platform, which implies reading local paths/install location — this is a scope creep relative to a purely API-facing skill and is not declared in top-level metadata.

Install Mechanism

No install spec or code files are included (instruction-only). That means nothing is downloaded or written during install, which lowers supply-chain risk. The runtime behavior still performs network operations, but there is no installer to evaluate.

Credentials

Only one credential (NEMO_TOKEN) is declared which is proportionate for a third-party API. However, SKILL.md will request an anonymous token via an API if NEMO_TOKEN is absent, meaning the skill will make network calls and create a bearer token automatically. The frontmatter also references a configPath (~/.config/nemovideo/) and requires reading an install path to set a header — these are additional local data accesses that were not listed in the registry's required config paths and should be explained.

Persistence & Privilege

always:false (not force-included) and disable-model-invocation is false (normal). The skill's instructions to 'connect automatically on first open' means it will perform network activity without an explicit user action beyond opening the skill; combined with its ability to obtain tokens automatically, this could be surprising. It does not request to modify other skills or system-wide configs.

What to consider before installing

Before installing or using this skill, consider the following: - Domain and origin: the skill talks to mega-api-prod.nemovideo.ai. Verify that this domain is a legitimate service you trust and review its privacy/data retention policy before uploading media. - Automatic token creation: the skill will POST to an anonymous-token endpoint to create a bearer token if NEMO_TOKEN isn't set. If you want control over credentials, set NEMO_TOKEN yourself rather than relying on anonymous provisioning. - File uploads: the skill uploads your media (up to 500MB) to a third-party server. Do not upload sensitive or confidential footage unless you accept external processing and storage risks. - Metadata inconsistency: the SKILL.md frontmatter references a config path (~/.config/nemovideo/) and asks the agent to detect install paths to set headers, but the registry metadata does not list these paths. Ask the publisher to clarify why local path inspection is necessary and what exactly is read or stored. - Automatic network activity: the skill will try to connect automatically on first use and may be invoked autonomously. If you want to avoid unexpected outbound traffic, do not enable autonomous invocation or only invoke the skill manually. - Transparency: there is no homepage or publisher info beyond an owner id. Prefer skills with a visible author, homepage, or privacy policy. Ask the owner to provide clear documentation about token handling, data retention, and what is stored locally vs. remotely. If you plan to proceed, set a dedicated NEMO_TOKEN (or a throwaway account), avoid uploading sensitive content, and request clarification about the configPath/install-path requirements from the skill author.

Getting Started

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

Try saying:

• "generate my video clips or images"
• "export 1080p MP4"
• "generate a video from my images"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Free Generator Editor — Generate and Edit Videos Free

Drop your video clips or images in the chat and tell me what you need. I'll handle the AI video generation editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 60-second raw screen recording or a set of product images, ask for generate a video from my images and edit it with transitions and music, and about 30-90 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter input clips and fewer images generate faster results.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is free-generator-editor, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a video from my images and edit it with transitions and music" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across all platforms.

Common Workflows

Quick edit: Upload → "generate a video from my images and edit it with transitions and music" → Download MP4. Takes 30-90 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.