Ai Video Dance Generator

generate images or video into animated dance videos with this skill. Works with JPG, PNG, MP4, MOV files up to 200MB. TikTok creators use it for animating ph...

Security Scan

The skill's stated purpose (animating images/video) matches the network calls and single credential it requests, but there are several documentation/integration inconsistencies and privacy‑relevant behaviors (automatic anonymous token issuance, hidden technical details, and a mismatched config-path declaration) that warrant caution before installing.

Purpose & Capability

The skill claims to generate animated dance videos and only requests a single service token (NEMO_TOKEN), and its runtime instructions call the expected upload/render/export endpoints on mega-api-prod.nemovideo.ai. That is broadly coherent. However, the SKILL.md frontmatter advertises a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — an inconsistency in declared requirements.

Instruction Scope

Instructions direct the agent to upload user-supplied images/videos to an external cloud API, establish sessions, poll renders, and (if no NEMO_TOKEN present) automatically request anonymous tokens by POSTing to an auth endpoint. Those network actions are expected for a cloud render service but are privacy-sensitive because user media is transmitted externally. The SKILL.md also instructs the agent to 'Keep the technical details out of the chat,' which would hide network/upload activity from users — this is a red flag for transparency. The doc also instructs generating and storing client IDs and session IDs and reading/detecting install paths for header construction, which implies the agent may read local path/installation context.

Install Mechanism

There is no install spec and no code files — this is instruction-only. That minimizes disk-level risk since nothing is downloaded or installed by the skill itself.

Credentials

Only one environment credential is declared (NEMO_TOKEN) and is the expected primary credential for a cloud API. The SKILL.md provides a fallback flow that will create/use an anonymous token by calling the API if NEMO_TOKEN is absent; that behavior is reasonable for convenience but increases network activity and token storage surface. Also note the frontmatter lists a config path (~/.config/nemovideo/) that is not reflected in the registry's required config paths — possible mis-declaration.

Persistence & Privilege

The skill is not marked always:true and does not request system-wide persistent installation. It instructs creation/management of session tokens for the service (normal for a cloud API). There is no instruction to modify other skills or agent-wide settings.

What to consider before installing

This skill will upload any images or video you provide to mega-api-prod.nemovideo.ai and will either use a NEMO_TOKEN from your environment or request an anonymous token on your behalf. Before installing or invoking it: - Confirm you trust the external service (https://mega-api-prod.nemovideo.ai) and review its privacy/TOS because your media will be sent off‑device. - Prefer supplying your own NEMO_TOKEN (from an account you control) rather than allowing the skill to create anonymous tokens automatically. - Ask the skill author to clarify the config-path mismatch (~/.config/nemovideo/ appears in SKILL.md but not in registry metadata) and whether any tokens or session data will be written to disk and where. - Be cautious about sending sensitive or private imagery (faces, IDs, confidential content). - If you need stronger guarantees, request an explicit log of network calls the skill will make (endpoints, headers, and whether any uploaded media is retained) or a source/homepage so you can audit code. These inconsistencies and the directive to 'keep technical details out of the chat' reduce transparency — not inherently malicious, but suspicious and worth clarification prior to use.

Getting Started

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

Try saying:

• "generate my images or video"
• "export 1080p MP4"
• "make this photo dance to a"

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.

AI Video Dance Generator — Animate Photos Into Dance Videos

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

Say you have a single full-body photo of a person and want to make this photo dance to a hip-hop beat — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: full-body images with clear backgrounds produce the most accurate dance animations.

Matching Input to Actions

User prompts referencing ai video dance 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.

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 ai-video-dance-generator, 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 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

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 field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

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 → "make this photo dance to a hip-hop beat" → 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 "make this photo dance to a hip-hop beat" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms.