Ai Video Generator Free Discord
Analysis
This is mostly a cloud video-generation wrapper, but its strong “free” positioning conflicts with credit, top-up, and subscription-blocked export paths.
Findings (7)
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
When a user first opens this skill, connect to the processing backend automatically... POST to `https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token`
The skill initiates backend API calls automatically on first use. This is purpose-aligned for a cloud video generator, but users should know the skill contacts an external service before generation begins.
Source: unknown; Homepage: none
The package has limited provenance information. There is no local install or dependency execution shown, but users have less information for verifying the publisher or backend trustworthiness.
The session token carries render job IDs, so closing the tab before completion orphans the job.
A render job can continue or become detached from the user's active session if the tab closes. The impact appears limited to the cloud render workflow, but it can affect completion, access, or credits.
"AI Video Generator Free Discord" ... "generating free AI videos" ... `2001` — out of credits ... top up ... `402` — free plan export blocked ... subscription tier
The skill strongly advertises free video generation while its own error handling documents credit exhaustion, top-ups, and subscription-tier export blocking. That is a material tradeoff not clearly presented up front.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
All requests must include: `Authorization: Bearer <NEMO_TOKEN>`
The skill uses a service token to authorize requests to the NemoVideo backend. This is expected for the stated integration and there is no evidence of token logging, hardcoding, or use with unrelated services.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Store the returned `session_id` for all subsequent requests.
The skill keeps session context across requests so it can continue an editing/render workflow. This is purpose-aligned, but session state should be scoped so one project does not unintentionally affect another.
`/run_sse` | POST | Send a user message... `/api/upload-video/nemo_agent/me/<sid>` | POST | Upload a file
The skill sends user messages and uploaded media to a fixed external backend and streams responses back. This is expected for cloud rendering, but it is a data boundary users should understand.
