Video Maker Free Apps

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

Security Scan

The skill's runtime instructions and required token are coherent with a cloud video-rendering service, but provenance is unknown, there are metadata inconsistencies (declared config path in SKILL.md vs registry), and some header/install-path requirements are odd — you should verify the backend and privacy before installing.

Purpose & Capability

The skill claims to create/export videos and its instructions call a remote rendering API and upload user media, which is consistent with the stated purpose. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) that the registry metadata did not list, and the skill has no listed homepage or source repository — lacking provenance. These inconsistencies don't prove malice but reduce trust.

Instruction Scope

Runtime instructions are narrowly focused on establishing a session, uploading files, polling render status, and handling SSE. They do not instruct reading arbitrary system files or unrelated environment variables. Minor concerns: the agent is asked to 'auto-detect' an install path for X-Skill-Platform header (ambiguous for instruction-only skill), and instructions to 'keep technical details out of the chat' could obscure useful audit info.

Install Mechanism

There is no install spec and no code files; this is an instruction-only skill. That minimizes on-disk risk because nothing is downloaded or executed locally by the skill itself.

Credentials

Only a single credential (NEMO_TOKEN) is declared as required, which is proportionate for a remote video service. The SKILL.md also instructs obtaining an anonymous token if none is present. Still, requiring a token means user files will be uploaded to an external service; consider whether that is acceptable for the content you plan to submit.

Persistence & Privilege

The skill does not request always:true, has no install steps, and does not ask to modify other skills or system-wide configs. Autonomous invocation is allowed (default) but not by itself a concern here.

What to consider before installing

This skill behaves like a normal cloud video-renderer: it will upload your photos/videos to mega-api-prod.nemovideo.ai and use a NEMO_TOKEN (or create an anonymous token) to process them. Before installing or using it: 1) Verify the provider (there's no homepage or repo listed) — ask the publisher for documentation or a privacy policy. 2) Don’t upload sensitive/private media unless you trust the service and its retention policy. 3) Note the SKILL.md frontmatter mentions a local config path (~/.config/nemovideo/) even though the registry didn't — ask whether the skill will read local config files. 4) If you must proceed, use an ephemeral/limited token or anonymous flow and avoid sharing sensitive content until you confirm the service's terms. If the publisher can't clarify provenance and data policies, treat this skill as higher-risk.

Getting Started

Ready when you are. Drop your video clips or images here or describe what you want to make.

Try saying:

• "create five product photos and a background music file into a 1080p MP4"
• "combine these photos into a 30-second video with transitions and text overlays"
• "creating short videos from photos or clips without paid software for casual 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.

Video Maker Free Apps — Create and Export Videos Free

Drop your video clips or images in the chat and tell me what you need. I'll handle the AI video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a five product photos and a background music file, ask for combine these photos into a 30-second video with transitions and text overlays, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — using shorter clips under 60 seconds speeds up processing significantly.

Matching Input to Actions

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

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the 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 these photos into a 30-second video with transitions and text overlays" → Download MP4. Takes 30-60 seconds 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 these photos into a 30-second video with transitions and text overlays" — 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 social platforms and devices.