Subtitle Download Skill
v1.0.0Turn a 10-minute YouTube tutorial video into 1080p downloadable subtitle files just by typing what you need. Whether it's downloading subtitle files from vid...
⭐ 0· 57·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the runtime instructions: the skill uploads video files and calls nemovideo.ai endpoints to extract subtitles and render exports. Requesting a service token (NEMO_TOKEN) is appropriate for this purpose.
Instruction Scope
Instructions direct the agent to upload user video files to the remote nemovideo.ai service, manage a session_id, poll for render status, and use SSE — all expected for a cloud render/subtitle workflow. Note: this necessarily transmits user media to a third party (the skill makes this explicit). The skill also reads its own frontmatter and attempts to detect an install path for attribution headers — reading its own metadata is expected, but 'detect install path' is a minor extra step that only affects header population.
Install Mechanism
Instruction-only skill with no install spec or downloaded code, so nothing is written to disk during install. Runtime network calls are used instead; that's expected for this cloud service integration.
Credentials
Only NEMO_TOKEN is required (primary credential). The SKILL.md also supports generating an anonymous token if none is present — a proportional fallback. Minor inconsistency: the registry metadata listed no required config paths, but the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/); this is a small metadata mismatch but not a large credential overreach.
Persistence & Privilege
The skill does not request 'always: true' and does not ask to modify other skills or system-wide settings. It will act at runtime and can be invoked by the agent (normal behavior).
Assessment
This skill uploads whatever video you provide to mega-api-prod.nemovideo.ai and requires a NEMO_TOKEN (or will obtain a short-lived anonymous token). That is expected for a cloud subtitle/render service, but be aware: any video you send will leave your machine and be processed by their servers. Before using it with sensitive or private content, check the service's privacy/retention policy and prefer ephemeral anonymous tokens or short-lived credentials rather than a long-lived NEMO_TOKEN. Note the small metadata mismatch: the frontmatter mentions a config path while the registry did not — not a major issue, but worth asking the publisher for clarification if you need guarantees about local config access. If you need subtitles without sending media externally, consider a local tool instead.Like a lobster shell, security has layers — review code before you run it.
latestvk9709k68emrsj474vq4rcg5d6h84q6x0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📥 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN