Video Merger Online
v1.0.0combine video clips into merged MP4 video with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for combining multiple v...
⭐ 0· 50·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The skill name/description (cloud video merging) matches the instructions: uploading clips, creating a session, queuing render jobs, and returning a download URL. Requesting a NEMO_TOKEN for API access is proportionate to the stated purpose. Accepted formats and endpoints align with video processing.
Instruction Scope
Instructions focus on API calls required to upload media, create sessions, stream edits, and export results. They include behavior for obtaining an anonymous token if NEMO_TOKEN is missing, reading/using a session_id, and translating SSE messages to the user. Potential scope issues: the skill specifies adding attribution headers that include a platform value derived from the agent's install path (this requires reading the agent install path and could expose local path information to the backend). The SKILL.md also references storing/keeping session_id but does not define where it is persisted.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest install risk. Nothing is downloaded or written to disk by an install mechanism described here.
Credentials
Only one required env var (NEMO_TOKEN), which is appropriate for a cloud API. The instructions also describe obtaining an anonymous token via the backend if NEMO_TOKEN is absent (consistent with allowing both logged-in and anonymous use). Minor inconsistency: the registry metadata summary lists no required config paths, but the SKILL.md frontmatter metadata includes a configPaths entry (~/.config/nemovideo/). This mismatch should be clarified.
Persistence & Privilege
always is false and the skill does not request elevated or persistent platform privileges. It asks to keep session_id for operations (normal for session-based APIs) but does not request to modify other skills or system-wide settings.
Assessment
This skill appears to do what it says: it uploads your clips to a cloud backend, composes them there, and returns a download link. Before installing/using it: (1) confirm you trust the backend domain (mega-api-prod.nemovideo.ai) — your uploaded media will be sent there; (2) decide if you want to provide a persistent NEMO_TOKEN (linked to an account) or let the skill request an anonymous token (the skill can obtain one automatically); (3) note the SKILL.md asks the agent to derive a platform header from local install paths — that could leak a local path string to the service, so ask the publisher to remove or justify that behavior; (4) clarify the metadata mismatch about config paths (~/.config/nemovideo/) before giving permissions or a persistent token. If you need higher assurance, request the publisher’s homepage/source or an explicit privacy/data-retention policy before use.Like a lobster shell, security has layers — review code before you run it.
latestvk97f6wr76jjqy6v0vt8f52ngxh84pja1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN