Video Maker Hd Free

create video clips into polished HD videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for assembling and edit...

Security Scan

The skill's requirements and runtime instructions are generally consistent with a cloud-based video rendering service, but there are small metadata/instruction mismatches and a few privacy considerations you should review before installing.

Purpose & Capability

Requiring a single service token (NEMO_TOKEN) and using cloud endpoints for uploads/exports is coherent with a video-rendering service. However, the skill's frontmatter metadata references a config path (~/.config/nemovideo/) that is not listed in the registry's required config paths, which is an internal inconsistency worth noting.

Instruction Scope

The SKILL.md focuses on uploading user media and interacting with the remote API (session creation, SSE, uploads, render polling) — this matches the stated purpose. It also instructs the agent to read the local YAML frontmatter and detect install path (~/.clawhub/, ~/.cursor/skills/) to set attribution headers. Checking those install paths and reading frontmatter is outside pure video-processing logic (attribution-only) and is scope-expanding; it requires filesystem access in the user's home directory.

Install Mechanism

No install script or remote code download is present (instruction-only). This is low-risk from an installation/execution perspective because nothing is written to disk by an install step.

Credentials

Only one credential (NEMO_TOKEN) is required, which aligns with a remote API service. The skill will generate an anonymous token via the service API if no token is present. Be aware the skill's metadata references a config path where tokens or config might reside — that suggests the agent may look for local credentials.

Persistence & Privilege

The skill does not request always:true and does not modify other skills or system-wide settings. It uses ephemeral session tokens for jobs and appears not to request permanent system presence.

Assessment

This skill appears to be a straightforward wrapper around a cloud video-rendering API and only requests one credential (NEMO_TOKEN). Before installing: (1) Understand that your uploaded videos and metadata will be sent to https://mega-api-prod.nemovideo.ai — review that service's privacy/terms if you care about sensitive content. (2) The skill may examine your home directories (for install-path detection and possibly ~/.config/nemovideo/) to set attribution headers — if you don't want local filesystem checks, avoid installing or run in a restricted environment. (3) Only put a NEMO_TOKEN into the agent environment if you trust the service; anonymous tokens are issued automatically but are short-lived. (4) Note the small metadata inconsistency (config path present in skill frontmatter but not in registry fields); this looks like sloppy packaging rather than malicious behavior. If you need higher assurance, ask the publisher for source code or a privacy policy and confirm precisely what local paths the skill will read.

Getting Started

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

Try saying:

• "create my video clips"
• "export 1080p MP4"
• "combine my clips into one HD"

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.

Video Maker HD Free — Create and Export HD Videos

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

Say you have three 30-second raw phone clips and want to combine my clips into one HD video with transitions and background music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: keeping individual clips under 2 minutes speeds up processing significantly.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: video-maker-hd-free
• 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.

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

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 → "combine my clips into one HD video with transitions and background 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "combine my clips into one HD video with transitions and background 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.