Video Merge
v1.0.0Get merged MP4 video ready to post, without touching a single slider. Upload your multiple video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like...
⭐ 0· 65·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 is a cloud video-merge tool and asks only for NEMO_TOKEN (the service API token), which is proportional to its stated purpose. Minor mismatch: the public registry metadata listed no required config paths, but the SKILL.md YAML frontmatter includes a configPaths entry (~/.config/nemovideo/). This is a small inconsistency in metadata but could indicate the skill expects a local nemovideo config directory.
Instruction Scope
The SKILL.md directly instructs the agent to upload user video files and call nemovideo.ai endpoints (session, upload, export, SSE) — exactly what a cloud merge tool must do. It also instructs the agent to detect an install path to set an X-Skill-Platform header, which implies the agent may inspect filesystem paths; that is not clearly declared in the registry. Otherwise the instructions stay within the stated purpose and do not ask for unrelated files or secrets.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest-risk installation model. Nothing is downloaded or written to disk by an install step.
Credentials
Only NEMO_TOKEN is declared as required and is the primary credential, which fits a cloud API workflow. The skill also describes an anonymous-token fallback (POST to mega-api-prod.nemovideo.ai) and says to 'use it as NEMO_TOKEN' — it's unclear whether that token is stored persistently or only used in-memory during a session. The earlier-mentioned configPaths entry (present in SKILL.md but not in registry) raises a small question about whether local config files might be read.
Persistence & Privilege
always:false and default model invocation are normal. The skill does not request permanent platform-level privileges. The only persistence ambiguity is whether the acquired anonymous token might be written or bound to a user account — the docs mention registration links but do not instruct the skill to modify other skills or system-wide settings.
Assessment
This skill is coherent with a cloud video-merge service: it will upload your video files to https://mega-api-prod.nemovideo.ai and requires an API token (NEMO_TOKEN) or will obtain an anonymous token for you. Before installing or using it, consider: (1) Privacy: your videos will be sent to an external service — confirm you are comfortable sharing that content. (2) Verify the endpoint and owner: the skill source is 'unknown' and homepage is absent; if you need stronger assurance, ask the publisher for a home page or documentation and verify the domain. (3) Token handling: confirm whether anonymous tokens or provided NEMO_TOKENs are stored persistently or only used for the session. (4) Metadata mismatch: SKILL.md references a local config path (~/.config/nemovideo/) and install-path-derived headers — ask whether the agent will inspect your filesystem. If any of these leave you uncomfortable or unanswered, do not enable the skill until the publisher clarifies.Like a lobster shell, security has layers — review code before you run it.
latestvk975mbc9m2mh1abkwqaxpg3kfs84qknj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN