Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Run a lightweight YouTube transcript workflow: transcribe, attribution cleanup, translation, and packaging with minimal tooling. Use for repeatable transcrip...
Run a lightweight YouTube transcript workflow: transcribe, attribution cleanup, translation, and packaging with minimal tooling. Use for repeatable transcrip...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use this when a user asks for: YouTube transcript generation and cleanup speaker correction around interview/interjector vs main speaker translated transcript output while preserving timestamps/speakers ready-to-share folder packaging
Transcribe Run your existing transcript flow for the target video (word-level preferred for reliable speaker calibration). Keep all raw outputs. Speaker cleanup (small-impact) Preserve the default/primary speaker mapping. Only flip clearly short-interjection/question lines when they are obviously misattributed. Keep line count and timestamps unchanged. Translate (optional) Translate content line-by-line. Keep format exactly: [HH:MM:SS] Speaker: text. Keep technical terms unless explicitly asked to simplify. Package for handoff Create concise structure: transcripts/, artifacts/, MANIFEST.txt. Include one reviewed transcript + one translated version when asked.
Do not introduce heavy automation assumptions. Do not change line/timestamp structure unless user explicitly asks. Do not aggressively relabel all speaker turns; prefer conservative flips.
Validate final line counts against source. Confirm active final files are present and clearly named. Keep every major handoff stage discoverable in manifest.
See references/limits.md for quick trade-offs and rollback guidance.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.