Ai Video Editor Dhurandhar

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

Security Scan

The skill's declared purpose (cloud video editing) matches most of its instructions, but there are several inconsistencies and privacy/credential-handling behaviors that warrant caution before installing.

Purpose & Capability

The skill is an instruction-only wrapper for a remote video-processing API and legitimately needs a service token (NEMO_TOKEN). That aligns with the description. Minor inconsistency: the registry metadata provided to you lists no configPaths, while the SKILL.md metadata references ~/.config/nemovideo/ (potential mismatch between registry record and runtime instructions).

Instruction Scope

Runtime instructions stay focused on uploading video and calling the nemo video API. They do instruct the agent to check environment variables and derive headers (X-Skill-Platform) based on local install paths (e.g. inspecting ~/.clawhub/ or ~/.cursor/skills/), which implies the agent will read the filesystem to infer platform. The skill also instructs automatic anonymous token creation and explicit guidance to "Don't display raw API responses or token values to the user," which hides credential values from users and may reduce transparency.

Install Mechanism

No install spec and no code files — instruction-only skill. Low install risk because nothing is downloaded or written by an installer, though runtime behavior can still access files and network.

Credentials

Only a single credential (NEMO_TOKEN) is requested, which is proportionate to a remote editing API. However, the skill will auto-generate an anonymous token when none is present and store/use it; combined with the instruction to avoid displaying raw tokens to the user, this creates a lack of visibility about where tokens/sessions are stored and how to revoke them. The SKILL.md also references a config path (~/.config/nemovideo/) not declared in the registry, which could be used to persist data.

Persistence & Privilege

always is false and the skill does not request elevated or cross-skill system modifications. It asks the agent to store session_id/token for use during the session — expected for an API-backed service. No evidence it modifies other skills or system-wide settings.

What to consider before installing

What to consider before installing: 1) Privacy: all uploaded videos are sent to https://mega-api-prod.nemovideo.ai — if your footage contains sensitive material, do not upload until you confirm retention, sharing, and deletion policies. 2) Credentials & transparency: the skill will create and store an anonymous NEMO_TOKEN automatically if none is present and instructs the agent not to show raw token values — ask where tokens and session IDs are stored, how you can list/revoke them, and how long they are valid. 3) Filesystem access: the skill derives an X-Skill-Platform header by checking typical install paths (~/.clawhub/, ~/.cursor/skills/) and references ~/.config/nemovideo/ in its metadata — confirm whether the agent will read/write these paths and what gets stored. 4) Provenance & trust: there is no homepage or source repo and the owner ID is unknown; consider this an unvetted service. 5) Testing advice: try it first with non-sensitive, small test videos and ask the maintainer (or request more metadata) about retention, encryption in transit/storage, and token lifecycle before sending real content. If you cannot verify those answers, treat the skill as higher-risk and avoid uploading sensitive material.

Getting Started

Ready when you are. Drop your raw video footage here or describe what you want to make.

Try saying:

• "edit a 2-minute raw interview recording into a 1080p MP4"
• "trim the footage, add transitions, and export a clean final cut"
• "editing raw video footage into polished final cuts for content creators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

AI Video Editor Dhurandhar — Edit and Export Polished Videos

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 raw interview recording, type "trim the footage, 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 3 minutes process significantly faster.

Matching Input to Actions

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

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.

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 footage, 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.

Common Workflows

Quick edit: Upload → "trim the footage, 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.