Youtube Video To Text

v3.0.0

Transcribe any YouTube video to text using AI — get a full transcript, timestamped SRT captions, chapter summaries, and key-point extraction from any YouTube...

0· 84·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
medium confidence
Purpose & Capability
The skill's name and description (transcribe YouTube videos, produce SRT, summaries, key points) align with the runtime instructions which POST video/URL to a Nemovideo API. Requiring a single service token (NEMO_TOKEN) is appropriate for this purpose.
Instruction Scope
SKILL.md instructs the agent to send a YouTube URL or upload video/audio to an external API (mega-api-prod.nemovideo.ai) and to include the NEMO_TOKEN in Authorization. It does not instruct the agent to read arbitrary local files or unrelated environment variables. Note: the skill will transmit full audio/video and derived transcripts to a third-party endpoint — users should consider privacy of the content being uploaded.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so nothing is written to disk or installed by the skill itself — lowest install risk.
Credentials
The primaryEnv is NEMO_TOKEN which matches the curl example and is proportional. However, SKILL.md metadata lists a config path (~/.config/nemovideo/) while the registry metadata earlier reported no required config paths — a small inconsistency. There are no other credential requests, which is appropriate.
Persistence & Privilege
always is false and the skill does not request elevated or platform-wide persistence. disable-model-invocation is false (normal). The skill doesn't ask to modify other skills or system-wide settings.
Assessment
This skill appears to do what it says — it sends video/audio (or a YouTube URL) to a Nemovideo API and uses a single NEMO_TOKEN to authenticate. Before installing, verify the external service and trustworthiness (there's no homepage/source listed here), confirm what the NEMO_TOKEN grants and how long the provider stores/transmits data, and avoid sending sensitive or confidential recordings. If you can't validate the provider, consider creating a time-limited or least-privilege token, review the provider's privacy/retention policy, and test with non-sensitive content first. Note the small metadata inconsistency: SKILL.md lists a config path (~/.config/nemovideo/) while registry metadata showed none — ask the publisher to clarify whether the skill will read or write that local config directory.

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

latestvk971prpft5gbyppgfsqtf9g94h83rgbn

License

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

Runtime requirements

📄 Clawdis
Primary envNEMO_TOKEN

Comments