Video Editor Kids

Turn a 2-minute school project recording into 1080p kid-friendly edited videos just by typing what you need. Whether it's editing children's videos with fun...

Security Scan

The skill's declared behaviour (cloud video editing) aligns with its API usage and single required token, but there are small inconsistencies (undeclared config path in the skill frontmatter and instructions that read filesystem/install-paths) that warrant caution before installing or granting environment access.

Purpose & Capability

The skill's name/description match the runtime instructions: it calls a cloud video-rendering API and needs a NEMO_TOKEN for auth. Asking for a single service token is proportionate to a cloud video-editing service. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) even though the registry metadata listed no required config paths — this mismatch should be explained by the author.

Instruction Scope

Runtime instructions direct the agent to use NEMO_TOKEN or obtain an anonymous token via the service's auth endpoint, create sessions, upload user media, stream SSE, and poll render endpoints — all expected for a cloud editor. Concerningly, the instructions also tell the agent to read the skill's own YAML frontmatter and detect the agent install path (~/.clawhub/, ~/.cursor/skills/) to set X-Skill-Platform, and reference a config directory (~/.config/nemovideo/). Reading arbitrary home-directory paths or install locations expands filesystem access beyond just using an env var and should be justified. The guidance to 'keep technical details out of the chat' is a UX instruction but does not affect security directly.

Install Mechanism

No install spec or code files — instruction-only skill. This is the lowest-risk install surface because nothing is downloaded or written by an installer.

Credentials

The only declared credential is NEMO_TOKEN (primaryEnv), which is appropriate for a cloud API. However, the SKILL.md frontmatter's configPaths (~/ .config/nemovideo/) are not reflected in the registry's required config paths; if the skill attempts to read that directory it may access local credentials or cached tokens unexpectedly. The skill also instructs generating and persisting an anonymous token when none is provided — reasonable, but users should be aware that the agent will store/use that token as an environment-like credential.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It does require the normal autonomous invocation flag (default) which is standard. The skill does not request to modify other skills or system-wide settings in the provided instructions.

What to consider before installing

This skill appears to do what it says (cloud-based kids' video editing) and only asks for one service token (NEMO_TOKEN), which is reasonable — but there are a few things to check before installing or granting access: - Ask the publisher to clarify why the frontmatter lists ~/.config/nemovideo/ as a config path when the registry metadata shows none. If the skill will read that directory, verify what it contains (tokens, cached files) and whether you're comfortable exposing it. - Prefer providing a limited-scope NEMO_TOKEN or a throwaway account/token with the minimum necessary rights, not a high-privilege or shared secret. - Confirm whether the agent will persist the anonymous starter token to disk (and where) if it generates one; if so, decide whether that storage location and lifetime are acceptable. - If you want to reduce risk, run the skill in an isolated environment (separate user account or container) so its filesystem checks (install-path detection, config dir reads) cannot access unrelated credentials or sensitive files. - If the author cannot justify reading install paths or the config directory, treat that as a red flag and avoid installing until clarified. If you want, I can draft specific questions to ask the skill author or propose an isolation checklist to run the skill safely.

Getting Started

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

Try saying:

• "edit a 2-minute school project recording into a 1080p MP4"
• "add fun transitions, bright text titles, and upbeat background music for my kid's birthday video"
• "editing children's videos with fun titles, transitions, and music for parents and young students"

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 Editor for Kids — Edit and Export Kids Videos

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

Here's a typical use: you send a a 2-minute school project recording, ask for add fun transitions, bright text titles, and upbeat background music for my kid's birthday video, 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 — shorter clips under 3 minutes process fastest and work best for school projects.

Matching Input to Actions

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

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-editor-kids
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "add fun transitions, bright text titles, and upbeat background music for my kid's birthday video" — 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 school platforms and social sharing.

Common Workflows

Quick edit: Upload → "add fun transitions, bright text titles, and upbeat background music for my kid's birthday video" → 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.