DEDUPEDWho it is forA learner working through a video course who wants written notes instead of rewatching lectures.
The problemA playlist of lectures has no text version, so notes mean rewatching each video.
The outcomeThe agent lists the playlist videos and writes notes for each one from its transcript.
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
- Run
npx skills add artemchuikin/youtube-skills --skill youtube-playlist(inferred, check the README) - Ask the agent: Turn this lecture course into study notes: [playlist URL]
- Confirm the video count matches the playlist before the notes are written
- Save the notes as a file in your project folder
Prompt for your agent
Using the youtube-skills repo, list every video in the playlist <playlist URL>, fetch each transcript, and write one set of study notes per video with timestamps. Verify that the number of notes equals the number of videos returned.
Caveat. Playlist listing costs one credit per page of 100 videos, and each transcript fetch costs one credit, so long courses use more credits than a single video.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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