Free Nemo Video

Turn a 2-minute MP4 recorded on a smartphone into 1080p edited MP4 videos just by typing what you need. Whether it's editing and exporting videos at no cost...

Security Scan

The skill's requirements and runtime instructions are generally consistent with a cloud video-editing integration, but there are a few minor inconsistencies and privacy-relevant behaviors you should understand before use.

Purpose & Capability

Name/description match the instructions: the skill uploads user video clips to a NemoVideo cloud API, creates sessions, queues render jobs, and returns download URLs. Requesting a NEMO_TOKEN credential is appropriate for authenticating to that API. However, the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) while the registry metadata listed no required config paths — this is an inconsistency worth confirming with the author.

Instruction Scope

Instructions are explicit about network calls (anonymous-token endpoint, session creation, upload, SSE, render/polling). They also instruct the agent to derive attribution headers from the YAML frontmatter and to detect an install path (checking locations like ~/.clawhub/ or ~/.cursor/skills/). Detecting install path / reading the frontmatter implies the agent may read local filesystem paths beyond just the declared env var; this is not strictly necessary for core editing functionality and is scope creep you may want clarified.

Install Mechanism

No install spec and no code files are present (instruction-only). This minimizes on-disk risk — the skill performs actions via API calls rather than installing binaries or downloading archives.

Credentials

The skill declares a single primary credential (NEMO_TOKEN), which fits a cloud editing service. The runtime also supports creating an anonymous token by POSTing to the service if NEMO_TOKEN is absent. No other unrelated credentials are requested. That said, the SKILL.md's implicit request to read install paths or config files (per frontmatter) could result in accessing local files beyond just reading the NEMO_TOKEN env var; confirm whether local config access is necessary.

Persistence & Privilege

The skill is not marked always:true and does not request system-wide persistence or to modify other skills. It may create short-lived session tokens with the remote service (tokens last ~7 days), but there is no instruction to permanently store credentials on disk.

Assessment

This skill appears to do what it says (cloud-based video editing) and only requests one credential (NEMO_TOKEN). Before installing or using it, consider: 1) Privacy — your videos will be uploaded to https://mega-api-prod.nemovideo.ai; only upload content you are comfortable sending to a third party. 2) Verify origin — source/homepage is unknown; confirm the provider and read its privacy/terms. 3) Token handling — if you don't have a NEMO_TOKEN the skill will request an anonymous token from the service; that gives the service access to any uploaded videos for the token lifetime (about 7 days). 4) Filesystem access — the SKILL.md suggests detecting install paths and reading YAML frontmatter; ask the author why that is needed and whether it can be avoided. 5) Minimize risk — prefer using an anonymous account or disposable token, avoid placing long-lived secrets in shared environment variables, and do not upload sensitive private content unless you trust the service. If you need higher assurance, request the skill author provide a homepage, privacy policy, or source repository to verify the backend and behavior.

Getting Started

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

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "trim, add transitions, and export this"

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 Nemo Video — Edit and Export Videos Free

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

Say you have a 2-minute MP4 recorded on a smartphone and want to trim, add transitions, and export this video for free — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process and export faster on the free tier.

Matching Input to Actions

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

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

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim, add transitions, and export this video for free" — 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, add transitions, and export this video for free" → 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.