
Open-source conversion skill that turns...
Questions open the relevant chapter instead of placing the whole file in the chat. Chapter files stay out of the skill budget until the topic comes up, and the core file keeps the mental model plus a chapter index. The extractor picks a tool by format: lightweight extraction for prose, a parser that keeps tables for technical books with code and formulas, and an immediate stop for scanned pages that still need text recognition. The generated skill records frameworks, decision rules, and anti-patterns, and it is not allowed to copy source paragraphs. After conversion you can publish the skill to a private repository and install it from there. It fits engineers and researchers who keep returning to the same technical book, runbook, or design spec.
book-to-skill is an open-source conversion skill that turns a technical book, a folder of documents, or a collection of sources into an agent skill loaded on demand. It pairs a deterministic extractor with a spec-driven generator. The default output is a core skill file, per-chapter files, a glossary, a pattern list, and a cheat sheet. Hosts include GitHub Copilot CLI, Amp, Claude Code, Hermes Agent, OpenCode, and OpenClaw. The same flow also fits internal manuals, brand guidelines, and research notes. The project is MIT licensed, the converter is free, and extraction runs on your machine.
Difficulty: Intermediate
Chapters loaded on demand
Splits a book into one file per chapter, plus a glossary, a pattern list, and a decision cheat sheet, and reads a chapter only when the question needs it.
More than books
The same flow accepts a technical book, architecture notes, a runbook, a brand voice guide, or a stack of papers, from a file, a folder, or a glob.
Format-specific extractors
Plain text and Markdown need no extra dependency. Prose books, technical books with tables, ebooks, and scans use different tools, and scans stop with an explanation.
Local processing and copyright limits
Extraction runs on your machine, and the repository contains no book text. Skills generated from copyrighted material should stay private and not be redistributed.
Keep a technical book in the workflow
An engineer converts a technical book they keep reopening, then asks the assistant by skill name and topic so it reads the matching chapter.
Fold internal docs into a skill
A team points the converter at architecture decisions and an onboarding handbook, then asks questions while coding instead of rereading the folder.
Turn a brand guide into a skill
Design or writing teammates convert a voice guide and component principles so the assistant answers from the spec instead of a long file.
The repository says extraction and analysis run on your machine and the tool itself does not upload files. If the assistant model runs in the cloud, text you send follows that provider's normal terms, as with any prompt. The repo contains no book text, and you should use a copy you have the right to read.
The name says book, but the input can be any structured prose you keep reopening. Internal docs such as architecture records, runbooks, and onboarding guides can be converted as a folder. Brand voice, component principles, papers with notes, API contracts, and compliance docs are listed too. Plain text and Markdown need no extra extractor.
If the pages are images with no text layer, the extractors cannot read them. The tool checks the first pages, stops, and explains why, instead of producing an empty skill. Run your own text recognition first, then pass the text-layer file to book-to-skill. Ebooks and office documents have their own parser dependencies.
Real reviews and feedback from users