Video Generator Free No Filter
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill is mostly coherent as a cloud video generator, but its “free/no restrictions” framing conflicts with documented upgrade/export limits and users should review it before sending media.
Before installing, understand that this is a third-party cloud service: it will send your prompts and uploaded media to mega-api-prod.nemovideo.ai, use a NEMO_TOKEN, and may have export or upgrade limits despite the “free/no filter” wording. Avoid uploading sensitive media unless you trust the provider and its terms.
Findings (6)
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.
A user may believe the service is free and unrestricted, then discover export or plan limitations only after sending prompts or media.
The skill advertises itself as free and unrestricted, but its own error handling says free-plan export may be blocked and may require registration or upgrade.
displayName: "Video Generator Free No Filter — Generate Videos Without Restrictions" ... "402 | Free plan export blocked ... Register or upgrade your plan to unlock export."
Treat the free/no-restrictions claims cautiously; confirm pricing, export limits, and content rules before uploading files or relying on the output.
Using the skill causes the agent to contact a third-party backend and create or use a session for rendering.
The skill directs the agent to make remote API calls automatically during setup. This is aligned with the cloud video-generation purpose, but it is still external tool/API use.
On first use, set up the connection automatically ... POST `https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token`
Use it only if you are comfortable with automatic connection setup to the NemoVideo API.
Anyone with the token could potentially use the associated NemoVideo credits or session access.
The skill uses a bearer token for the remote provider. This is expected for the integration and the instructions say not to expose it, but it is still credential use.
Look for `NEMO_TOKEN` in the environment ... All requests must include: `Authorization: Bearer <NEMO_TOKEN>` ... Don't expose tokens
Use a dedicated token, avoid sharing logs containing it, and rotate or revoke it if you suspect exposure.
Private video, image, audio, or prompt content uploaded for generation may be processed by the remote service.
Prompts and selected media files are sent to a remote provider API. This is central to the stated cloud-rendering purpose, but the artifacts do not describe retention or privacy boundaries.
`/run_sse` | POST | Send a user message ... `/api/upload-video/nemo_agent/me/<sid>` | POST | Upload a file ... Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.
Do not upload sensitive personal, confidential, or regulated media unless you have reviewed the provider’s privacy and retention terms.
A render job may keep running remotely or consume credits even if the local session is interrupted.
Remote render jobs can continue or become orphaned if the user leaves before completion. This is disclosed and purpose-aligned, but users should notice it.
The session token carries render job IDs, so closing the tab before completion orphans the job.
Monitor exports until completion and check whether the service provides cancellation or cleanup controls for unfinished jobs.
Users have limited provenance information for assessing who maintains the integration or service endpoint.
The skill has no install-time code, but the registry metadata does not provide a verifiable source or homepage for the remote-service integration.
Source: unknown; Homepage: none
Prefer verified publishers or independently confirm the service identity before using credentials or uploading important media.