Video Maker In Free

create images or clips into finished MP4 videos with this skill. Works with MP4, MOV, JPG, PNG files up to 500MB. content creators and small business owners...

Security Scan

The skill's declared purpose (cloud-based video creation) matches its runtime instructions and required credential (NEMO_TOKEN); it will contact a single external backend to obtain tokens, create sessions, upload media, and retrieve rendered videos, which is coherent with its stated functionality but has some minor metadata and privacy/operational notes you should review before installing.

Purpose & Capability

The skill name/description match the required credential (NEMO_TOKEN) and the described API endpoints for uploading, rendering, and downloading video. Minor inconsistency: the registry metadata you provided lists no required config paths, but the SKILL.md frontmatter declares a configPaths entry (~/.config/nemovideo/). This mismatch is small but worth noting.

Instruction Scope

SKILL.md instructions stay within the video-rendering scope: checking for NEMO_TOKEN, obtaining an anonymous token from the provider if absent, creating a session, uploading files, using SSE for interactive commands, and polling for export results. It does instruct detecting install path (~/.clawhub/, ~/.cursor/skills/) to populate an X-Skill-Platform header, which requires reading the agent's filesystem layout; otherwise, it does not direct the agent to read unrelated files or extra environment variables.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk by an installer. This is the lowest-risk install pattern and consistent with the skill type.

Credentials

Only NEMO_TOKEN is declared as required. The SKILL.md explains how to obtain an anonymous NEMO_TOKEN via the provider's auth endpoint if not present (100 free credits, 7-day expiry). That behavior is coherent with the purpose, but it does mean the skill will contact an external service to mint a credential automatically if the environment lacks one — consider whether you want the agent to obtain/store such tokens for you. The SKILL.md's configPaths entry may imply writing configuration under ~/.config/nemovideo/.

Persistence & Privilege

The skill is not always-on and does not request system-wide privileges or modification of other skills. It only asks to hold a session_id for active operations (ephemeral). Autonomous invocation is enabled (normal), but there is no evidence of persistent privileged behavior beyond potential local config storage under the declared config path.

Assessment

This skill appears internally consistent for a cloud video-rendering integration, but before installing consider: 1) Source and provenance are unknown (no homepage), so verify you trust the domain mega-api-prod.nemovideo.ai before sending media. 2) The skill will, if no NEMO_TOKEN is present, call the provider to mint an anonymous token and then upload files to their backend — do not use sensitive or private videos unless you trust their service and privacy policy. 3) The SKILL.md mentions a config path (~/.config/nemovideo/) and will detect install paths to populate headers; check where (and whether) tokens or session IDs would be stored on disk. 4) If you need to limit network actions, disable autonomous invocation or run the skill in a sandbox and test with non-sensitive sample files first. If you want more confidence, ask the owner for a homepage or source code, or request explicit details about token persistence and data retention from the service operator.

Getting Started

Got images or clips to work with? Send it over and tell me what you need — I'll take care of the AI video creation.

Try saying:

• "create five product photos and a logo file into a 1080p MP4"
• "turn my photos into a 30-second promo video with music and text"
• "creating videos from photos or clips without paid software for content creators and small business owners"

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.

Video Maker in Free — Create and Export Videos Free

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

Say you have five product photos and a logo file and want to turn my photos into a 30-second promo video with music and text — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: using fewer than 10 images speeds up generation noticeably.

Matching Input to Actions

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

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

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

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.

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

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

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.

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 → "turn my photos into a 30-second promo video with music and text" → 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 "turn my photos into a 30-second promo video with music and text" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, JPG, PNG for the smoothest experience.

Export as MP4 for widest compatibility across platforms and devices.