Video Editor Capcut
v1.0.0Get edited video clips ready to post, without touching a single slider. Upload your raw video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "t...
⭐ 0· 56·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
The name and description promise cloud-based AI video editing; the SKILL.md describes a cloud API for session creation, upload, SSE-driven editing, and export. The single required env var (NEMO_TOKEN) and the declared config path align with a dedicated video-editing backend.
Instruction Scope
Runtime instructions focus on creating/using a session token, uploading video files, polling renders, and reporting status. They do not instruct reading unrelated system files or harvesting unrelated environment variables. The skill will send user video files and metadata to the described API (mega-api-prod.nemovideo.ai), which is expected for this purpose.
Install Mechanism
No install spec or code files are present (instruction-only). That minimizes on-disk execution risk; all actions are HTTP interactions described in SKILL.md.
Credentials
Only NEMO_TOKEN is required and marked primary. The SKILL.md also documents how an anonymous token may be obtained if none is present. There are no unrelated secret env vars requested. The metadata lists a config path (~/.config/nemovideo/) which is plausible for storing service config, though the instructions do not require reading it.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. It does not instruct modifying other skills or system-wide agent settings; its behavior is limited to interacting with its own cloud backend.
Assessment
This skill uploads whatever video files you provide to the nemovideo.ai backend and uses a single service token (NEMO_TOKEN) to authenticate. Before installing or using it: (1) Confirm you trust the domain (mega-api-prod.nemovideo.ai) and its privacy/storage practices before uploading sensitive video content; (2) Prefer using an anonymous/token tied to this service (the skill can create one) rather than a shared secret; (3) Expect uploads and renders to occur on remote GPUs and that files will be transmitted over the network; (4) Check retention/cost/credit rules (tokens expire after 7 days and some operations may require registration/upgrades per the docs); (5) If you keep a long-lived NEMO_TOKEN in your environment, treat it like a service credential and rotate/revoke it if leaked.Like a lobster shell, security has layers — review code before you run it.
latestvk978fm90jx1mbvkyaxnfpsnjgd84sqnc
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN