Best Video Edit

Skip the learning curve of professional editing software. Describe what you want — trim the pauses, add transitions, and sync background music — and get poli...

Security Scan

The skill's behavior mostly matches a cloud video-editing tool, but there are coherence issues (missing source/homepage, inconsistent config-path declaration) and it will generate/store tokens and send user videos to an external API — review before installing.

Purpose & Capability

The name/description align with calls to an external video-editing API (uploading footage, creating render jobs, exporting). Required credential NEMO_TOKEN and the listed endpoints are coherent with a cloud render backend. However, the skill source is unknown and there is no homepage or publisher info, which reduces transparency. The SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) while the registry metadata above reported no required config paths — this inconsistency should be resolved.

Instruction Scope

Runtime instructions stay within the editing workflow (create session, SSE for edits, upload files, poll render status). They explicitly instruct generating an anonymous token when NEMO_TOKEN is not present and to 'store the returned session_id' and to avoid showing raw API responses or token values to the user. Those behaviors are reasonable for a cloud service but warrant attention because they mean the agent will contact an external domain and persist tokens/sessions (storage location unspecified). The instructions do not ask the agent to read unrelated system files, but the frontmatter's config path reference is not otherwise used in SKILL.md.

Install Mechanism

No install spec or code files are present; this is instruction-only, so nothing will be written to disk by an installer. That minimizes installation risk.

Credentials

Only one credential (NEMO_TOKEN) is declared as required and is appropriate for a third-party editing API. The skill will generate an anonymous token via the service if none is provided, which is acceptable but means the agent will silently obtain and store credentials. The frontmatter's mention of a config path (~/.config/nemovideo/) is inconsistent with the registry summary and not justified by the instructions — a potential mismatch to clarify.

Persistence & Privilege

always:false and normal autonomous invocation are used. The skill instructs storing session_id and token values for subsequent API calls (expected for sessions), but it does not request elevated or system-wide privileges or modify other skills. The persistence/scope of stored tokens (in-memory vs. on-disk) is unspecified and should be confirmed.

What to consider before installing

This skill will upload your video files to a third-party service (mega-api-prod.nemovideo.ai), obtain and store API/session tokens, and include hidden headers on each request. That is consistent with cloud editing but has privacy implications: confirm you are comfortable sending raw footage to an external provider. Also note: there is no visible source code or homepage and the SKILL.md frontmatter references a config path (~/.config/nemovideo/) that isn't otherwise used — ask the publisher to clarify where tokens/sessions are stored, provide a privacy/security policy, and confirm the domain is legitimate before installing. If you need stronger assurance, request the skill's source or prefer a skill from a known publisher. If you plan to use private or sensitive footage, do not install until you verify data retention and access policies with the provider.

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 pauses, add transitions, and"

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.

Best Video Edit — Edit and Export Polished Videos

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 unedited phone recording and want to trim the pauses, add transitions, and sync background music — 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 best video edit, 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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	best-video-edit
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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.

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

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 → "trim the pauses, add transitions, and sync background music" → 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 pauses, add transitions, and sync background music" — 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.