Free Editing Generator

Get edited video clips ready to post, without touching a single slider. Upload your raw video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "t...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-based video editing service: it asks only for a single service token and instructs calls to a single API host for uploads, editing, and exports.

Purpose & Capability

Name/description (automatic video editing) match the declared requirements and runtime instructions. The skill only requires a NEMO_TOKEN and references a nemo-specific config path (~/.config/nemovideo/), both of which are plausible for a hosted video-processing backend.

Instruction Scope

SKILL.md instructs the agent to obtain or use a NEMO_TOKEN, create a session, upload files, stream SSE edits, poll export status, and include attribution headers read from the skill's frontmatter and install path. These actions stay within the stated purpose. Two scope notes: (1) the skill asks the agent to detect its install path and read this file's YAML frontmatter at runtime — that requires reading skill-local filesystem metadata (acceptable if limited to the skill bundle, but verify it does not read unrelated system files), and (2) the skill will send any uploaded media to mega-api-prod.nemovideo.ai, so any media the user supplies is transmitted off-device to that service.

Install Mechanism

There is no install spec and no code files — instruction-only skills are lower risk because nothing is downloaded or written by the skill at install time.

Credentials

Only one environment variable is required (NEMO_TOKEN), which is appropriate for a third-party API. The SKILL.md also describes creating an anonymous token when the variable is absent; no unrelated credentials (AWS, GitHub, etc.) are requested.

Persistence & Privilege

The skill is not always-enabled and does not request system-wide configuration changes. It does instruct storing the session_id for subsequent API calls (normal for session-based services) but does not ask to modify other skills or global agent settings.

Assessment

This skill appears to do what it says: it uploads your video clips to a remote service (mega-api-prod.nemovideo.ai) for cloud editing and returns a download URL. Before installing or using it, confirm you trust that remote service and avoid uploading sensitive or private footage. Note the skill can create an anonymous NEMO_TOKEN automatically if none is provided — that token grants the service access to any files you upload. If you require stronger privacy guarantees, ask the skill owner for a privacy/retention policy or use a local/offline editing tool instead.

Getting Started

Ready when you are. Drop your raw video clips here or describe what you want to make.

Try saying:

• "edit a 2-minute unedited phone recording into a 1080p MP4"
• "trim the pauses, add transitions, and export a clean final cut"
• "automatically editing raw footage into a polished video without manual effort for content creators and social media users"

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 Editing Generator — Edit and Export Polished Videos

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

A quick example: upload a 2-minute unedited phone recording, type "trim the pauses, add transitions, and export a clean final cut", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

User prompts referencing free 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: free-editing-generator
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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.

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

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 → "trim the pauses, add transitions, and export a clean final cut" → 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 "trim the pauses, add transitions, and export a clean final cut" — 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 all platforms.