Ai Video Editor For Davinci

Get edited video files ready to post, without touching a single slider. Upload your raw footage (MP4, MOV, AVI, MKV, up to 500MB), say something like "cut th...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-based AI video editor: it asks for a single service token, uploads user video to a vendor API, and runs session/export workflows — nothing requested appears unrelated to the stated purpose, but source is unknown so exercise caution.

Purpose & Capability

Name and description describe a cloud AI video editing service. The only credential requested is NEMO_TOKEN and the SKILL.md documents endpoints for uploads, SSE chat, session creation, and export — all directly tied to remote video processing.

Instruction Scope

Instructions direct the agent to obtain/use NEMO_TOKEN (or generate an anonymous one), create a session, upload media, follow SSE for edits, poll status, and return a download URL. Those actions are expected for a cloud render service. The skill requires uploading user media to mega-api-prod.nemovideo.ai (privacy/host trust consideration). It does not instruct reading unrelated system files or other credentials, and it explicitly says not to print tokens/raw JSON.

Install Mechanism

No install spec or code files are present (instruction-only). That minimizes on-disk install risk; runtime network calls are the primary surface.

Credentials

Only NEMO_TOKEN is declared as required (primaryEnv). The SKILL frontmatter also lists a config path (~/.config/nemovideo/) which is coherent for storing tokens/session state, but the registry summary earlier said 'required config paths: none' — minor metadata inconsistency. No unrelated credentials are requested.

Persistence & Privilege

always is false and the skill does not request elevated or global privileges. It may store tokens/session info under its own config path, which is normal. Autonomous invocation is enabled by default (platform default) but is not combined with other red flags.

Assessment

This skill behaves like a cloud video editor: it will upload your video files to mega-api-prod.nemovideo.ai and use a NEMO_TOKEN to authenticate (or create a short-lived anonymous token). Before installing, consider: (1) Do you trust the vendor/domain? Videos you upload will leave your machine. (2) Provide only non-sensitive footage; do not upload private or regulated content without review. (3) The skill may store token/session data in ~/.config/nemovideo/ — verify and audit that directory if you use the skill. (4) The package/source is marked unknown and has no homepage; if you need higher assurance, ask the publisher for provenance or prefer an editor with a verifiable vendor and documented privacy policy. Finally, note a minor metadata mismatch: the SKILL frontmatter lists a config path while the registry summary said none — this is likely benign but worth verifying.

Getting Started

Got raw footage to work with? Send it over and tell me what you need — I'll take care of the AI-assisted video editing.

Try saying:

• "edit a 3-minute DaVinci Resolve project export into a 4K MP4"
• "cut the dead air, add color grading, and sync transitions to the beat"
• "AI-assisted editing for DaVinci Resolve users who want faster post-production for video editors and filmmakers"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

AI Video Editor for DaVinci — Edit and Export DaVinci Videos

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

Say you have a 3-minute DaVinci Resolve project export and want to cut the dead air, add color grading, and sync transitions to the beat — the backend processes it in about 1-2 minutes and hands you a 4K MP4.

Tip: export your DaVinci timeline as a flat MP4 first for the smoothest processing.

Matching Input to Actions

User prompts referencing ai video editor for davinci, 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	ai-video-editor-for-davinci
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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)

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.

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

Common Workflows

Quick edit: Upload → "cut the dead air, add color grading, and sync transitions to the beat" → 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 "cut the dead air, add color grading, and sync transitions to the beat" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, MKV for the smoothest experience.

H.264 codec gives the best balance of quality and file size for uploads.