You commented "PM". Here it is. Two things: the free GitHub repo of 28 product management skills built from Lenny's Podcast, and a knowledge base I made so you can ask any product question and get answers from Lenny's guests, with the episode cited. No course, no upsell.
You'll also get the weekly letter: five useful things I made with AI, with the prompts and workflows inside. Unsubscribe any time.
Already on the list? Enter the same email and it unlocks without subscribing you twice.
Each skill turns one area of product management into instructions your AI assistant follows while you work.
The repo is called Awesome PM Skills. Every skill is a folder with a SKILL.md file inside: the frameworks, decision trees, templates and real examples for one part of the job, credited to the guests they came from. Brian Chesky, Shreyas Doshi, Marty Cagan, Kevin Weil, April Dunford and many more. The README says the skills draw on 300+ episodes, using the public transcript archive from ChatPRD.
You don't read these like a course. You install them, then work as normal. When you ask Claude Code to scope an MVP, it can pull in the scoping skill. When you ask for an exec update, it reaches for the memo skill.
Claude Code loads skills from a .claude/skills folder, so the job is to clone the repo and copy the skill folders there.
The repo's own README says to clone it into your workspace, but its "Get started" snippet still has a placeholder URL. Use the real one below. Run this from the project you want the skills in:
git clone https://github.com/menkesu/awesome-pm-skills.git
mkdir -p .claude/skills
for d in awesome-pm-skills/*/; do [ -f "$d/SKILL.md" ] && cp -R "${d%/}" .claude/skills/; doneThat copies every folder that has a SKILL.md and skips the images folder. Want the skills in every project? Swap .claude/skills for ~/.claude/skills.
Using Codex? Same loop, different folder. Codex looks for project skills in .agents/skills:
mkdir -p .agents/skills
for d in awesome-pm-skills/*/; do [ -f "$d/SKILL.md" ] && cp -R "${d%/}" .agents/skills/; doneThen use them. Tell the assistant what you're working on and it picks the skills that fit. If one doesn't kick in, name it: "Use the zero-to-launch skill" or "Use Shreyas Doshi's LNO framework on this".
one-step-better-ai-pm, is a newer add-on that pulls daily briefs from the author's GenAI PM newsletter. It needs a free GenAI PM subscription and a GENAIPM_EMAIL environment variable. Skip it if you just want the Lenny skills.Here they are sorted into the five stages from the Reel, so you can go straight to the part of the job you want to get better at.
The repo's README groups the same 28 skills into seven "modes". This is my grouping, not the author's. Each name links to its folder on GitHub.
Ask any product question and get an answer built from what Lenny's guests actually said, with every point credited to the guest and the episode.
I went through 35 recent episodes of Lenny's Podcast and turned each one into a one-page digest: the key lessons, the frameworks, a few short quotes and a link to the full episode on YouTube. Boris Cherny, Cat Wu, Elena Verna, Simon Willison, Marc Andreessen, Molly Graham and 29 more.
The zip also has a skill called lenny-wisdom. It tells your assistant how to use the digests: find the right three to six episodes, answer with citations, show where the guests disagree, and end with what to do next. Pressure-test a pitch, a roadmap or a pricing idea against the same people.
What's inside:
index.md: every episode with its topics, a "start here, by question" table and the themes that run across episodes.episodes/<slug>/summary.md: one digest per episode.all-episodes.md: all 35 digests in one file, for tools that want fewer uploads.lenny-wisdom/SKILL.md: the skill for Claude Code (it works in Codex too).README.md: the setup guide below, in more detail.Claude Code gets the full skill. Claude and ChatGPT get the same knowledge as project files plus a short instruction.
Claude Code. Unzip into your project, so you have your-project/lennys-podcast-knowledge-base/. Then copy the skill in:
mkdir -p .claude/skills cp -R lennys-podcast-knowledge-base/lenny-wisdom .claude/skills/
Start Claude Code in that project and ask: "What would Lenny's guests say about pricing an AI feature?" Or call it by name with /lenny-wisdom. In Codex, copy the same folder into .agents/skills/ instead.
A Claude Project. Create a Project in Claude, add index.md and all-episodes.md to the project knowledge, and paste the instruction below into the project instructions.
ChatGPT. Create a Project, add the same two files and paste the same instruction. Building a custom GPT instead? Put the instruction in Instructions and the two files under Knowledge. Custom GPTs limit how many knowledge files you can add, which is why the combined file is there.
Answer my questions using only the Lenny's Podcast digests in this project's knowledge. Start from index.md to find the 3 to 6 most relevant episodes, then read their digests. Credit every point to the guest and the episode. Show where guests disagree, not just where they agree. If the digests don't cover my question, say so and label your own reasoning as yours. Answer in this shape: Take, What the guests say, Counter-signals and risks, What to do next.
Installing skills doesn't make you a better PM. Using them on a real decision this week does.
zero-to-launch on a side project. Then ask the knowledge base "what do Lenny's guests say a great PM does in the AI era?"prioritization-craft and strategic-build over it, then ask the knowledge base to pressure-test the top item.exec-comms for the memo, influence-craft for the room.positioning-craft first, then launch-execution.You're on the list now. Every week you'll get five useful things I made with AI, with the prompt or workflow behind each one. This kit was one of them.
Back to the site