Animation Video Maker Free

create text or images into animated video files with this animation-video-maker-free skill. Works with PNG, JPG, MP4, GIF files up to 200MB. students, small...

Security Scan

The skill's declared requirements and runtime instructions are consistent with an online animation rendering service: it uses a single service token, talks to a single external API, and stores session state — nothing in the package suggests behavior outside that purpose.

Purpose & Capability

Name/description (create animated videos) aligns with required env var (NEMO_TOKEN) and config path (~/.config/nemovideo/). The API endpoints and headers described are appropriate for a cloud rendering backend.

Instruction Scope

SKILL.md instructs the agent to automatically obtain an anonymous token if NEMO_TOKEN is absent, create sessions, upload user files, and poll render status. It also instructs deriving X-Skill-Platform from local install-path checks (detecting presence of ~/.clawhub/ or ~/.cursor/skills/) and to avoid showing raw API responses or token values to the user. These actions are within the scope of a rendering service, but the automatic token acquisition, filesystem path detection for platform headers, and instruction to hide raw responses are worth noting for privacy/opacity reasons.

Install Mechanism

This is an instruction-only skill with no install spec or code files; nothing is written to disk by an installer. That is the lowest-risk install model.

Credentials

Only one credential is declared: NEMO_TOKEN (primaryEnv). That matches the described API usage. The skill also documents a config path (~/.config/nemovideo/) for storing session state; requiring a single service token is proportionate to the described functionality.

Persistence & Privilege

The skill will store session_id and likely persist the anonymous token into its config path for subsequent requests. It is not marked always:true and does not request other credentials. However, the instructions do not specify how/where tokens are stored (encryption, permissions), so there is a minor persistence/privacy consideration.

Assessment

This skill talks to an external API (mega-api-prod.nemovideo.ai), will upload the files you provide, and will create/store an anonymous NEMO_TOKEN and session id if you don't provide one. If you install/use it, consider: (1) Do you trust that external service and its privacy policy? (2) If you prefer more control, set your own NEMO_TOKEN ahead of use rather than letting the skill create one automatically. (3) Uploaded media will leave your machine — do not upload sensitive content. (4) Check the ~/.config/nemovideo/ folder (or equivalent skill config) afterward to see what was stored and remove tokens/sessions if you want to revoke access. The skill appears internally coherent, but review the external service and storage practices before using with sensitive data.

Getting Started

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

Try saying:

• "create my text or images"
• "export 1080p MP4"
• "create a 30-second animated explainer video"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Animation Video Maker Free — Create animated videos from text

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

Here's a typical use: you send a a short script or set of character images, ask for create a 30-second animated explainer video from this text script, 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 seconds produce the cleanest animations.

Matching Input to Actions

User prompts referencing animation video maker 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.

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

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

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

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

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.

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)

Common Workflows

Quick edit: Upload → "create a 30-second animated explainer video from this text script" → 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 "create a 30-second animated explainer video from this text script" — 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 social platforms and presentations.