Editor De Video Con Ia

edit raw video footage into edited video clips with this editor-de-video-con-ia skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and...

Security Scan

The skill's declared requirements and runtime instructions are generally consistent with an AI cloud video-editing integration; there are minor metadata inconsistencies and a small scope creep around platform/install-path detection that you should be aware of before use.

Purpose & Capability

The skill is an instruction-only AI video editor and asks only for a NEMO_TOKEN (or to obtain an anonymous token) which is appropriate for a backend video-editing service. Minor inconsistencies: the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) in metadata, while the registry summary listed no required config paths; the user-facing description lists support for MP4/MOV/AVI/WebM up to 500MB but the API docs inside the SKILL.md list additional formats (mkv, many image/audio types). These are small mismatches but not evidence of malicious intent.

Instruction Scope

Instructions focus on authenticating, creating sessions, uploading videos, streaming SSE, and polling render status — all expected for a cloud render/editor. They also instruct deriving attribution headers from the skill YAML and detecting the install path to populate X-Skill-Platform, which requires the agent to inspect the runtime/install path (a minor scope creep). The instructions do not direct the agent to read unrelated user files or system secrets beyond the token flows described.

Install Mechanism

No install spec or code is present (instruction-only). Nothing will be downloaded or written to disk by the skill itself as provided here.

Credentials

The only declared required credential is NEMO_TOKEN (primaryEnv), which is proportional for a third-party API. The SKILL.md will generate an anonymous token if none is present, avoiding the need for other credentials. The earlier-mentioned metadata config path (~/.config/nemovideo/) is inconsistent with the registry's 'no required config paths' — if present, that would imply reading/writing a local config, which should be confirmed before installing.

Persistence & Privilege

The skill is not marked always:true and does not request unusual persistent privileges. It creates short-lived sessions with the remote API (normal for this use) and does not attempt to modify other skills or global agent settings.

Assessment

This skill appears to be a straightforward cloud-based video editor that uses a single token (NEMO_TOKEN) or an anonymous token from https://mega-api-prod.nemovideo.ai. Before installing or using it: (1) confirm you trust the nemo video service domain and its privacy policy (you will upload video content to that service); (2) avoid sending sensitive or private video content until you verify the provider; (3) note the SKILL.md may inspect the agent's install path to set an X-Skill-Platform header — if you are concerned about leaking local path/platform info, ask for that behavior to be removed or clarified; (4) verify whether a local config (~/.config/nemovideo/) will be read/written, since registry metadata and SKILL.md differ on this point; and (5) because this is instruction-only, no code will be installed on your machine by the skill itself, but network calls will occur to the listed API endpoints.

Getting Started

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

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "recorta las partes silenciosas, agrega transiciones"

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.

Editor de Video con IA — Edit and Export Videos with AI

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

Say you have a 2-minute smartphone recording and want to recorta las partes silenciosas, agrega transiciones y subtítulos en español — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: clips under 3 minutes process significantly faster.

Matching Input to Actions

User prompts referencing editor de video con ia, 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 requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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

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.

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 → "recorta las partes silenciosas, agrega transiciones y subtítulos en español" → 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 "recorta las partes silenciosas, agrega transiciones y subtítulos en español" — 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.