Free Online Video Editor

Turn a 3-minute travel vlog recorded on a smartphone into 1080p edited video clips just by typing what you need. Whether it's trimming and enhancing raw foot...

Security Scan

The skill's requirements and runtime instructions are coherent for a cloud video-editing service, but it will upload user videos and may create/use anonymous tokens so review privacy and trust in the external service before using.

Purpose & Capability

The skill's name and description (cloud video editing) align with the declared credential (NEMO_TOKEN) and the SKILL.md which talks to nemovideo.ai endpoints for uploads, sessions, and rendering. Requiring a token and calling remote render/upload endpoints is expected for this purpose.

Instruction Scope

Instructions are narrowly scoped to creating/using a session token, uploading user-supplied video files, interacting with SSE for edits, and exporting results. Important behavioral notes: the skill will automatically obtain an anonymous token (POST to /api/auth/anonymous-token) if NEMO_TOKEN is not present, and it will upload user media to mega-api-prod.nemovideo.ai for cloud processing. The agent is instructed to not 'expose tokens or raw API output', but the workflow inherently transmits user media and metadata to that external service.

Install Mechanism

Instruction-only skill with no install spec or code — nothing is written to disk or downloaded by the skill itself. This is the lowest-risk install model.

Credentials

Only one env var (NEMO_TOKEN) is declared, which matches the API's Bearer auth requirement. The skill can also create an anonymous NEMO_TOKEN via the public endpoint, so requiring a pre-existing token is not strictly necessary. The SKILL.md frontmatter also references a config path (~/.config/nemovideo/) in metadata which is not reflected in the registry summary; this is an inconsistency and could indicate the skill expects or can use a local config file, but the runtime instructions do not require reading arbitrary local files.

Persistence & Privilege

always is false and the skill is user-invocable; it doesn't request any persistent platform-level privileges. Autonomous invocation is allowed (platform default) but not combined with other high-privilege requests.

Assessment

This skill will upload any videos you send to a third-party service (mega-api-prod.nemovideo.ai) and uses a bearer token (NEMO_TOKEN). If you don't provide a token, the skill will request an anonymous token from the service and use it (100 free credits, 7-day expiry). Before installing or using: (1) confirm you trust nemovideo.ai and are comfortable uploading the specific footage (privacy/sensitivity), (2) avoid setting NEMO_TOKEN to any high-privilege or unrelated secrets, (3) check the service's privacy/retention policy for uploaded media, and (4) note the SKILL.md references a local config path (~/.config/nemovideo/) in its metadata — verify whether any local config will be read or created if you want to avoid local state. If you need stronger assurance, ask the skill author for the service privacy URL and for clarification about the local config usage.

Getting Started

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

Try saying:

• "edit a 3-minute travel vlog recorded on a smartphone into a 1080p MP4"
• "trim the slow parts, add transitions, and put text overlays on key moments"
• "trimming and enhancing raw footage for social media or YouTube for content creators and casual users"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Free Online Video Editor — Edit and Export Videos Online

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

Here's a typical use: you send a a 3-minute travel vlog recorded on a smartphone, ask for trim the slow parts, add transitions, and put text overlays on key moments, and about 1-2 minutes 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 2 minutes process significantly faster and give snappier results.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	free-online-video-editor
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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)

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

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the slow parts, add transitions, and put text overlays on key moments" — 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 slow parts, add transitions, and put text overlays on key moments" → 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.