Simple Video Generator Cartoon

generate text or images into animated cartoon videos with this skill. Works with JPG, PNG, MP4, GIF files up to 200MB. educators, content creators, parents u...

Security Scan

The skill's instructions, required credential, and runtime steps are coherent with a cloud video-rendering integration, but some minor inconsistencies and unknown provenance merit caution before installation.

Purpose & Capability

Name/description and required credential (NEMO_TOKEN) align with a cloud video-generation service. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — this mismatch should be clarified. The skill's source/homepage is also missing, reducing traceability.

Instruction Scope

Runtime instructions are focused on contacting the nemovideo API (auth, session, SSE, uploads, render) and handling returned data; they do not ask to read unrelated system files. One instruction asks to 'auto-detect' X-Skill-Platform from an install path, which could require probing the agent's install or filesystem paths — that is outside pure network I/O and should be clarified. The skill also instructs saving session_id/token state but doesn't define storage boundaries.

Install Mechanism

Instruction-only skill with no install steps or downloaded code, so nothing is written to disk by an installer. This is the lowest-risk install mechanism.

Credentials

The single required env var (NEMO_TOKEN) is proportional for a service needing bearer auth. Still, the frontmatter's config path (~/.config/nemovideo/) implies potential local config access; registry metadata omitted config paths, so the reason for that path should be explained. Users should treat NEMO_TOKEN as sensitive (gives access/credits).

Persistence & Privilege

The skill is not always-enabled, does not request elevated platform privileges, and is instruction-only. Autonomous invocation is allowed (platform default) but not combined with additional privileges here.

Assessment

This skill appears to do what it says (remote cartoon-video generation) and only asks for one credential (NEMO_TOKEN). Before installing: 1) Note the skill has no listed homepage or source—verify the service domain (mega-api-prod.nemovideo.ai) and the vendor independently if possible. 2) Prefer generating an anonymous/ephemeral token (the SKILL.md describes an anonymous-token flow) instead of storing a long-lived NEMO_TOKEN in your environment. 3) Ask the author to clarify the config-path mention (~/.config/nemovideo/) and the 'auto-detect install path' behavior so you know whether the agent will read local filesystem paths. 4) Treat uploaded media as sent to a third-party cloud GPU service—don’t upload sensitive content without checking the provider’s privacy/retention policy. 5) If you must set NEMO_TOKEN, restrict its scope/permissions and be prepared to revoke it after testing.

Getting Started

Share your text or images and I'll get started on cartoon video generation. Or just tell me what you're thinking.

Try saying:

• "generate my text or images"
• "export 1080p MP4"
• "turn my story idea into a"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Simple Video Generator Cartoon — Generate Cartoon Videos from Text

Send me your text or images and describe the result you want. The cartoon video generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a short story prompt or three character sketches, type "turn my story idea into a 30-second cartoon video with animated characters", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter scripts under 60 words produce cleaner cartoon animations.

Matching Input to Actions

User prompts referencing simple video generator cartoon, 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	simple-video-generator-cartoon
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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 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 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 "turn my story idea into a 30-second cartoon video with animated characters" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "turn my story idea into a 30-second cartoon video with animated characters" → 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.