ClawHub

Ai Video Editor Hiring

v1.0.0

Get polished edited clips ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, WebM, up to 500MB), say something li...

⭐ 0· 48·0 current·0 all-time
by@linmillsd7
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
✓
Purpose & Capability
Name/description match the declared cloud backend endpoints and the single required credential (NEMO_TOKEN). Uploading media and requesting render/export via the nemo video API is coherent for an AI video editor.
ℹ
Instruction Scope
SKILL.md instructs the agent to check for NEMO_TOKEN, generate an anonymous token if missing, create a session, upload files and stream SSE. It does not request unrelated files or credentials, but it is vague about whether/where it will persist tokens or write to ~/.config/nemovideo/ (metadata lists that path).
✓
Install Mechanism
No install steps or external packages — instruction-only skill. Nothing is downloaded or written by an installer in the manifest.
✓
Credentials
Only NEMO_TOKEN is required. That is proportional to a cloud editing service. The skill will also create anonymous tokens via the service API if NEMO_TOKEN is absent, which is consistent with the workflow.
✓
Persistence & Privilege
always:false and no special privileges requested. The skill will create sessions on the remote service but does not demand persistent system-wide privileges.
Assessment
This skill is coherent for remote AI video editing, but you should consider privacy and token handling before installing: 1) Uploads: your raw media will be uploaded to https://mega-api-prod.nemovideo.ai — do not send sensitive or private footage unless you trust the service and its policies. 2) Tokens: the skill uses NEMO_TOKEN (or will create an anonymous token). Ask the author whether tokens are stored on disk (metadata references ~/.config/nemovideo/) and for how long sessions or uploaded media are retained. 3) Attribution headers and auto-detection: the skill requires custom headers (X-Skill-Source/Version/Platform); confirm these will be set exactly and not leak unexpected local paths. 4) If you want tighter control, create a dedicated service account/token with minimal scope and avoid using long-lived personal credentials. If the author can clarify where tokens are stored/rotated and how long media is kept, that will raise confidence.

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

latestvk97dm708ytzv0eewrbxb1wcr3184r2fx

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN

Comments