DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to bulk export a channel's transcripts for a search index with YouTube Skills

Collect video IDs from a channel or playlist and export transcripts in retrieval-sized chunks.

  • Research
  • Intermediate
  • 30 minutes
  • From the README
  • Claude Code
  • Cursor
  • Codex

Credentials. The bulk job spends one credit per video, so keep the API key in a protected shell profile or secret store and check the balance before a large run.

Who it is forA developer building a search or RAG index over a creator's or course's back catalogue.

The problemScripting transcript downloads for hundreds of videos means handling rate limits, retries and chunking yourself.

The outcomeA single batch job returns chunked transcripts in JSON, ready for an embedding pipeline with no re-chunking step.

What you need first

  • An agent that reads the Agent Skills format, such as Claude Code, Cursor or Codex
  • A TranscriptOut API key starting with sk_, created on first run with an email code (free account, 100 credits)
  • Node.js with npx for the npx install path

Steps

  1. Run npx skills add artemchuikin/youtube-skills --skill youtube-full
  2. Ask the agent to list the channel or playlist IDs first, using ids_only=true to keep the lookup cheap
  3. Ask the agent to submit one bulk job for those videos, with segment=1000&format=json
  4. Check job progress and read results page by page while the job runs

Prompt for your agent

Using the youtube-skills repo, list all video IDs for <channel or playlist>, then submit one bulk transcript job with segment=1000 and format=json. Report the job ID, the number of videos accepted and the credits charged, and confirm that each chunk has a start timestamp.

Caveat. Bulk submit costs one credit per video, and results are read while the job is still running, so partial output is normal until the job finishes.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page