Editor Ai Youtube

v1.0.0

YouTubers edit raw video footage into edited YouTube videos using this skill. Accepts MP4, MOV, AVI, WebM up to 500MB, renders on cloud GPUs at 1080p, and re...

0· 66·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description describe a cloud AI video editor and the SKILL.md only requests an API token (NEMO_TOKEN) and describes API calls to a rendering backend (mega-api-prod.nemovideo.ai), which is proportionate to the stated purpose.
Instruction Scope
Instructions focus on establishing a session, uploading video files, streaming SSE messages, polling export status, and returning download URLs — all appropriate for a cloud editor. They explicitly instruct obtaining an anonymous token if no NEMO_TOKEN is present and to upload files (multipart or via URL). Note: SKILL.md references detecting install path (~/.clawhub, ~/.cursor/skills/) and a config path (~/.config/nemovideo/) in frontmatter metadata; the instructions do not clearly justify reading the user's filesystem beyond receiving user-supplied upload paths, so this is a small ambiguity to verify.
Install Mechanism
Instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. This is low risk from an install perspective.
Credentials
Only NEMO_TOKEN is declared as required and used. That token is the expected credential for a hosted service. The skill instructs creating a short-lived anonymous token if none is present, which is consistent with the service flow.
Persistence & Privilege
always is false and there is no request for persistent system-wide privileges or modification of other skills. The skill is eligible for autonomous invocation (platform default) but does not request elevated installation privileges.
Assessment
This skill appears internally consistent for a cloud video editor, but before installing consider the following: (1) Using the skill uploads your raw video to mega-api-prod.nemovideo.ai — do you trust that endpoint and its privacy/retention policies? (2) The skill accepts a NEMO_TOKEN; prefer using a short-lived or anonymous token rather than a long-lived personal secret. (3) SKILL.md mentions a config path (~/.config/nemovideo/) and infers install-path-based headers — clarify whether the skill will read those local paths if you care about filesystem privacy. (4) Because this is instruction-only (no code files), static scanners had nothing to analyze; runtime behavior (network calls, file uploads) happens when the skill runs, so limit use with sensitive content unless you verify the vendor. (5) If you need stronger assurance, request the skill publisher or vendor homepage, privacy policy, and a list of exactly which headers/metadata are transmitted with uploads.

Like a lobster shell, security has layers — review code before you run it.

latestvk9743z50tw27rb94aqfffbsyrh84kr97

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN

Comments