// Extract transcripts, captions, or subtitles from YouTube videos. Use when the user provides a YouTube URL or video ID and asks for a transcript, optionally with timestamps, or asks to save captions to a file.
| name | youtube-transcript |
| description | Extract transcripts, captions, or subtitles from YouTube videos. Use when the user provides a YouTube URL or video ID and asks for a transcript, optionally with timestamps, or asks to save captions to a file. |
| user-invocable | true |
Fetch a YouTube video's transcript using youtube-transcript-api.
Reference: https://gist.github.com/intellectronica/6178110791dc19a05d7c0173118fd48e
nix-shell -p 'python312.withPackages (ps: [ ps.youtube-transcript-api ])' --run 'python {baseDir}/scripts/get_transcript.py "VIDEO_URL_OR_ID"'
With timestamps:
nix-shell -p 'python312.withPackages (ps: [ ps.youtube-transcript-api ])' --run 'python {baseDir}/scripts/get_transcript.py "VIDEO_URL_OR_ID" --timestamps'
Save to a file:
nix-shell -p 'python312.withPackages (ps: [ ps.youtube-transcript-api ])' --run 'python {baseDir}/scripts/get_transcript.py "VIDEO_URL_OR_ID" --timestamps' > transcript.txt
<video-id>-transcript.txt.https://www.youtube.com/watch?v=VIDEO_IDhttps://youtu.be/VIDEO_IDhttps://youtube.com/embed/VIDEO_IDhttps://youtube.com/v/VIDEO_IDGuide frontend component design and code review using functional cohesion. Use when designing, reviewing, or refactoring React/TypeScript UI components with multiple roles, similar screens, conditional rendering, API-union-driven UI, notifications, directory/file rows, create/edit forms, or when deciding whether to split, merge, or commonize components.
Fetch today's Discord channel + Mastodon posts via API tokens, summarize to Markdown, and save into an Obsidian vault (Bun script).
Audit the baseline repo hygiene of an existing Next.js project when joining it for the first time. Use this whenever the user says they just joined a Next.js project, asks what to check first, wants a first-pass setup review, or wants to confirm dependency pinning, pnpm workspace strictness, Knip setup, Node version pinning, environment-variable validation, or testing strategy before doing feature work.
Draft or refine a newcomer-friendly GitHub issue from repo context. Use when the user asks to create a "good first issue", wants a small scoped starter task, needs an issue body with clear acceptance criteria, or wants to split a larger task into a safe first contribution.
Draft or refine an architecture decision record (ADR) when the user needs a durable technical decision, not just a summary. Use for architecture, dependency, API contract, infrastructure, security, tooling, or process choices that need clear rationale, rejected alternatives, consequences, and an adoption path.
Lint and secure GitHub Actions workflows using pinact, actionlint, ghalint, and zizmor. Use when the user adds, updates, or reviews GitHub Actions workflows and wants to check correctness, security, or pin action versions.