High Quality Video Maker Free

Get polished MP4 videos ready to post, without touching a single slider. Upload your video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "clea...

Security Scan

The skill's declared requirements and runtime instructions are coherent with a cloud-based video-rendering service; no disproportionate credential or install requests were found, though there are small inconsistencies to verify before installing.

Purpose & Capability

The skill claims to call a remote video-rendering API and only requests a single service token (NEMO_TOKEN) and a session. Endpoints, upload, SSE, and render flows in SKILL.md line up with a cloud video editor. Minor inconsistency: the SKILL.md YAML frontmatter lists a config path (~/.config/nemovideo/) while the registry summary reported no required config paths — this is likely benign but worth confirming.

Instruction Scope

Instructions are specific and limited to: use NEMO_TOKEN (or obtain an anonymous token via the public auth endpoint), create a session, upload user-provided media, stream SSE, poll render status, and return download URLs. These actions match the described purpose. Note: the SKILL.md also describes deriving an X-Skill-Platform header from install-path detection (e.g., ~/.clawhub/), which implies the runtime might inspect its install location; that behavior is plausible but not necessary for core functionality and is somewhat vague in an instruction-only skill.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is written to disk by the skill itself. This is the lowest-risk install pattern.

Credentials

Only one credential (NEMO_TOKEN) is required, which is appropriate for authenticating to the described backend. The SKILL.md's anonymous-token fallback (POST to /api/auth/anonymous-token) is consistent with allowing operation without a pre-provisioned key. Users should note that any token (anonymous or not) grants access to upload and render operations on the remote service.

Persistence & Privilege

The skill does not request always:true, does not modify other skills, and has no install-time persistence. Session tokens are used transiently for jobs; no elevated or permanent system privileges are requested.

Assessment

This skill will upload your video/audio files to a third-party rendering service (mega-api-prod.nemovideo.ai) and requires a service token (NEMO_TOKEN) or will obtain an anonymous token for you. Before installing, confirm the service domain and privacy policy, and avoid uploading sensitive or private footage you wouldn't want processed off-device. Verify the small metadata mismatch (SKILL.md lists a ~/.config/nemovideo/ path while the registry showed no required config paths) and confirm where tokens are stored and how long anonymous tokens remain valid. If you care about provenance, ask the publisher for their homepage or privacy terms before use.

Getting Started

Send me your video clips and I'll handle the AI video enhancement. Or just describe what you're after.

Try saying:

• "create a 2-minute raw smartphone recording into a 1080p MP4"
• "clean up the footage, add transitions, and export in 1080p"
• "turning raw clips into professional-looking videos without paid software for content creators and small business owners"

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.

High Quality Video Maker Free — Create and Export HD Videos

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

A quick example: upload a 2-minute raw smartphone recording, type "clean up the footage, add transitions, and export in 1080p", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: keeping clips under 3 minutes speeds up processing significantly.

Matching Input to Actions

User prompts referencing high quality video maker free, 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 high-quality-video-maker-free, 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).

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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

Common Workflows

Quick edit: Upload → "clean up the footage, add transitions, and export in 1080p" → 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 "clean up the footage, add transitions, and export in 1080p" — 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 best balance of quality and file size.