Editor Ai Hd
v1.0.0YouTubers and content creators edit raw video footage into HD edited videos using this skill. Accepts MP4, MOV, AVI, WebM up to 500MB, renders on cloud GPUs...
⭐ 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 claims cloud GPU video editing and the SKILL.md instructs uploading videos and calling render endpoints using a single NEMO_TOKEN — this is coherent. Note: the YAML frontmatter lists a config path (~/.config/nemovideo/) that the registry metadata did not list; that discrepancy should be clarified.
Instruction Scope
Instructions stay within video-editing scope (session creation, SSE for edits, multipart upload, render polling). They do require the agent to read/detect an install path to derive X-Skill-Platform and to save a session_id; both are plausible but extend beyond purely 'upload this one file' behavior and may require filesystem access or local storage of session state.
Install Mechanism
No install spec or code files are present (instruction-only), so nothing will be written to disk by an installer. This is the lowest-risk install mechanism.
Credentials
Only one credential (NEMO_TOKEN) is required, which matches a cloud API. However the frontmatter mentions a config path (~/.config/nemovideo/) which would give the skill access to local configuration — that wasn't listed in the registry metadata and may be unnecessary. The skill also suggests generating and storing an anonymous token (100 credits, 7-day expiry); clarify whether tokens are stored persistently or only in-memory.
Persistence & Privilege
always:false (no forced global enable). The skill will store session_id and may write session state locally per instructions, which is reasonable for multi-step cloud jobs. Autonomous invocation is allowed (default) but not excessive by itself.
Assessment
This skill appears to do what it says: upload videos and call a cloud render API using a NEMO_TOKEN. Before installing, confirm: (1) the external domain (mega-api-prod.nemovideo.ai) is a service you trust to handle your media; (2) whether the skill will persist the anonymous token and session_id on disk (the frontmatter references ~/.config/nemovideo/); and (3) whether the agent will access other files when detecting install paths. If you need stronger privacy controls, avoid using anonymous token generation or uploading sensitive footage until you verify the service's terms and storage retention policies.Like a lobster shell, security has layers — review code before you run it.
latestvk9739sej597ea705m5a2r8p7x984kqpr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN