Editor Ai Professional

Turn a 3-minute interview recording into 1080p polished edited videos just by typing what you need. Whether it's turning raw footage into professionally edit...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-based video editing service and mostly proportionate, with a few minor inconsistencies and small scope-creep items you should be aware of before installing.

Purpose & Capability

Name/description (AI video editing) match the declared runtime actions: session creation, upload, SSE-based editing, render/export and downloading a URL. Requesting a single service token (NEMO_TOKEN) is expected for that backend.

Instruction Scope

SKILL.md instructs the agent to create sessions, upload user video files, stream SSE messages, poll render status, and return download URLs — all aligned with the stated editing purpose. However it also asks the agent to detect install path (e.g., ~/.clawhub/ or ~/.cursor/skills/) to set an X-Skill-Platform header, which requires reading local filesystem/install location; and it embeds a config path (~/.config/nemovideo/) in the YAML frontmatter. These filesystem reads are not strictly necessary for editing and widen the agent's runtime access.

Install Mechanism

Instruction-only skill with no install spec or downloaded code, which minimizes install-time risk. No external package downloads or archive extraction are requested.

Credentials

Only one credential is declared (NEMO_TOKEN), which is appropriate. The instructions also provide a fallback anonymous-token flow (POST to the service to get a limited token). Minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) even though the registry metadata showed no required config paths — this should be clarified because it implies the agent may read that directory.

Persistence & Privilege

Skill is not always-enabled and does not request elevated platform-wide privileges. It does not instruct modifying other skills or system settings. Autonomous invocation is enabled (default) but that is expected for skills and not by itself a concern.

Assessment

This skill looks like a legitimate remote video-editing integration: it uploads your video to mega-api-prod.nemovideo.ai, runs edits on their GPU nodes, and returns a download URL. Before installing: (1) decide whether you want to provide a permanent NEMO_TOKEN — if you do not trust the service, prefer using the anonymous-token fallback or avoid supplying a permanent token; (2) confirm you are comfortable with your video files being sent to the external API and review the service's privacy/deletion policy; (3) be aware the skill may try to read/install-paths (e.g., ~/.clawhub, ~/.cursor/skills, ~/.config/nemovideo/) to populate X-Skill-Platform headers — if you do not want the agent to inspect your filesystem, do not install or restrict its file access; (4) ask the skill author to clarify the mismatch between the registry metadata and the SKILL.md frontmatter (configPaths) so you understand exactly what local paths it will access. If you need higher assurance, request that the author remove filesystem detection or document exactly which paths will be read.

Getting Started

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

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "cut the pauses, balance the audio,"

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.

AI Editor Professional — Edit and Export Professional Videos

Send me your raw video footage and describe the result you want. The AI professional editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 3-minute interview recording, type "cut the pauses, balance the audio, and add lower-third titles", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: clips under 5 minutes process significantly faster and yield more precise AI cuts.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: editor-ai-professional
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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.

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.

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)

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 pauses, balance the audio, and add lower-third titles" → 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, balance the audio, and add lower-third titles" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the best balance of quality and file size.