Video Maker Free Export

Turn a 2-minute product demo clip into 1080p exported MP4 videos just by typing what you need. Whether it's editing and exporting finished videos without a p...

Security Scan

The skill's requests and runtime instructions are consistent with a remote video-editing service: it asks for a single service token, uploads user media, and calls the documented API endpoints—no unrelated credentials or installers are required.

Purpose & Capability

Name/description (remote AI video editing and export) align with required NEMO_TOKEN and the API endpoints described in SKILL.md. Requesting a single service token is reasonable for this purpose; accepted file types and render endpoints match the stated functionality.

Instruction Scope

SKILL.md instructs the agent to upload user video/audio files, create an anonymous token if NEMO_TOKEN is missing, open sessions, stream SSE, poll render status, and return download URLs. These actions are within the expected scope for a remote render/editing service. One operational note: the skill auto-generates and stores session_id/token for subsequent calls (ephemeral session management) — the doc says not to display raw tokens, which is appropriate. The instructions also reference detecting an install path and mapping GUI instructions; reading the install path or a config dir is plausible but not strictly required for core functionality.

Install Mechanism

No install spec or code files are present; this instruction-only skill performs network calls at runtime only. No downloads, package installs, or archive extraction are requested.

Credentials

Only one required environment variable (NEMO_TOKEN) is declared and used, which matches the remote API authentication pattern. Minor inconsistency: the registry metadata listed no required config paths, but the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/). Reading that config path or detecting install paths is plausible (to detect platform/attribution headers) but should be justified to the user.

Persistence & Privilege

always:false and autonomous invocation allowed (default). The skill instructs storing an anonymous token and session_id for the session lifecycle; this is typical and appears ephemeral. The skill does not request system-wide privileges or modification of other skills.

Assessment

This skill appears coherent for a remote video-editing service, but before installing consider: 1) You will upload video/audio files to a third-party endpoint (https://mega-api-prod.nemovideo.ai). Do not send sensitive or private content unless you trust the service and reviewed its privacy/retention terms. 2) The skill will create and store an anonymous token (NEMO_TOKEN) if you don't provide one; that token grants the skill ability to create sessions and start renders for ~7 days—treat it like a short-lived credential. 3) There is a minor metadata mismatch (SKILL.md references ~/.config/nemovideo/ and install-path detection) — if you prefer, supply your own NEMO_TOKEN rather than allowing the skill to auto-provision one. 4) If you need stronger guarantees about data deletion, retention, or where the GPUs are hosted, check the vendor/policy for mega-api-prod.nemovideo.ai before using. If those concerns are acceptable, the skill is internally consistent with its stated purpose.

Getting Started

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

Try saying:

• "edit a 2-minute product demo clip into a 1080p MP4"
• "trim the footage, add music, and export as a free MP4 download"
• "editing and exporting finished videos without a paid subscription for content creators"

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.

Video Maker Free Export — Edit and Export Videos Free

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

A quick example: upload a 2-minute product demo clip, type "trim the footage, add music, and export as a free MP4 download", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds export fastest and are less likely to hit free tier limits.

Matching Input to Actions

User prompts referencing video maker free export, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-maker-free-export, 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.

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

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.

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 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 "trim the footage, add music, and export as a free MP4 download" — 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 platforms and devices.

Common Workflows

Quick edit: Upload → "trim the footage, add music, and export as a free MP4 download" → 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.