ClawHub

Free Auto Caption

v1.0.0

content creators add video files into captioned video files using this skill. Accepts MP4, MOV, AVI, WebM up to 500MB, renders on cloud GPUs at 1080p, and re...

⭐ 0· 59·0 current·0 all-time
by@susan4731-wilfordf
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 (auto-captioning, cloud render) align with required credential (NEMO_TOKEN) and the SKILL.md which documents upload, session, render, and export endpoints. One minor inconsistency: the registry metadata reported no required config paths, but the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) used for attribution — this is likely metadata drift rather than malicious behavior.
ℹ
Instruction Scope
SKILL.md contains concrete runtime instructions: generate anonymous tokens, create sessions, upload files, use SSE endpoints, poll render status, and include Authorization and attribution headers. These actions are within the expected scope for a cloud rendering/captioning service. It instructs the agent to detect its install path (for X-Skill-Platform attribution) and to 'save session_id' and use tokens; it does not instruct reading unrelated system files or unrelated credentials. Clarify where tokens/session IDs are persisted (in-memory vs disk) and whether the agent will write to ~/.config/nemovideo/ if present.
✓
Install Mechanism
This is instruction-only (no install spec, no code files), so nothing gets downloaded or written by an installer. That is the lowest-risk install model.
✓
Credentials
Only NEMO_TOKEN is required (and the SKILL.md documents how to obtain an anonymous token if missing). That single credential is proportional to a cloud API integration. The only exception is the frontmatter's configPaths hint (~/.config/nemovideo/) which suggests optional local config access; the registry's required configPaths field was empty — ask the publisher to confirm whether any local config is read or written.
✓
Persistence & Privilege
The skill does not request always:true and does not ask to modify other skills or system-wide settings. It does instruct saving session_id and using tokens for future calls, which is expected for session-based APIs; confirm whether those are persisted to disk and for how long.
Assessment
This skill appears to be what it says: a cloud-based auto-captioning integration that needs a NEMO_TOKEN and will upload video files to nemovideo.ai. Before installing/using, consider: (1) Privacy and trust: your videos (and their audio) are uploaded to a third-party service — verify you trust mega-api-prod.nemovideo.ai and read its privacy/retention policy. (2) Token & session storage: ask the publisher whether NEMO_TOKEN or anonymous tokens/session IDs are stored on disk (the SKILL.md references ~/.config/nemovideo/ and detecting install paths); if so, verify where and for how long. (3) Billing/limits: the skill mentions credits, rate limits, and 7-day anonymous tokens — confirm expected behavior for private or large projects. (4) Metadata mismatch: the registry metadata omitted configPaths while the SKILL.md included one — request clarification. If you plan to upload sensitive footage, verify the service's terms and consider testing with non-sensitive material first.

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

latestvk973aq4y9q5264c45vypb6xetn84jbba

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