Free Video Generator Cartoon

generate text or images into animated cartoon videos with this skill. Works with PNG, JPG, MP4, GIF files up to 200MB. students, educators, social media crea...

Security Scan

The skill's behavior mostly matches its description (it talks to an external nemoVideo API using a NEMO_TOKEN) but there are metadata inconsistencies and privacy/persistence concerns you should understand before installing.

Purpose & Capability

The name/description (generate cartoon videos) align with the runtime instructions (endpoints for upload, render, credits). Requesting a NEMO_TOKEN is consistent with a third-party API integration. However, the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/) while the registry metadata listed no required config paths — this mismatch is unexplained.

Instruction Scope

The SKILL.md instructs the agent to obtain or use a bearer token, create sessions, upload user files (up to 200MB) and call multiple external endpoints (including an anonymous-token endpoint). These actions are within the expected scope for a cloud rendering service, but they involve sending user content and session tokens to an external domain (mega-api-prod.nemovideo.ai), so privacy and data-exfiltration risk should be considered.

Install Mechanism

Instruction-only skill with no install spec or code files — nothing is downloaded or written by an installer step. That reduces the risk of arbitrary code being installed by the skill itself.

Credentials

Only one credential (NEMO_TOKEN) is required, which is proportional for an API-backed video service. But the skill also describes a mechanism to mint anonymous tokens (client-side UUID → POST) and requires that bearer token for exports — treat that token as sensitive. The earlier-noted configPaths reference suggests potential local storage of session or token data that wasn't declared in the registry metadata.

Persistence & Privilege

always:false (normal). The SKILL.md instructs saving session_id and the frontmatter references a config path (~/.config/nemovideo/), implying the agent may persist session state locally; the registry metadata not listing config paths is inconsistent. The skill does not request force-inclusion or elevated privileges, but potential local persistence of tokens/session IDs should be confirmed.

What to consider before installing

This skill appears to be a straightforward connector to an external service (mega-api-prod.nemovideo.ai) and only asks for a single API token, but before installing consider the following: - Trust & provenance: The skill has no homepage and an unknown source/owner. Verify the service (nemovideo.ai) and the publisher before sending content or secrets. - Token sensitivity: NEMO_TOKEN is a bearer token. If you set a persistent environment variable, that token could be reused by other processes. Prefer using ephemeral anonymous tokens if you trust the service, or do not store a long-lived token in a global env var. - Data exposure: The skill uploads user-provided files (images, audio, video) up to 200MB to the third-party API — do not upload sensitive or regulated data unless you have reviewed the service's privacy terms. - Persistence mismatch: SKILL.md references a config path (~/.config/nemovideo/) but the registry metadata did not list any config paths; ask the publisher whether the skill will write session/tokens to disk and where. - Visibility & auditing: Because the skill makes network calls to an external API, review logs or ask for a privacy/security policy if you need assurance about how data is stored/retained. If you want to proceed safely: ask the publisher for a homepage/repo, confirm whether any tokens or session IDs are written to disk and where, and use a limited-scope/ephemeral token when testing. If you cannot verify the service or the storage behavior, treat the skill as higher risk and avoid uploading sensitive files.

Getting Started

Share your text or images and I'll get started on AI 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.

Free Video Generator Cartoon — Generate Cartoon Videos from Text

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

Here's a typical use: you send a a short story prompt or three character illustrations, ask for turn my story idea into a 30-second animated cartoon video, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter scripts under 60 words produce faster and cleaner cartoon outputs.

Matching Input to Actions

User prompts referencing free 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	free-video-generator-cartoon
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 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

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.

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 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 animated cartoon video" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms and devices.

Common Workflows

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