Free Video Generator Discord
v1.0.0generate text prompts or clips into shareable video clips with this skill. Works with MP4, MOV, WebM, GIF files up to 500MB. Discord community members use it...
⭐ 0· 15·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the runtime instructions: the SKILL.md describes uploading media, starting render jobs, polling status, and downloading results from a single external API (mega-api-prod.nemovideo.ai). Requesting a NEMO_TOKEN as the primary credential is coherent for a hosted rendering service. Note: the registry metadata did not list config paths, but the SKILL.md metadata includes a configPaths entry (~/.config/nemovideo/), which is an inconsistency in metadata but does not materially contradict the stated purpose.
Instruction Scope
Instructions remain focused on the video generation workflow (session creation, SSE chat, uploads, export/polling). Two items to note: (1) the SKILL.md instructs the agent to detect the install path to set an X-Skill-Platform header (this implies reading filesystem paths), and (2) it instructs saving session_id and using/storing NEMO_TOKEN. Neither is unexpected for this integration, but they require the agent to access environment/config state and potentially disk locations for attribution; that's narrower than broad system access but worth being aware of.
Install Mechanism
This is an instruction-only skill with no install spec or code files, so nothing is written to disk by an installer. That is the lowest-risk install profile.
Credentials
The skill declares a single credential (NEMO_TOKEN) as primary. The SKILL.md also provides an anonymous-token flow (POST to obtain a short-lived token), so requiring NEMO_TOKEN is proportional to the service's needs. There are no unrelated credentials requested.
Persistence & Privilege
always is false and the skill does not request system-wide privileges. It asks the agent to persist session_id/token state for the video workflow, which is appropriate for a sessioned API integration and does not modify other skills or global agent configuration.
Assessment
This skill appears to do what it says: connect to nemo video APIs, accept uploads, and manage render jobs. Before installing, consider: (1) you will be sending media and any associated text prompts to a third-party domain (mega-api-prod.nemovideo.ai) — don't upload private/sensitive content you wouldn't want shared with that service; (2) the skill asks for a NEMO_TOKEN (or will fetch a short-lived anonymous token) — prefer the anonymous token flow or a scoped account token rather than a long-lived personal credential; (3) the skill may read/install-path information to populate attribution headers and will store a session_id/token for the session — if you are uncomfortable with the agent reading config/install paths, avoid installing; (4) verify the service's privacy/terms if you need assurances about retention of uploaded media. The main metadata inconsistency is that SKILL.md lists a configPath while the registry metadata did not — this is likely benign but worth noting.Like a lobster shell, security has layers — review code before you run it.
latestvk972d4937ycp8yd2g1r4ttqnvn84rbh9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN