With Ai Youtube
v1.0.0edit YouTube video files into YouTube-ready videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. YouTubers use it for editing and optimi...
⭐ 0· 57·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description ask for YouTube video editing and the runtime instructions exclusively call a single backend (mega-api-prod.nemovideo.ai) and require a NEMO_TOKEN—this is proportionate to the claimed capability.
Instruction Scope
Instructions are explicit about uploading user files, creating sessions, streaming SSE, polling render status, and optionally checking local install/config paths to populate an attribution header. These actions are within the editing workflow, but the skill will read supplied local file paths for upload and may check ~/.config/nemovideo/ and certain install paths (~/.clawhub/, ~/.cursor/skills/) to set headers—be aware this touches your home directory when run.
Install Mechanism
No install steps or downloads are present (instruction-only), so nothing is written to disk by the skill itself during install.
Credentials
Only a single credential (NEMO_TOKEN) is declared and used; the SKILL.md also describes a reasonable anonymous-token fallback via the nemovideo auth endpoint. No unrelated secrets or multiple external credentials are requested.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform-wide privileges or modify other skills. Autonomous invocation is allowed (platform default) but not combined with other red flags.
Assessment
This skill will upload your video files to an external service (mega-api-prod.nemovideo.ai) and uses a NEMO_TOKEN if present, otherwise it requests an anonymous token from the same service. Only provide tokens you trust to be used that way. Expect the skill to read any local file paths you provide for upload and to check a nemovideo config folder and common install paths to populate attribution headers; if you prefer not to expose those local paths or a persistent token, avoid setting NEMO_TOKEN and be cautious when uploading sensitive content. If you need higher assurance, verify the remote service and its privacy/retention policies before use.Like a lobster shell, security has layers — review code before you run it.
latestvk9702h6tf2r4kr4hx1eh2h1zt584mb9c
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
▶️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
