Text To Speech Video
PassAudited by ClawScan on May 16, 2026.
Overview
This is a coherent cloud text-to-video connector, but it sends selected content to NemoVideo and uses or creates a Nemo token, so users should treat uploads as external processing.
Before installing, confirm you are comfortable using NemoVideo's cloud service, sending your selected scripts or media to that provider, and allowing the skill to use or create a NEMO_TOKEN that may consume credits. Avoid sensitive uploads unless you trust the service and have verified the supported file types.
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.
Scripts, files, or media chosen for generation may be uploaded to NemoVideo's cloud service.
The skill explicitly sends user-provided content to an external provider API for processing. This is expected for a cloud video-generation skill, but it is still a data-sharing boundary users should understand.
This skill connects to a cloud processing backend... Base URL: `https://mega-api-prod.nemovideo.ai` ... `/api/upload-video/nemo_agent/me/<sid>` | POST | Upload a file (multipart) or URL.
Only use the skill with content you are comfortable sending to the external provider, and avoid uploading sensitive documents unless you trust the service.
The agent can use the NemoVideo token to create sessions, check credits, upload content, and start exports under that token.
The skill uses a provider bearer token, and can create an anonymous token if one is not present. This is purpose-aligned for the service, but it gives the agent authority to create sessions and consume provider credits.
Look for `NEMO_TOKEN` in the environment... POST `https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token`... Include `Authorization: Bearer <NEMO_TOKEN>` and all attribution headers on every request
Use a limited-purpose token, monitor credit usage, and revoke or rotate the token if you no longer want the skill to access the service.
Users may be unsure which file types are actually supported or may upload documents expecting a workflow the endpoint list does not clearly describe.
The front description advertises document/script formats, while the later upload list names media formats. This looks like a capability clarity issue rather than malicious behavior.
Works with TXT, DOCX, PDF, SRT files up to 200MB... Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.
Verify supported input formats before uploading large or sensitive files.
It is harder to independently confirm who maintains the skill or review provider documentation before use.
There is no executable install payload, but there is also no source or homepage to help verify the provider or publisher.
Source: unknown Homepage: none No install spec — this is an instruction-only skill.
Prefer installing only if you trust the publisher and the NemoVideo service endpoint shown in the skill.