Ai Video Merger
v1.0.1Merge, combine, and join multiple videos into one polished video with AI — NemoVideo intelligently merges clips with color matching, audio normalization, smo...
⭐ 0· 64·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
Name/description (AI video merging) match the manifest: primary credential NEMO_TOKEN and a config path for ~/.config/nemovideo/ are reasonable for a cloud API client that stores credentials and uploads clips. No unrelated binaries or exotic permissions are requested.
Instruction Scope
SKILL.md describes uploading and harmonizing arbitrary clips (expected). The truncated snippet shows a curl-based upload flow — this implies user video/audio data will be transmitted to nemoVideo's servers. That is coherent for the stated purpose but has privacy implications; ensure uploads are only sent to the official API endpoints and that you accept offloading media to the service.
Install Mechanism
No install spec and no code files (instruction-only) — low local install risk. The skill relies on network/API calls rather than installing binaries.
Credentials
Only one primary credential (NEMO_TOKEN) is declared, which is proportionate. Minor inconsistency: metadata 'requires.env' is an empty list while 'primaryEnv' is set to NEMO_TOKEN — this is a bookkeeping/incoherence issue that should be corrected but doesn't imply malicious behavior. The config path (~/.config/nemovideo/) may be used to store the token; confirm what is stored there before installing.
Persistence & Privilege
always:false and default autonomous invocation are used. The skill does not request elevated or persistent system privileges; it does reference a per-user config path which is reasonable for storing API credentials.
Assessment
This appears to be an instruction-only client for the NemoVideo cloud service and is internally coherent, but before installing you should: (1) review the full SKILL.md to confirm the exact upload endpoints (curl commands) and ensure they point to the official nemovideo domain; (2) understand that your video/audio files will likely be uploaded to NemoVideo — do not upload sensitive or confidential footage unless you accept the service's privacy policy and retention rules; (3) verify the origin/repository and homepage links (https://nemovideo.com and the GitHub repo) to ensure legitimacy; (4) confirm NEMO_TOKEN scope and storage — prefer short-lived or scoped tokens and check what is written to ~/.config/nemovideo/; and (5) if you need higher assurance, request the full SKILL.md or test with non-sensitive sample files first. The only technical inconsistency found is that metadata lists primaryEnv but does not include it in the 'requires.env' list — ask the publisher to fix that manifest detail.Like a lobster shell, security has layers — review code before you run it.
latestvk978x4j5ejq3dwa3dkrsbpr2vn83t4mh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔗 Clawdis
Primary envNEMO_TOKEN