Show HN: Book-skills – Agent Skills distilled from mgmt and programming books

A Show HN submission introduces book-skills, an open-source collection of Claude Code skills distilled from management and programming books. The author built it after experimenting with Claude Code skills and asking whether those skills could encode the frameworks they already apply repeatedly at work. Named examples include The Lean Startup, High Output Management, and The Pragmatic Programmer, with each skill mapped to a single book rather than a generic topic.

Technically, book-skills treats a Claude Code skill as a container for a book’s methodology, not a synopsis. Installing a skill such as the Lean Startup skill loads that book’s working method into the agent session so Claude can apply it when prompted. The design goal is executability: turn repeated professional frameworks into callable agent behavior instead of passive reading notes or chat-side summaries.

For engineers and builders, this is a concrete way to put durable process knowledge next to the tools already used for coding. Instead of re-explaining build-measure-learn loops, management cadence, or pragmatic engineering habits in every prompt, a skill can carry that structure once and reuse it across tasks. That matters most for people who already live by a few books and want the agent to follow those same rules under pressure.

Market context sits at the intersection of open-source agent tooling and Show HN–style personal infrastructure. Claude Code skills are becoming a packaging format for reusable agent behavior; book-skills shows that packaging applied to classic management and programming canons, not only to APIs or repo conventions. It competes less with book summaries and more with ad-hoc system prompts and private skill libraries that never leave one developer’s machine.

The practical takeaway is to try encoding one methodology you already use—not a book you have not read—and judge whether the agent’s outputs follow that process under real work prompts. Watch whether the collection stays book-scoped and methodology-first, how install-and-invoke flows feel day to day, and whether other authors publish comparable skill packs for the same titles or adjacent canons.