Ai Video Editor Kids

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — add fun transitions, bright text titles, and background music for my kids...

0· 54·0 current·0 all-time
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The name/description (AI kids video editor) lines up with the declared requirement (NEMO_TOKEN) and the SKILL.md which describes uploading videos, session creation, SSE editing, and rendering endpoints. The declared config path (~/.config/nemovideo/) and the single env var are consistent with a client for an external video service.
Instruction Scope
Instructions remain within the scope of a cloud editor (check for token, obtain anonymous token if missing, create session, upload files, use SSE, poll render status). The skill will upload user media to an external domain (mega-api-prod.nemovideo.ai) and stream backend events; this is expected but has privacy implications. The SKILL.md instructs not to expose tokens/raw API output, which is good. There is no instruction to read unrelated system files or other env vars.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest install risk. No downloads/extracts or third-party package installs are requested.
Credentials
Only one environment variable (NEMO_TOKEN) is required and is directly used for API authentication. The skill also documents how to obtain an anonymous token if none is present. No unrelated credentials or excessive env access are requested.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. It does not instruct modifying other skills or system-wide configuration beyond using its own config path and token.
Assessment
This skill appears coherent for a cloud video editor, but it will upload your videos and metadata to an external service (mega-api-prod.nemovideo.ai). Before installing or using it, consider: (1) Do you trust the service and its privacy/retention policy for children’s content? (2) If you already have a NEMO_TOKEN in your environment, the skill will use it — avoid exposing long-lived credentials you care about. (3) The skill can obtain an anonymous token automatically (100 free credits, 7-day expiry) — you may prefer using a throwaway token or verifying the provider first. (4) Because this is an instruction-only skill from an unknown source, prefer to verify the vendor/homepage or request source code before granting access to any sensitive content. If you want, I can help draft questions to ask the provider or suggest safer alternatives (local editing tools or trusted cloud editors).

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk973yasb1hm0j5540b36vjsdas84smex
54downloads
0stars
1versions
Updated 5d ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "edit my raw video clips"
  • "export 1080p MP4"
  • "add fun transitions, bright text titles,"

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.

AI Video Editor for Kids — Edit and Export Kids Videos

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

Say you have a 2-minute school project recording and want to add fun transitions, bright text titles, and background music for my kids birthday video — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 3 minutes process fastest for young users in a hurry.

Matching Input to Actions

User prompts referencing ai video editor kids, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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

EndpointMethodPurpose
/api/tasks/me/with-session/nemo_agentPOSTStart a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_ssePOSTSend 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>POSTUpload a file (multipart) or URL.
/api/credits/balance/simpleGETCheck remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latestGETFetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambdaPOSTStart 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.

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

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

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 saysYou 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 JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

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 background music for my kids 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 background music for my kids birthday video" → 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.

Comments

Loading comments...