Run a lightweight YouTube transcript workflow: transcribe, attribution cleanup, translation, and packaging with minimal tooling. Use for repeatable transcript handoff tasks when you need a concise, auditable process over custom automation.
Scanned 5/30/2026
Install via CLI
openskills install GeorgeDoors888/GB-Power-Market-JJ---
name: youtube-transcript-pipeline-lite
description: "Run a lightweight YouTube transcript workflow: transcribe, attribution cleanup, translation, and packaging with minimal tooling. Use for repeatable transcript handoff tasks when you need a concise, auditable process over custom automation."
---
# YouTube Transcript Pipeline (Lite)
## Quick Start
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
## Minimal Workflow
1. **Transcribe**
- Run your existing transcript flow for the target video (word-level preferred for reliable speaker calibration).
- Keep all raw outputs.
2. **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.
3. **Translate (optional)**
- Translate content line-by-line.
- Keep format exactly: `[HH:MM:SS] Speaker: text`.
- Keep technical terms unless explicitly asked to simplify.
4. **Package for handoff**
- Create concise structure: `transcripts/`, `artifacts/`, `MANIFEST.txt`.
- Include one reviewed transcript + one translated version when asked.
## What not to do in this skill
- 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.
## Quality checks
- Validate final line counts against source.
- Confirm active final files are present and clearly named.
- Keep every major handoff stage discoverable in manifest.
## Reference
See `references/limits.md` for quick trade-offs and rollback guidance.No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an i...