Video Editor Openai

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

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based video-editing integration (it asks for an API token, uploads video, starts render jobs, and polls for results), but it calls an external API of unknown provenance and will transmit user video to that service — verify the provider before sending sensitive footage.

Purpose & Capability

Name/description (AI video editing) align with the actual instructions: the SKILL.md describes uploading video, creating a session, sending SSE edit commands, and exporting MP4 via a nemo-video REST API. The single required env var (NEMO_TOKEN) and the declared config path (~/.config/nemovideo/) are relevant to the described backend service.

Instruction Scope

Most instructions stay inside the stated purpose (upload, edit, export, check credits/state). The file instructs the agent to: generate an anonymous token via an external endpoint if NEMO_TOKEN is absent; save session_id and token for the session; and detect an install path (~/.clawhub/ or ~/.cursor/skills/) to populate an X-Skill-Platform header. Detecting install paths requires reading local filesystem paths (minor scope creep) but is plausibly for attribution headers. The skill does not instruct reading unrelated credentials, shell history, or arbitrary files.

Install Mechanism

Instruction-only skill with no install spec and no code files. Nothing is written to disk by the skill itself in the install phase (lowest install risk).

Credentials

Only one credential is required: NEMO_TOKEN (declared as primaryEnv). The SKILL.md also documents how to obtain an anonymous token via the service API and implies storing it for the session. This is proportionate to a cloud-rendering integration, but it means the skill will either use an existing token you provide or obtain and use one it creates — both result in outbound authenticated requests to the external service.

Persistence & Privilege

always:false and default invocation settings are used. The skill asks the agent to store session_id/token for the editing session (normal session state), and it does not request persistent platform-wide privileges or modify other skills' configs.

Assessment

This skill appears coherent for a cloud video-editor: it will upload whatever video you give it to mega-api-prod.nemovideo.ai and use a NEMO_TOKEN (either one you provide or an anonymous token it requests) to run render jobs. Before installing/using: 1) Confirm you trust the nemovideo.ai service and read its privacy/terms — your raw video files will be transmitted off your machine. 2) If you have sensitive footage, do not upload it until you verify retention, deletion, and access policies. 3) Consider providing your own NEMO_TOKEN from an account you control instead of relying on an anonymous token. 4) Be aware the skill may read basic local paths (~/.clawhub or ~/.cursor/skills/) to set a header — this is low-risk but worth noting. 5) Test first with non-sensitive short clips. If you need higher confidence, ask the skill author for a homepage, privacy policy, or official SDK/docs for nemo-video prior to use.

Getting Started

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

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "cut the pauses, add background music,"

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.

Video Editor OpenAI — Edit Videos with AI Assistance

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

Say you have a 2-minute unedited screen recording and want to cut the pauses, add background music, and export as a clean MP4 — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

User prompts referencing video editor openai, 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 video-editor-openai, 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 JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

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 → "cut the pauses, add background music, and export as a clean MP4" → 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 pauses, add background music, and export as a clean MP4" — 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.