ClawHub

Ai Copywriter Video

v1.0.0

Get script-overlaid videos ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, WebM, up to 500MB), say something l...

⭐ 0· 59·0 current·0 all-time
by@francemichaell-15
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 (AI copywriting + overlaying captions on video) align with the API endpoints and actions described in SKILL.md (upload, SSE-based generation, render/export). The single required credential (NEMO_TOKEN) is appropriate for a cloud video service.
ℹ
Instruction Scope
Instructions are scoped to the Nemo backend: create/use session, upload files or URLs, stream SSE messages, poll render status, return download URL. The skill tells the agent to read its own YAML frontmatter and detect install path to populate X-Skill-Platform headers, and it will POST to an anonymous-token endpoint if no NEMO_TOKEN is present. These behaviors are explainable for attribution and fallback auth, but they do mean user video data and generated tokens are sent to the external API.
✓
Install Mechanism
No install spec and no code files — instruction-only skill. No binaries or archives are downloaded or written to disk by an installer, which minimizes install-time risk.
ℹ
Credentials
The skill only requires one credential (NEMO_TOKEN), which is appropriate. Metadata also lists a config path (~/.config/nemovideo/) that the SKILL.md does not actually reference; this mismatch is minor but should be clarified by the author. The runtime also requires access to any files the user uploads (video paths) — expected for this purpose.
✓
Persistence & Privilege
always:false and normal model invocation. The skill does not request elevated/persistent system privileges or modification of other skills. It only asks to read its own frontmatter/paths for attribution.
Assessment
This skill appears to do what it says: it sends your uploaded video to Nemo's cloud rendering service and uses a NEMO_TOKEN to authenticate. Before installing or using it, consider: 1) Any video you upload will be transmitted to an external service (mega-api-prod.nemovideo.ai) — do not upload sensitive footage you wouldn't want processed off‑site. 2) Prefer supplying your own NEMO_TOKEN rather than relying on the anonymous-token fallback if you want account-level auditing or control. 3) Ask the developer to explain why metadata lists ~/.config/nemovideo/ when the runtime docs don't reference that path. 4) Check Nemo's privacy/retention policy if you care about how long uploaded media or generated text is stored. If those items are acceptable, the skill's requests and instructions are proportionate to its stated purpose.

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

latestvk977am028497krjkkzkcdy0ycd84p3vz

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