Free Free Editing

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

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud-based video editing service, but there are a few small metadata inconsistencies and privacy considerations to review before use.

Purpose & Capability

The skill claims to perform cloud video editing and only requests a single service token (NEMO_TOKEN) which is consistent. Minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) but the registry metadata reported 'Required config paths: none'.

Instruction Scope

Runtime instructions focus on connecting to the external Nemovideo API, uploading user media, streaming SSE events, and polling for export. These actions are within scope for a cloud editing skill. The instructions also tell the agent to detect the install path and read the skill's YAML frontmatter for attribution, and to 'keep technical details out of the chat' (which reduces transparency).

Install Mechanism

No install spec or code is present (instruction-only), so nothing is written to disk by an installer — this minimizes install risk.

Credentials

The only required environment credential is NEMO_TOKEN (declared as primary), which is proportionate for a third-party editing API. Caveat: SKILL.md metadata references a local config path (~/.config/nemovideo/) not listed in the registry — if the agent actually reads that path it could expose additional locally-stored credentials or config.

Persistence & Privilege

The skill is not always-enabled and has no install-time persistence. It creates ephemeral sessions on the remote service but does not request elevated platform privileges.

Assessment

This skill appears to do what it says: it uploads your videos to an external service (mega-api-prod.nemovideo.ai) for cloud GPU editing and requires a NEMO_TOKEN (or will request an anonymous starter token). Before installing/using it: 1) Confirm you are comfortable that your media will be uploaded to that external service and review its privacy/retention policy. 2) Avoid placing highly sensitive credentials in NEMO_TOKEN unless you trust the service and understand token scopes. 3) Note the small metadata mismatch: SKILL.md mentions a local config path (~/.config/nemovideo/) — ask the maintainer whether the agent will read that path and why. 4) If you want transparency, ask the skill author to surface connection/activity logs to the user instead of 'keeping technical details out of the chat.' If you want higher assurance, test with non-sensitive sample videos and a throwaway token first.

Getting Started

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

Try saying:

• "edit a 2-minute unedited screen recording into a 1080p MP4"
• "trim the pauses, cut dead air, and smooth the transitions"
• "editing videos quickly without paid software 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.

Free Video Editing — Edit and Export Videos Free

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

Here's a typical use: you send a a 2-minute unedited screen recording, ask for trim the pauses, cut dead air, and smooth the transitions, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 3 minutes process the fastest.

Matching Input to Actions

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

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

• X-Skill-Source: free-free-editing
• 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.

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.

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

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 pauses, cut dead air, and smooth the transitions" — 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.

Common Workflows

Quick edit: Upload → "trim the pauses, cut dead air, and smooth the transitions" → 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.