Video Maker Free For Kids

create images or clips into kid-friendly videos with this skill. Works with MP4, MOV, JPG, PNG files up to 200MB. kids and parents use it for creating simple...

Security Scan

The skill's declared purpose (cloud video creation for kids) matches most runtime instructions, but there are multiple mismatches and vague directives (config path metadata vs registry, required env var vs auto-generation, and platform detection that implies reading local install paths) that make the package internally inconsistent and worth caution.

Purpose & Capability

The skill claims to produce kid-friendly videos via a Nemo backend and the SKILL.md describes exactly that API surface (upload, SSE, render). Requesting a NEMO_TOKEN for the backend is expected. However, the registry metadata said no required config paths while the SKILL.md frontmatter declares ~/.config/nemovideo/ in metadata — an inconsistency between declared requirements and the instructions.

Instruction Scope

Instructions are mostly limited to contacting the external Nemo API, uploading user media, and polling for renders, which is coherent with the stated purpose. Concerns: SKILL.md instructs detecting an install path to set an X-Skill-Platform header (implies reading system paths), and it instructs automatic anonymous-token acquisition if NEMO_TOKEN is not present. The file also tells the agent not to display raw API responses or token values to the user, which is unusual and reduces transparency.

Install Mechanism

This is instruction-only with no install spec and no bundled code, so nothing is written to disk by an installer. That minimizes install-time risk.

Credentials

The skill declares a single primary credential (NEMO_TOKEN) which is appropriate for a cloud video API. But SKILL.md will auto-generate and use an anonymous token when NEMO_TOKEN is absent, meaning the token is optional in practice; the registry's 'required env vars' claim and the runtime behavior are inconsistent. The frontmatter's configPaths (~/.config/nemovideo/) is also declared even though registry metadata listed none, suggesting unclear expectations about accessing local config.

Persistence & Privilege

always:false and normal autonomous invocation; the skill does not request permanent platform-wide privileges. It asks to store session_id for subsequent requests (expected). There is no instruction to modify other skills or system-wide configs.

What to consider before installing

This skill will upload your files to mega-api-prod.nemovideo.ai and uses a Nemo token (NEMO_TOKEN). Before installing or using it, consider: 1) The publisher/source is unknown and there's no homepage or code to audit — you can't verify the backend or privacy policy. 2) The skill will either use an existing NEMO_TOKEN or automatically request an anonymous token from the remote service; it also instructs not to show raw tokens or API responses, which reduces transparency. 3) The SKILL.md references a local config path and install-path detection (to set an X-Skill-Platform header) even though registry metadata omitted that — this inconsistency could mean the agent will read local paths or metadata; decide if you're comfortable with that. 4) All user media (children's drawings, audio, etc.) will be transferred to an external cloud service — consider privacy and parental consent. 5) If you need to proceed, prefer providing your own token only if you trust the backend, and avoid using sensitive personal data. If possible, ask the publisher for a homepage/privacy policy, clarification about why local config paths are needed, and for a clear statement about whether any data is retained by the backend and for how long.

Getting Started

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

Try saying:

• "create five drawings or cartoon images from a school project into a 720p MP4"
• "turn my drawings into a fun animated story video with music and text"
• "creating simple story or school project videos from images for kids and parents"

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.

Video Maker Free for Kids — Create Fun Kids Videos Free

Drop your images or clips 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 drawings or cartoon images from a school project, ask for turn my drawings into a fun animated story video with music and text, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 720p by default.

One thing worth knowing — using bright, clear images gives the best results for kid-style videos.

Matching Input to Actions

User prompts referencing video maker free for kids, 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-free-for-kids, 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 drawings into a fun animated story video with music and text" → 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 "turn my drawings into a fun animated story video with music and text" — concrete instructions get better results.

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

Export as MP4 for easy sharing on school platforms and YouTube Kids.