Video Animation
ReviewAudited by ClawScan on May 4, 2026.
Overview
This appears to be a coherent cloud video-animation skill, but it sends uploaded media to a NemoVideo backend and uses a bearer token/session to run remote render jobs.
This skill is reasonable for cloud video animation if you are comfortable sending your media to NemoVideo. Protect the NEMO_TOKEN, avoid uploading sensitive files unless you trust the service, and request confirmation before exports if you want tighter control over credit use.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may create a remote session and perform video-editing/export API steps as part of the workflow.
The skill can initiate remote setup and perform API actions based on backend responses. This is consistent with a cloud video editor, but it means users should expect remote workflow actions rather than only passive advice.
When a user first opens this skill, connect to the processing backend automatically... Backend says | "click [button]" / "点击" | Execute via API ... "Export button" / "导出" | Execute export workflow
Use the skill when you intend to work with the NemoVideo backend, and ask for confirmation before exports or other credit-consuming actions if that matters to you.
Anyone with the token may be able to use the associated NemoVideo session or credits until it expires or is revoked.
The skill uses a bearer token to access the video-rendering service. This credential use is expected for the integration, but the token should still be treated as sensitive.
Check if `NEMO_TOKEN` is set... The response `data.token` is your NEMO_TOKEN — 100 free credits, valid 7 days... All requests must include: `Authorization: Bearer <NEMO_TOKEN>`
Protect NEMO_TOKEN like a password, avoid pasting it into chats or logs, and rotate or remove it if you no longer use the skill.
Files you upload for animation leave the local environment and are processed by the remote NemoVideo service.
The workflow sends user media and prompts to an external provider for processing. This is disclosed and purpose-aligned, but uploaded images, videos, audio, and generated drafts may contain private or business-sensitive content.
All rendering happens server-side... All calls go to `https://mega-api-prod.nemovideo.ai`... Upload — `POST /api/upload-video/nemo_agent/me/<sid>` — multipart file or JSON with URLs.
Do not upload confidential, regulated, or rights-sensitive media unless you trust the provider and its data-handling terms.
You have less provenance information to evaluate who operates or maintains the integration.
There is no local code to install, but the registry information does not provide a source repository or homepage to independently verify the service/operator behind the external API integration.
Source: unknown Homepage: none No install spec — this is an instruction-only skill.
Prefer installing only if you recognize the provider or can otherwise verify that the NemoVideo API endpoint is legitimate.