Video Editor Extension

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — trim the pauses, add transitions, and export as a clean MP4 — and get edit...

0· 49·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 cloud video editing and the skill only requests a single API credential (NEMO_TOKEN) and a config path for nemovideo — these are coherent with a remote-rendering video editor.
Instruction Scope
Runtime instructions direct the agent to upload user video files and poll/render via https://mega-api-prod.nemovideo.ai, including SSE handling and export polling. This is expected for a cloud editor, but it means user media will be transmitted to a third-party service and an anonymous token may be requested automatically if NEMO_TOKEN is not present. The skill explicitly instructs not to expose tokens/raw API output.
Install Mechanism
No install spec or code files — instruction-only skill. This limits local persistence and reduces local-supply-chain risk.
Credentials
Only one credential (NEMO_TOKEN) is required, which is proportional. Metadata lists a config path (~/.config/nemovideo/) that could be used to store tokens/session state; SKILL.md also instructs the agent to obtain an anonymous NEMO_TOKEN if none exists. Be aware tokens may be persisted in that config path.
Persistence & Privilege
Skill is not always:true, does not request to modify other skills or system-wide settings, and is user-invocable. It relies on server-side sessions but does not demand elevated local privileges.
Assessment
This skill appears to do what it says: it uploads user videos and controls a cloud render service using a single API token (NEMO_TOKEN). Before installing/using it, consider: 1) Privacy: your raw video files will be sent to https://mega-api-prod.nemovideo.ai — do not upload sensitive footage unless you trust that service and its privacy policy. 2) Token handling: if you don't provide NEMO_TOKEN, the skill will request an anonymous token (100 free credits, 7-day expiry) from the service and may persist session/token info (metadata references ~/.config/nemovideo/). If you prefer control, supply your own NEMO_TOKEN and monitor where it is stored. 3) Attribution headers: the skill requires sending X-Skill-Source/Version/Platform headers on each request (normal for a plugin). 4) No local binaries are installed and no unrelated credentials are requested. If you need higher assurance, audit network calls to the listed domain and review the service's terms/privacy before uploading private content.

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

latestvk976h7rpa755kpk697148ant9x84qnj9

License

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

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN

Comments