Maker Best

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

Security Scan

The skill appears to be a coherent video-upload/render frontend, but several instruction details are surprising (automatic anonymous token creation, instructions to hide tokens, and ambiguous config/header behaviors) and warrant caution before use.

Purpose & Capability

The declared purpose (cloud video processing/export) maps to the single required environment variable NEMO_TOKEN and the API endpoints documented in SKILL.md, so required credentials are expected. However the metadata also declares a config path (~/.config/nemovideo/) that is not referenced elsewhere in the instructions, which is unnecessary or unclear for a pure API client.

Instruction Scope

Instructions direct the agent to upload local files or URLs to an external backend and to poll/render jobs — expected for a video service — but also instruct automatic anonymous token generation when NEMO_TOKEN is absent, explicitly tell the agent not to display raw API responses or token values to the user, and require deriving an X-Skill-Platform value from the install path. These steps give the skill discretion to (a) obtain and use credentials without explicit user-provided auth and (b) read local file paths and possibly installation paths to populate headers, which broadens data access beyond simply sending the user-selected video.

Install Mechanism

No install spec and no code files — the skill is instruction-only, so nothing is downloaded or written by an installer. This is the lowest install risk.

Credentials

Only one env var (NEMO_TOKEN) is declared which is proportional to the stated purpose. However the runtime instructions include a fallback that generates an anonymous token by POSTing to an external endpoint and then treats that token as the NEMO_TOKEN; automatic creation and use of credentials without an explicit, clear user opt-in is a material behavioral detail users should be aware of. The declared config path appears unnecessary.

Persistence & Privilege

The skill does not request always:true and makes no claim to modify other skills or persistent agent settings. Autonomous invocation is allowed by default but not a distinguishing risk here.

What to consider before installing

This skill mostly behaves like a cloud video-processing client, but be aware of three things before installing: (1) it will upload files you provide to an external service (mega-api-prod.nemovideo.ai) — do not send sensitive or private footage unless you trust that domain and service; (2) if you don't supply NEMO_TOKEN it will automatically generate an anonymous token by calling the provider API and then use and store that token for your session — consider whether you want the skill to obtain credentials on your behalf; (3) the instructions explicitly say not to show raw API responses or token values to users, which hides backend details. If you decide to proceed, test with non-sensitive files first, consider providing your own NEMO_TOKEN if you want control over credentials, and verify the service's privacy/terms outside the skill (the skill provides no homepage or published source).

Getting Started

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

Try saying:

• "create my raw video footage"
• "export 1080p MP4"
• "turn my raw clips into a"

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.

Maker Best — Create and Export Top Videos

This tool takes your raw video footage and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-minute unedited screen recording and want to turn my raw clips into a polished video with transitions and music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter source clips let the AI pick the best moments more accurately.

Matching Input to Actions

User prompts referencing maker best, 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	maker-best
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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 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 "turn my raw clips into a polished video with transitions and 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 and devices.

Common Workflows

Quick edit: Upload → "turn my raw clips into a polished video with transitions and 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.