In Video Free

Turn a 2-minute tutorial recording into 1080p clean edited videos just by typing what you need. Whether it's editing videos online for free without a waterma...

Security Scan

The skill's requirements and runtime instructions are generally consistent with a cloud video-editing integration: it needs a NEMO_TOKEN and calls a nemovideo.ai API to upload/process/export videos; nothing obviously unrelated is requested.

Purpose & Capability

The skill's name/description (AI video editing/export) matches the declared primary credential (NEMO_TOKEN) and the SKILL.md which documents API calls for uploads, session creation, credits, and exports. Requesting a single service token for the backend is proportionate.

Instruction Scope

Instructions are explicit about creating a session, uploading files, using SSE for edits, polling exports, and re-acquiring anonymous tokens if missing/expired. Two minor scope notes: (1) the skill asks agents to 'keep the technical details out of the chat' (a transparency preference, not a technical requirement), and (2) it describes deriving headers from YAML frontmatter and detecting an install path to set X-Skill-Platform — this implies the agent may check its environment/install path or read its own metadata, which is plausible but not strictly necessary for core editing functionality.

Install Mechanism

Instruction-only skill with no install spec or downloads; nothing is written to disk by the skill itself. Low install risk.

Credentials

Only one required env var (NEMO_TOKEN) is declared and used. SKILL.md documents fallback to acquiring an anonymous token via the service's auth endpoint if no token is provided. No unrelated credentials or wide-ranging env access are requested.

Persistence & Privilege

always:false and no requests to modify other skills or system-wide settings. The skill expects to create short-lived sessions on the backend and queue render jobs, which is appropriate for a cloud render pipeline.

Assessment

This skill will upload your video files and call a cloud API at mega-api-prod.nemovideo.ai to edit and render outputs. Before installing/using it: (1) confirm you trust the nemovideo.ai service and are comfortable uploading the videos you plan to edit (check their privacy/retention policy); (2) only provide an explicit NEMO_TOKEN if you trust the service — otherwise allow the skill to use the anonymous-token flow (limited credits and 7‑day token); (3) be aware the skill may inspect agent metadata or install paths to set headers (this is odd but not dangerous by itself); (4) ask the publisher for source code or a homepage if you need stronger assurance — there is no install code or public homepage provided here. If any of these points are unacceptable, do not enable the skill or restrict it to non-sensitive content.

Getting Started

Send me your video clips and I'll handle the free AI video editing. Or just describe what you're after.

Try saying:

• "edit a 2-minute tutorial recording into a 1080p MP4"
• "trim the intro, add text overlays, and export without watermark"
• "editing videos online for free without a watermark 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.

In Video Free — Edit and Export Videos Free

This tool takes your video clips and runs free AI video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-minute tutorial recording and want to trim the intro, add text overlays, and export without watermark — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 3 minutes process and export significantly faster.

Matching Input to Actions

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

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

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

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.

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 → "trim the intro, add text overlays, and export without watermark" → 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 "trim the intro, add text overlays, and export without watermark" — 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.