Best Video Maker

create raw footage into polished MP4 videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for turning raw clips...

Security Scan

The skill's instructions generally match a cloud video-rendering capability, but there are inconsistencies (missing source/homepage, discrepant config-path declarations) and it will upload your files and use or mint a service token — you should verify the service and privacy implications before installing.

Purpose & Capability

The name/description (cloud video editing → MP4 exports) aligns with the API endpoints and upload/render workflow described in SKILL.md. Requesting a single service token (NEMO_TOKEN) is plausible for this purpose. However, the registry metadata earlier said 'required config paths: none' while the skill frontmatter references '~/.config/nemovideo/' — a minor inconsistency. Also the package has no source/homepage, which reduces ability to verify the service.

Instruction Scope

SKILL.md instructs the agent to: read NEMO_TOKEN from environment (if present), or generate an anonymous client UUID and POST to an external auth endpoint to obtain a token; create a session; upload user files (multipart) to the remote API; start renders and poll SSE or status endpoints. These actions are exactly what a cloud-rendering skill would do, but they involve transmitting user media and session metadata to a third-party domain (mega-api-prod.nemovideo.ai). The instructions also require including specific attribution headers on every request. No other unrelated files or env vars are read, but the file upload/exfiltration risk is inherent and must be expected by users.

Install Mechanism

This is instruction-only with no install spec and no code files, so nothing is written to disk by an installer. That is the lowest install risk; however, runtime network activity (API calls, uploads, SSE) is still required.

Credentials

The skill declares a single credential, NEMO_TOKEN (primaryEnv), which is proportionate for a cloud service. It also documents an anonymous-token fallback flow that the agent will call if no token is present. No unrelated secrets are requested. The SKILL.md frontmatter adds a config path (~/.config/nemovideo/) that the registry metadata did not list — this discrepancy is unexplained but not necessarily malicious.

Persistence & Privilege

always is false and the skill is user-invocable; model invocation is enabled (default). This is expected for a skill that needs to call remote APIs. There is no request to modify other skills or system-wide settings.

What to consider before installing

This skill appears to implement a legitimate cloud video-rendering workflow, but you should be cautious before installing: 1) The skill will upload any media you provide to mega-api-prod.nemovideo.ai (a third party). Do not send sensitive or private footage unless you trust the service and its privacy terms. 2) The package has no listed source or homepage — ask the publisher for a privacy policy, terms of service, and a way to verify the service identity. 3) The skill reads NEMO_TOKEN from the environment (and will mint an anonymous token if none exists); prefer using a limited-scope or expendable token if you must provide credentials. 4) Confirm the '~/.config/nemovideo/' config path referenced in the skill frontmatter is required and harmless (registry metadata omitted it). 5) Because this is instruction-only, there's no code to audit; if you need greater assurance, request an official homepage, public repo, or documentation and test with non-sensitive files first. If you proceed, monitor usage and rotate any tokens you provide.

Getting Started

Ready when you are. Drop your raw footage here or describe what you want to make.

Try saying:

• "create a 2-minute smartphone recording into a 1080p MP4"
• "cut the best moments, add background music, and export as a shareable video"
• "turning raw clips into finished, shareable videos for content creators"

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.

Best Video Maker — Create and Export Finished Videos

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

A quick example: upload a 2-minute smartphone recording, type "cut the best moments, add background music, and export as a shareable video", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter source clips under 60 seconds process significantly faster.

Matching Input to Actions

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

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

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

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

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the best moments, add background music, and export as a shareable video" — 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 and devices.

Common Workflows

Quick edit: Upload → "cut the best moments, add background music, and export as a shareable video" → 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.