YouTube Transcript Pipeline Lite

v1.0.0

Run a lightweight YouTube transcript workflow: transcribe, attribution cleanup, translation, and packaging with minimal tooling. Use for repeatable transcrip...

0· 552·0 current·0 all-time
byBlueBirdBack ✨@bluebirdback
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
The name/description (YouTube transcript generation, cleanup, translation, packaging) matches the SKILL.md steps. The skill does not request unrelated binaries, environment variables, or config paths.
Instruction Scope
The instructions stay within transcript generation, speaker cleanup, translation, and packaging. They repeatedly emphasize not changing timestamps and keeping raw outputs. One minor vagueness: it tells the agent to "Run your existing transcript flow" which assumes the agent has access to mutually-trusted transcription tooling; the skill itself does not instruct reading unrelated files or exfiltrating data.
Install Mechanism
No install spec and no code files are provided (instruction-only). Nothing is downloaded or written to disk by the skill itself.
Credentials
No environment variables, credentials, or config paths are required. There are no requests for unrelated secrets or excessive permissions.
Persistence & Privilege
always is false and the skill does not request persistent/system-wide changes. It neither modifies other skills nor asks for elevated platform presence.
Assessment
This skill is instruction-only and internally consistent, but it depends on whatever transcription tooling the agent already has: before installing, confirm the agent's transcript pipeline (or any external APIs it will invoke) is trustworthy and won't leak sensitive audio/transcript data. Because the skill keeps raw outputs and manifests, make sure you have an appropriate data-retention and sharing policy for transcripts and translations. Limit use to explicit invocations (don't bind it to always-on automation) if you want tighter control.

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

latestvk97am6mg1x78ja5qy80kvxjgw5819f5z

License

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

Comments