Ai Video Editor App Download

edit raw video footage into edited MP4 clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and casual users use it for...

Security Scan

The skill's declared purpose (cloud video editing) matches most of its runtime instructions, but there are inconsistencies (declared config paths vs registry metadata) and clear privacy/safety implications (automatic token creation and uploading user videos to an external service) that you should understand before installing.

Purpose & Capability

The skill claims to perform cloud video editing and asks only for a single API token (NEMO_TOKEN) which is appropriate for that purpose. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that the registry metadata did not declare; this mismatch is unexplained and could indicate either sloppy metadata or an unadvertised need to access user config files.

Instruction Scope

The instructions tell the agent to (a) check the environment for NEMO_TOKEN or else acquire an anonymous token by POSTing to a remote endpoint, (b) maintain session_id for subsequent calls, (c) upload user video files (either by file path or URL) to the remote API, and (d) inspect installation paths (~/.clawhub/, ~/.cursor/skills/) to set an attribution header. Uploading user media to a third-party endpoint and probing home-directory paths are significant actions that go beyond simple local editing helpers and should be explicit to the user. The SKILL.md also instructs reading its own YAML frontmatter and detecting install paths — these imply filesystem reads that are not declared elsewhere.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing will be downloaded or written to disk by an install step. That lowers supply-chain risk compared to installers or external archives.

Credentials

The single required env var NEMO_TOKEN is proportionate to a cloud service integration. However, the SKILL.md frontmatter also declares a configPaths value (~/.config/nemovideo/) while the registry metadata lists no required config paths — an inconsistency. The skill also instructs creating and using anonymous tokens automatically, which is functional but means the agent will call remote auth endpoints and hold bearer tokens in memory; users should confirm they are comfortable with that token being used for uploads.

Persistence & Privilege

The skill is not marked always:true and does not request privileged persistent presence. It does instruct the agent to hold session_id for the duration of a session, but it does not mandate writing tokens or sessions to disk. Autonomous invocation is allowed by default and is not in itself a problem here.

What to consider before installing

This skill will upload any video you send to a third-party service (mega-api-prod.nemovideo.ai) and will automatically obtain and use an anonymous bearer token if you don't supply NEMO_TOKEN. Before installing or using it: (1) confirm you trust that external service and its privacy/retention policy for your videos; (2) prefer supplying an ephemeral or dedicated token rather than a credential used elsewhere; (3) ask the publisher to explain the apparent mismatch about required config paths (~/.config/nemovideo/ listed in the skill but not in registry metadata) and why the skill probes install paths in your home directory; (4) avoid sending sensitive footage until you're satisfied with those answers. If you cannot verify the service owner or privacy terms, treat this skill with caution.

Getting Started

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

Try saying:

• "edit a 2-minute smartphone recording into a 1080p MP4"
• "trim the weak parts, add transitions, and export a clean final cut"
• "editing raw footage into polished videos without desktop software 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.

AI Video Editor App Download — Edit and Export Videos Online

Send me your raw video footage 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 smartphone recording, type "trim the weak parts, add transitions, and export a clean final cut", 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 process significantly faster.

Matching Input to Actions

User prompts referencing ai video editor app download, 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.

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

• X-Skill-Source: ai-video-editor-app-download
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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

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

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 the weak parts, add transitions, and export a clean final cut" — 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 weak parts, add transitions, and export a clean final cut" → 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.