Animated Video Generator

generate text or images into animated MP4 videos with this animated-video-generator skill. Works with PNG, JPG, MP4, GIF files up to 200MB. marketers, educat...

Security Scan

The skill's requirements and runtime instructions align with its stated purpose (remote video rendering) and request only a single service token; however it will make network calls to an external API, may create/use an anonymous token, and inspects a few local paths, so review network/privacy implications before use.

Purpose & Capability

The skill claims to render videos on a remote service and only requests a single credential (NEMO_TOKEN) and a config path under ~/.config/nemovideo/. Those requirements are consistent with calling an external video-rendering API.

Instruction Scope

Runtime instructions confine actions to the nemovideo backend (session creation, SSE chat, uploads, exports). The skill instructs the agent to read its YAML frontmatter and to detect an install path (~/.clawhub, ~/.cursor/skills) to populate X-Skill-Platform; that requires minimal filesystem checks. It does not instruct reading unrelated sensitive files, but it will upload user-supplied media (up to 200MB) and send data to mega-api-prod.nemovideo.ai.

Install Mechanism

There is no install spec or downloaded code — this is an instruction-only skill, so nothing is written to disk by the skill itself during install.

Credentials

Only NEMO_TOKEN is declared as required (and a config path for local caching). Declaring NEMO_TOKEN as primary is appropriate for a remote service. The instructions also support obtaining an anonymous token via the service's anonymous-token endpoint when no token is present, which is explainable given the skill's purpose.

Persistence & Privilege

The skill is not always-on and does not request system-wide persistence or modifications to other skills. It can be invoked autonomously (platform default), but it does not request unusual privileges.

Assessment

This skill appears internally consistent with a remote video-rendering service, but it will make outbound network calls to mega-api-prod.nemovideo.ai and will upload any media you provide. Before installing: 1) Confirm the origin of NEMO_TOKEN (only provide a token you trust). 2) Be comfortable with sending media (up to 200MB) to the advertised domain and review that service's privacy/retention policy. 3) Note the skill may obtain an anonymous token if no NEMO_TOKEN is present — this gives the skill temporary credentials to the service. 4) If you want to limit exposure, run the skill in a sandboxed environment or block network access to the domain until you've vetted it. If you need higher assurance, request the skill's source or a published homepage/terms for the nemovideo service; absence of a known publisher reduces confidence.

Getting Started

Ready when you are. Drop your text or images here or describe what you want to make.

Try saying:

• "generate a short product description paragraph into a 1080p MP4"
• "turn this text into a 30-second animated explainer video with characters and motion graphics"
• "creating animated explainer videos from text or images for marketers, educators, content creators"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Animated Video Generator — Generate Animated Videos from Text

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

A quick example: upload a short product description paragraph, type "turn this text into a 30-second animated explainer video with characters and motion graphics", and you'll get a 1080p MP4 back in roughly 1-3 minutes. All rendering happens server-side.

Worth noting: shorter scripts under 60 words produce tighter, faster animations.

Matching Input to Actions

User prompts referencing animated video generator, 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: animated-video-generator
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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)

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

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn this text into a 30-second animated explainer video with characters and motion graphics" — 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 and presentation platforms.

Common Workflows

Quick edit: Upload → "turn this text into a 30-second animated explainer video with characters and motion graphics" → Download MP4. Takes 1-3 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.