Who it is forA teacher, course creator or developer who needs a short explainer on a concept and has no video editor.
The problemProducing a whiteboard-style explainer normally means recording, drawing and editing by hand.
The outcomeAn MP4 of a diagram drawn stroke by stroke while a voice explains it, plus a contact sheet of every beat.
What you need first
- macOS
- Node 20 or newer
- ffmpeg (install with brew install ffmpeg)
- Claude Code, since the repo installs as a Claude Code skill
Steps
- Install ffmpeg on macOS with
brew install ffmpeg. - Clone the skill into Claude Code's skills folder with
git clone https://github.com/haiderfarooq3/khan-explainer ~/.claude/skills/khan-explainer. - Install dependencies with
cd ~/.claude/skills/khan-explainer/scripts && npm install && npx playwright install chromium. - Ask Claude Code: Make a 30-second Khan-style explainer on <topic>.
- Open the MP4 and the contact sheet path that the render prints, and check the layout on each beat.
Prompt for your agent
Using the khan-explainer skill in ~/.claude/skills/khan-explainer, write a 30-second Khan-style explainer scene about <topic> and render it to an MP4. Confirm the render prints a contact sheet path and that the MP4 plays with narration and drawing in sync.
Caveat. The skill's built-in voice is the macOS say voice, so the narration sounds like a system voice unless you add an optional voice.
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