The result is book-skills, an open-source collection of Claude Code skills where each skill represents a book (The Lean Startup, High Output Management, The Pragmatic Programmer, etc.).
The goal isn't to summarize books. It's to make their methodologies executable.
For example, after installing the Lean Startup skill, asking Claude something like:
> "How should I validate this idea before building it?"
is enough for Claude to structure its response around Build-Measure-Learn, MVPs, validated learning, actionable metrics, and pivot/persevere decisions. There's no need to explicitly mention the book or ask Claude to use that framework.
Each skill is just a `SKILL.md` file with:
- a description containing the concepts that trigger the skill
- the actionable ideas from the book
- instructions describing how Claude should apply those ideas
I'd love feedback on two things:
1. Is this a useful way of reusing methodologies you already rely on?
2. Which books would you turn into skills?
Repository: