Video Maker Cartoon Free

Turn five character sketches and a short story script into 1080p animated cartoon videos just by typing what you need. Whether it's creating free animated ca...

Security Scan

The skill's declared purpose (creating cartoon videos) aligns with its runtime instructions and requested credential (NEMO_TOKEN); minor metadata inconsistencies and privacy considerations are noted but do not indicate intentional misdirection.

Purpose & Capability

The skill is a cloud-backed video rendering tool and requests a single service token (NEMO_TOKEN), which is consistent with needing authenticated access to a remote rendering API. Nothing in the instructions requires unrelated credentials or system-level access.

Instruction Scope

SKILL.md instructs the agent to create sessions, upload user files, stream SSE responses, and poll render status on the external API — all expected for a cloud render workflow. It also tells the agent to generate an anonymous token by POSTing to the provider's auth endpoint when NEMO_TOKEN is not present, and to 'auto-setup' on first use. These behaviors imply network communication and likely storage of session/token state; the instructions do not ask for unrelated files or secrets. Be aware that user-supplied images and scripts will be transmitted to the external service.

Install Mechanism

This is an instruction-only skill with no install spec or code to write to disk, which is the lowest-risk install profile.

Credentials

Only one credential is required (NEMO_TOKEN) — appropriate for accessing the remote API. The skill's frontmatter also lists a config path (~/.config/nemovideo/) which suggests the agent may persist tokens or session state; the registry metadata provided separately did not list this config path, creating a small inconsistency that should be clarified.

Persistence & Privilege

The skill is not set to always:true and does not request elevated platform privileges. However, the frontmatter-configured config path implies the skill may store files (tokens/session state) under ~/.config/nemovideo/; this is plausibly needed but the registry metadata mismatch should be resolved so the user knows where data will be written.

Assessment

This skill appears to do what it says: it uploads your images/text to a remote rendering service (mega-api-prod.nemovideo.ai) and returns a rendered video. Before installing, consider: (1) Privacy — your images and scripts will be sent to that external service, so don't upload sensitive content. (2) Token handling — the skill will use NEMO_TOKEN if present, otherwise it will request an anonymous token from the provider and may persist session/token state under ~/.config/nemovideo/ (the registry metadata and the skill frontmatter disagree on config paths — ask the author to clarify). (3) Revocation — know how to revoke the token/anonymous access with the provider if you stop using the skill. (4) Verify the domain and service reputation if you have concerns about data handling. If you need higher assurance, request the skill author to: explicitly document where tokens are stored, how long they last, and provide an option to opt out of persisting tokens to disk.

Getting Started

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

Try saying:

• "create my images or text"
• "export 1080p MP4"
• "turn my script and images into"

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.

Video Maker Cartoon Free — Create Animated Cartoon Videos Free

This tool takes your images or text and runs AI cartoon video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have five character sketches and a short story script and want to turn my script and images into an animated cartoon video with music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter scripts under 60 seconds render significantly faster.

Matching Input to Actions

User prompts referencing video maker cartoon free, 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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	video-maker-cartoon-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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.

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.

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)

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

Common Workflows

Quick edit: Upload → "turn my script and images into an animated cartoon video with music" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn my script and images into an animated cartoon video with music" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms.