Automatic Generator Cartoon

Get cartoon-style videos ready to post, without touching a single slider. Upload your images or video (MP4, MOV, AVI, WebM, up to 500MB), say something like...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-based cartoon-video conversion integration that uses a single service token (NEMO_TOKEN); nothing in the SKILL.md indicates unrelated access or hidden behavior, though there are a couple of small metadata inconsistencies to be aware of.

Purpose & Capability

The skill is advertised as a cloud-based cartoon video converter and only asks for a single service credential (NEMO_TOKEN) and describes API endpoints that match that purpose. Note: the frontmatter in SKILL.md references a configPath (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch is likely benign but worth confirming.

Instruction Scope

SKILL.md contains precise instructions for authenticating (including how to obtain an anonymous token), creating a session, uploading media, using SSE, exporting and polling for results. All referenced files, endpoints, and headers are directly related to converting and exporting media. The instructions explicitly tell the agent not to print tokens or raw JSON. There is some vague guidance about auto-detecting the platform from install path which could imply reading the agent install path, but this is minor and consistent with adding a platform header.

Install Mechanism

No install spec or code files are included — this is instruction-only. That minimizes on-disk installation risk.

Credentials

Only one environment variable (NEMO_TOKEN) is required and it is the credential for the documented API; SKILL.md also documents how to obtain a short-lived anonymous token if none is provided. There are no unrelated secrets requested.

Persistence & Privilege

The skill is not always-enabled and does not request special system-wide privileges. It expects to maintain a session_id and job IDs for in-progress jobs (normal for a render service). Autonomous invocation is allowed by default (platform normal) but is not combined with any broad or unrelated access here.

Assessment

This skill is coherent with its stated purpose: it will use the NEMO_TOKEN (or acquire a short-lived anonymous token) to upload your media to nemovideo.ai, create render jobs, and return download URLs. Before installing, confirm you trust the nemo domain and are comfortable the service will receive the media you upload. Check where you store NEMO_TOKEN (environment vs agent config) and treat it like an API key — revoke it if you stop using the skill. Note the minor metadata mismatch (SKILL.md mentions a config path while registry metadata does not); you may want to ask the publisher whether the skill reads or writes ~/.config/nemovideo/. Avoid sending sensitive personal data in media uploads and verify the service's privacy policy if that matters to you.

Getting Started

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

Try saying:

• "convert my images or video"
• "export 1080p MP4"
• "automatically convert my video 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.

Automatic Generator Cartoon — Convert Videos into Cartoon Style

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

Say you have a 30-second live-action video clip and want to automatically convert my video into a cartoon animation style — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds produce the most consistent cartoon results.

Matching Input to Actions

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

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

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.

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

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

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.

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 "automatically convert my video into a cartoon animation style" — 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 social platforms.

Common Workflows

Quick edit: Upload → "automatically convert my video into a cartoon animation style" → 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.