Text To Video Invideo
PassAudited by ClawScan on May 10, 2026.
Overview
The skill is coherent for cloud text-to-video generation, but users should know it connects to a NemoVideo API and may upload selected text or media files there.
This looks like a normal instruction-only cloud video-generation skill. Before installing, confirm that you trust the NemoVideo API endpoint, understand that files or text you provide may be uploaded for rendering, and use a dedicated NEMO token if you choose to configure one.
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 skill can act against the NemoVideo API using the configured or generated token.
The skill uses a bearer token to access the external video service. This is expected for the stated integration, and the instructions say not to print tokens or raw JSON.
Include `Authorization: Bearer <NEMO_TOKEN>` ... on every request
Use a dedicated token if possible and avoid sharing the token in chats, logs, or uploaded files.
Text, documents, media, or URLs provided for video generation may be uploaded to the NemoVideo service.
The skill sends user-selected files or URLs to a remote API for processing. This is aligned with cloud video generation, but it is still an external data boundary.
**Upload**: POST `/api/upload-video/nemo_agent/me/<sid>` — file: multipart `-F "files=@/path"`, or URL: `{"urls":["<url>"],"source_type":"url"}`Only upload content you are comfortable sending to the external provider, and avoid sensitive documents unless you trust that service’s handling practices.
Invoking the skill may create an anonymous token/session and contact the external service before a video job is submitted.
The skill initiates an external API connection automatically when first used. This is coherent for a hosted rendering workflow, but users should be aware of the automatic network setup.
On first interaction, connect to the processing API before doing anything else.
Install only if you are comfortable with first-use connection to the listed NemoVideo API endpoint.
Users may assume one provider from the name while the actual API endpoint shown in the skill is another provider domain.
The displayed name references InVideo while the documented backend is NemoVideo. The API base is disclosed, so this is a transparency note rather than evidence of deception.
displayName: "Text to Video InVideo — Convert Text Into Shareable Videos" ... **API base**: `https://mega-api-prod.nemovideo.ai`
Verify the intended provider before uploading content or relying on the generated token workflow.