Best Editor

edit raw video footage into polished edited clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. YouTubers and content creators use it fo...

Security Scan

The skill's high-level purpose (cloud video editing) matches the network calls and single credential it uses, but there are metadata inconsistencies and a few behavioral details (automatic anonymous token creation, implicit filesystem-derived headers, and automatic uploads to an external API) that warrant caution before installing.

Purpose & Capability

The skill claims to perform cloud video editing and its SKILL.md instructs calls to a nemo-video cloud API and upload endpoints — that aligns with the stated purpose. However, the registry listing and the skill's own YAML disagree about config paths (registry said none; the SKILL.md frontmatter includes ~/.config/nemovideo/) and the skill declares NEMO_TOKEN as required even though the runtime instructions show a fallback anonymous-token flow. These inconsistencies should be clarified.

Instruction Scope

Instructions explicitly direct the agent to upload user-supplied media to https://mega-api-prod.nemovideo.ai, create sessions, stream SSE messages, poll render status, and include attribution headers (derived from the skill frontmatter and install path). Uploading media and posting to the vendor API is expected for this service, but the skill also instructs automatic anonymous token creation when NEMO_TOKEN is absent (i.e., it will call out to an external auth endpoint and obtain credentials on the fly). The skill therefore will perform network calls and transmit user files to an external service; confirm you consent to that before use.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That is the lower-risk option for installation mechanics.

Credentials

The skill declares a single primary credential (NEMO_TOKEN), which is appropriate for a cloud editing backend. But the registry marked NEMO_TOKEN as required while the SKILL.md provides a clear anonymous-token fallback flow — meaning the registry's required-credential designation may be inaccurate or overstated. The YAML also references a config path (~/.config/nemovideo/) that the registry listing did not surface; this mismatch in declared vs. actual required config/resources is a proportionality/inventory concern that should be corrected.

Persistence & Privilege

The skill does not request always:true, has no install scripts, and does not write persistent system-wide config as part of an installer. It will create ephemeral sessions and tokens with the backend, which is expected for its function.

What to consider before installing

What to know before installing: - This skill uploads your videos to an external cloud service (mega-api-prod.nemovideo.ai). If your footage is sensitive, do not use it until you confirm the provider and their privacy terms. - The skill declares NEMO_TOKEN as a required credential but will automatically obtain an anonymous token if none is present; clarify whether you must supply your own token (for billable/registered use) or whether anonymous use is allowed. - There is a metadata mismatch: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that the registry summary did not. Ask the publisher to clarify required files/paths and whether the skill will read any local config. - The skill derives attribution headers from the agent's install path (it may read its own install location). That is normal for attribution but worth knowing. - Recommendation: Verify the service domain (mega-api-prod.nemovideo.ai) and the vendor's homepage/terms/privacy. If you plan to use paid account features, supply your own NEMO_TOKEN rather than relying on anonymous tokens. Refuse installation or avoid uploading sensitive content until these inconsistencies are clarified. What would change this assessment: if the registry metadata is corrected (NEMO_TOKEN marked optional when anonymous tokens are allowed, or configPaths consistently declared) and the provider domain and privacy policy are verified as reputable, this would move the assessment toward benign.

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"
• "cut the dead air, add transitions,"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Best Editor — 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 3-minute unedited camera recording and want to cut the dead air, add transitions, and balance the audio — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 2 minutes process significantly faster and use fewer credits.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is best-editor, 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).

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

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

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 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 dead air, add transitions, and balance the 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the dead air, add transitions, and balance the 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.