Youtube Video Clip Maker

v1.0.5

The youtube-video-clip-maker skill lets you extract precise clips from longer videos by simply describing what you want — no timeline scrubbing or manual key...

0· 104·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description align with requested resources: the skill talks to nemovideo's API, uses a NEMO_TOKEN for auth, and persists a client_id under ~/.config/nemovideo/. No unrelated cloud credentials or binaries are requested.
Instruction Scope
Instructions direct the agent to generate/read ~/.config/nemovideo/client_id, call the nemovideo API to obtain an anonymous token if none supplied, create a session, and (implicitly) upload user video files to the service for trimming. Uploading user media to an external API is expected for this skill but is a privacy/consent consideration the user should be aware of.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is downloaded or written beyond the client_id file the skill itself documents. This minimizes local code execution risk.
Credentials
Primary credential NEMO_TOKEN is appropriate for the described remote service. However, registry metadata lists NEMO_TOKEN as required while SKILL.md documents it as optional (auto‑generated anonymous token). This mismatch should be clarified. The only local path the skill writes is ~/.config/nemovideo/client_id (UUID only), which is proportionate.
Persistence & Privilege
always:false and no elevated privileges. The skill persists only a client_id in the user's config directory and does not request system-wide settings or other skills' credentials.
Assessment
This skill appears to do what it says, but before installing consider: 1) Privacy: using the skill will upload your video files to https://mega-api-prod.nemovideo.ai / nemovideo.com — don't upload sensitive content unless you trust the service and have reviewed its privacy/terms. 2) Token mismatch: the registry metadata marks NEMO_TOKEN as required but the SKILL.md says an anonymous token can be auto‑generated; ask the publisher whether you must supply your own token or can safely use the anonymous flow. 3) Local writes: the skill will create ~/.config/nemovideo/client_id (UUID only) — benign but persistent. 4) Session handling: confirm whether the skill persists NEMO_TOKEN to disk or only keeps it in session memory; prefer ephemeral tokens if you supply a personal token. 5) Source verification: homepage and repo are provided but source is listed as 'unknown' — if you need stronger assurance, review the repo or vendor documentation (nemovideo.com) and test with a non‑sensitive sample video first. Providing any API token grants the service access to your uploads, so only proceed if you trust the provider.

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

latestvk97f0h8v378t4p99qdb9rb0f0s83xgjv

License

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

Runtime requirements

✂️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN

Comments