Ai Batch Video Creator
v1.0.0Get batch-processed MP4s ready to post, without touching a single slider. Upload your multiple video files (MP4, MOV, AVI, WebM, up to 500MB), say something...
⭐ 0· 59·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 claims to perform batch video processing and requires a NEMO_TOKEN (primary credential) and an optional config path for nemo config in its SKILL.md — that aligns with a cloud video service. However, registry metadata above lists no required config paths while the SKILL.md frontmatter declares ~/.config/nemovideo/ as a config path; this mismatch should be reconciled. The requirement to add attribution headers (X-Skill-Source/Version/Platform) for every request is unusual but coherent with a service wanting client identification.
Instruction Scope
All runtime instructions describe API calls to mega-api-prod.nemovideo.ai (auth, session creation, uploads, SSE, export/polling). That matches the described function (uploading and rendering video). It explicitly instructs creating anonymous tokens if no NEMO_TOKEN is present and uploading potentially large and private video files to the external service — this is expected but privacy-sensitive. The SKILL.md also expects the agent to 'auto-detect' platform from an install path (not always available), which is an implementation assumption rather than a necessity for the skill's purpose.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest installation risk (nothing is written to disk by an installer).
Credentials
The skill asks for a single token (NEMO_TOKEN) which is proportionate to interacting with a third‑party API. The SKILL.md provides a fallback to obtain a short-lived anonymous token via the service's anonymous-token endpoint if NEMO_TOKEN is absent — this means the skill can operate without pre-provisioned credentials. The earlier mismatch about configPaths (registry metadata vs SKILL.md) should be clarified. No other unrelated secrets are requested.
Persistence & Privilege
always is false and the skill has no install or persistent system presence; it does not request broad system privileges or modify other skills' configuration.
Assessment
This skill will upload your video files to https://mega-api-prod.nemovideo.ai and will either use a NEMO_TOKEN from your environment or mint a short-lived anonymous token for you. Before using it: 1) Don’t upload sensitive or private footage until you trust the service and have verified its privacy policy and ownership of the domain. 2) If you provide a NEMO_TOKEN, treat it like any API secret; only provide a token you control and can revoke. 3) Note the SKILL.md requests special attribution headers and expects to detect platform from an install path—this is an implementation detail but unusual; verify the client behavior if you audit network calls. 4) The registry metadata and SKILL.md disagree about a config path; ask the publisher to clarify. If you proceed, test with non‑sensitive sample videos first and be prepared to revoke the token or stop using the skill if anything looks unexpected.Like a lobster shell, security has layers — review code before you run it.
latestvk97a987k76sq0nr48jsb48xmeh84ps3z
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN