Yoga Video Maker
v1.0.0Describe your yoga practice and NemoVideo creates the video. Morning flow sequences, flexibility progression content, beginner pose breakdowns, breathing tec...
⭐ 0· 73·0 current·0 all-time
bypeandrover adam@peand-rover
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The skill describes creating yoga videos via the NemoVideo backend and its instructions call the nemo API domain and request an API token - this is coherent with the declared purpose. Note: the registry metadata above said 'Required env vars: none' while the SKILL.md declares NEMO_TOKEN and a config path; that discrepancy should be reconciled.
Instruction Scope
Runtime instructions are scoped to the NeptuneVideo integration: they (a) greet the user, (b) check for NEMO_TOKEN, (c) read/write ~/.config/nemovideo/client_id, (d) call the anon-token endpoint via curl and store the returned token for the session, and (e) create a session. These actions are within the skill's purpose but do include reading/writing a user config path and making network calls to an external API.
Install Mechanism
No install spec or external downloads — instruction-only skill (no code files). This is the lowest-risk install mechanism.
Credentials
The SKILL.md requires a single credential (NEMO_TOKEN) and a config path under ~/.config/nemovideo/, which is proportionate for a third-party API integration. However the registry metadata at the top lists no required env vars; that mismatch should be clarified. The skill does not request unrelated credentials or broad system paths.
Persistence & Privilege
always is false and the skill only writes its own config file (~/.config/nemovideo/client_id) and stores a session token for the run. It does not request system-wide privileges or modify other skills' configs.
Assessment
This skill appears to do what it says: it will contact mega-api-prod.nemovideo.ai, create/read a small config file at ~/.config/nemovideo/client_id, and either use a NEMO_TOKEN you provide or call the anonymous-token endpoint to obtain a session token. Before installing: (1) Decide whether you’re comfortable uploading video content to NemoVideo’s backend and review their privacy/terms on https://nemovideo.com. (2) Note the registry metadata and the SKILL.md disagree about required env vars — expect the skill to use NEMO_TOKEN or generate a client_id file. (3) If you prefer, supply your own NEMO_TOKEN (so the skill won’t request an anonymous token) or inspect/delete ~/.config/nemovideo/ after use. (4) Don’t send sensitive personal data or credentials to the skill; it will transmit data to an external service. If you want higher assurance, verify the repository (https://github.com/nemovideo/nemovideo_skills) and confirm the API hostname and behavior with NemoVideo documentation before using.Like a lobster shell, security has layers — review code before you run it.
latestvk979q8rjqn8vm4x47k0tr360y183va9r
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
