Best Video

create raw video footage into polished MP4 videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and marketers use it fo...

Security Scan

The skill is a coherent wrapper for a cloud video-processing service: it asks for a single service token and its runtime instructions match the described purpose, but there are minor inconsistencies and privacy implications you should review before installing.

Purpose & Capability

The name/description match the behavior in SKILL.md: the skill sends user video files to a remote GPU-backed API and returns edited MP4s. Requesting a NEMO_TOKEN for the backend is proportional. One small inconsistency: registry metadata listed no config paths, but the SKILL.md frontmatter references ~/.config/nemovideo/ (possible discrepancy about where data is stored).

Instruction Scope

The instructions are focused on the video service (auth, session creation, SSE messaging, file upload, export polling). They also instruct the agent to auto-connect on first use and to generate an anonymous token if NEMO_TOKEN is absent. The skill reads its own frontmatter and may read install paths to set an attribution header — this requires filesystem access but is limited in scope. Be aware: the skill will upload user files to an external endpoint and store session identifiers for subsequent requests.

Install Mechanism

Instruction-only skill with no install spec or downloaded code — low filesystem/install risk. Nothing is written by an installer step in the package itself, but the runtime may create local session/config files (see config path note).

Credentials

Only NEMO_TOKEN is declared as required, which is appropriate for a remote service. The skill can also obtain an anonymous token via an API call if NEMO_TOKEN is missing; that behavior is documented. The frontmatter's configPaths (~/.config/nemovideo/) implies local storage of tokens/sessions which is not reflected in the registry metadata — verify where and how tokens/session IDs are stored and protected.

Persistence & Privilege

The skill is not set always:true and is user-invocable. It requests to persist session state (session_id) for ongoing jobs, which is reasonable for a cloud render workflow. Autonomous invocation is allowed but not unusual; no excessive persistent privileges are requested.

Assessment

This skill will upload your video files (up to 500MB) to an external service (mega-api-prod.nemovideo.ai) for processing and will include an Authorization token on each request. If you don't provide a NEMO_TOKEN, the skill will automatically request an anonymous token and store session state — check where (~/.config/nemovideo/) it might save tokens or session IDs and how to delete/revoke them. Only install if you trust the remote service and are comfortable with your media being sent off-device. If you want tighter control, supply your own NEMO_TOKEN, avoid uploading sensitive or private content, and confirm the service's privacy/retention policy. Note the small metadata mismatch (registry says no config paths but SKILL.md mentions one); ask the publisher to clarify storage location and retention before installing.

Getting Started

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

Try saying:

• "create my raw video footage"
• "export 1080p MP4"
• "clean up this video and make"

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 — Create and Export Polished Videos

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

A quick example: upload a 2-minute unedited screen recording, type "clean up this video and make it look professional with smooth cuts and balanced audio", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process significantly faster and give more precise AI results.

Matching Input to Actions

User prompts referencing best video, 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: best-video
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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.

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.

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 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)

Error Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "clean up this video and make it look professional with smooth cuts and balanced audio" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the widest platform compatibility.

Common Workflows

Quick edit: Upload → "clean up this video and make it look professional with smooth cuts and balanced audio" → 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.