Video Maker Google
v1.0.0Turn three product photos and a logo file into 1080p finished MP4 videos just by typing what you need. Whether it's creating short videos from images or clip...
⭐ 0· 52·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
The skill name/description (cloud video rendering) matches the required environment variable (NEMO_TOKEN) and the network endpoints it calls (nemovideo API). Minor inconsistency: the registry metadata reported no required config paths, but the SKILL.md frontmatter lists a config path (~/.config/nemovideo/). This looks like a harmless metadata mismatch rather than a functional mismatch with purpose.
Instruction Scope
SKILL.md instructs the agent to check NEMO_TOKEN, optionally obtain an anonymous token via the service's auth endpoint, create a session, upload files, stream SSE for edits, and request renders. All referenced files, endpoints, and headers are tied to the stated video-rendering workflow; the instructions do not ask the agent to read unrelated system files or unrelated environment variables.
Install Mechanism
This is instruction-only with no install spec or code files, so nothing is written to disk or installed. That's appropriate and lower risk for this type of remote service integration.
Credentials
The only credential requested is NEMO_TOKEN, which is proportionate for a hosted video-rendering API. The skill also instructs the agent to fetch an anonymous token from the service if NEMO_TOKEN is missing (reasonable). Users should note the token grants access to remote rendering and has a 7-day expiry — treat it like a service credential. No unrelated secrets are requested.
Persistence & Privilege
The skill does not request always: true and does not attempt to modify other skills or system-level config. It expects to keep a session_id for operations within a user's session, which is normal for this workflow.
Assessment
This skill appears to do what it says: it sends your images/videos to a remote service (mega-api-prod.nemovideo.ai) for rendering and returns a download URL. Before installing, consider: 1) Are you comfortable uploading the media you plan to render to an external service? Avoid sending sensitive/confidential images. 2) The skill uses a single credential (NEMO_TOKEN) and can obtain a temporary anonymous token itself; treat any tokens as service credentials and revoke them if you suspect misuse. 3) Verify the service domain and ownership if you need an audit trail or have compliance concerns—the skill's source/homepage is unknown. 4) The SKILL.md frontmatter mentions a local config path (~/.config/nemovideo/), which is likely informational; confirm the platform won't attempt to read unrelated local files. If you need greater assurance, ask the skill author for the service's privacy policy, official homepage, or the provenance of the API endpoints before sending production or private media.Like a lobster shell, security has layers — review code before you run it.
latestvk976k16t5d1pwra5ey8y3gqgsn84pd2f
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN