Ai Video Editor India

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

Security Scan

The skill appears to do what it says (cloud video editing) and only requests a single service token, but there are small metadata inconsistencies and privacy implications (your videos are uploaded to a third-party backend) you should be aware of before installing.

Purpose & Capability

The declared purpose (cloud video editing) aligns with the runtime instructions (upload, session creation, render/export endpoints). The skill requires/uses a NEMO_TOKEN which is appropriate for a cloud service. Minor incoherence: registry metadata above listed no required config paths, but the SKILL.md frontmatter lists a config path (~/.config/nemovideo/). This mismatch should be clarified by the publisher.

Instruction Scope

SKILL.md explicitly instructs the agent to upload user video files and interact with the nemovideo.ai API (session creation, SSE, render endpoints). Those actions match the described editing task. The instructions do not ask for unrelated files or other credentials. Note: it requires sending user media to an external service and derives a platform header by inspecting install paths (~/.clawhub/, ~/.cursor/skills/), which implies the agent may check filesystem/install-location.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an install script. That is lower risk.

Credentials

Only NEMO_TOKEN is required (primary credential), which is proportionate for an API-backed editor. The SKILL.md provides a fallback flow to obtain an anonymous token via https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token if NEMO_TOKEN is absent — this is consistent but means the agent will call that API automatically and receive a short-lived token. The earlier mismatch about config path metadata is again noted.

Persistence & Privilege

The skill is not always-enabled and does not request persistent system modifications. It does not claim to change other skills or system-wide agent settings.

Assessment

This skill sends your video files and instructions to a third-party backend (mega-api-prod.nemovideo.ai) for processing. If you install it, expect uploads of any media you give it and that the agent may auto-request a short-lived anonymous token if NEMO_TOKEN is not present. Before installing: (1) confirm you trust the nemovideo.ai service and its privacy/retention policy for potentially sensitive footage; (2) prefer supplying your own NEMO_TOKEN if you have a paid/account-controlled token rather than relying on anonymous tokens; (3) ask the publisher to explain the metadata mismatch around config paths (~/.config/nemovideo/) and to provide a homepage or source link; (4) avoid uploading sensitive personal or regulated content until you verify the backend's policies.

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"
• "trim the best moments, add Hindi"

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 India — Edit and Export Videos Online

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 wedding clip shot on an Android phone and want to trim the best moments, add Hindi captions, and export for Instagram Reels — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process fastest — split long videos before uploading.

Matching Input to Actions

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

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

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.

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)

Common Workflows

Quick edit: Upload → "trim the best moments, add Hindi captions, and export for Instagram Reels" → 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 "trim the best moments, add Hindi captions, and export for Instagram Reels" — 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 WhatsApp, YouTube, and Instagram.