alirezarezvani/claude-skills / engineering/book-to-skill/skills/book-to-skill
book-to-skill
UnverifiedUse when turning a book, docs folder or spec collection (PDF, EPUB, DOCX, HTML, Markdown) into an agent skill, before summarizing it by hand. Extracts with extract_document.py, compiles chapters, glossary and cheatsheet, validates with book_skill_validator.py and enforces a rights gate.
assets/chapter_template.md
View on GitHub# Chapter <N>: <Full Chapter Title>
<!--
Budget (Step 7): reference study
BOOK_TYPE=text 800–1,200 1,000–1,800
BOOK_TYPE=technical 1,200–1,800 2,000–3,000
Targets, not caps. Density beats length — never pad to hit a number.
Delete every section that does not apply; an empty heading costs tokens
on every load and tells the agent nothing.
-->
## Core Idea
<One or two sentences: the single most important thing this chapter teaches. If you cannot
state it plainly, re-read the chapter — you have copied it, not extracted it. If the chapter
is genuinely thin, say so here rather than padding the sections below.>
## Frameworks Introduced
- **<Framework Name — the author's exact naming>**: <exact formulation>
- When to use: <the specific situation that triggers it>
- How: <steps or criteria — explicit for study depth, a line for reference depth>
- Why it works / fails: <study depth only, for the top 1–2 frameworks>
## Key Concepts
<5–10 terms, no more. Past ten you are transcribing a glossary rather than chunking.>
- **<Term>**: <precise one-sentence definition>
## Mental Models
<2–4 thinking tools. Write them as instruments, not descriptions:
"Use X when Y" / "Think of X as Y" / "Prefer X over Y because Z".>
## Anti-patterns
- **<What to avoid>**: <why it fails, in the author's terms>
## Code Examples
<!-- Technical sources only. Delete for prose. Copy the single most instructive snippet;
preserve indentation exactly. One good example beats three partial ones. -->
```<language>
<key code example>
```
- **What it demonstrates**: <one line>
## Reference Tables
<!-- Technical sources only. Reproduce a comparison matrix, parameter table, or decision
table as Markdown. Tables do not compress — this is what the wider technical budget
is for. -->
## Worked Example
<!-- DEPTH=study only. Reconstruct ONE concrete thing the author works through: a sample
document, a dialogue, a filled-in template, a before/after, a decision walked end to
end. This is the single biggest reason a study chapter is worth its budget, and the
main thing a learner returns for.
Reconstruct compactly in your own words. Do not reproduce the author's example
verbatim at length — see references/rights_and_provenance.md. -->
## Key Takeaways
<3–7 items. Each one actionable — something a practitioner does differently tomorrow,
not something they now know.>
1. <Actionable insight>
2. <Actionable insight>
3. <Actionable insight>
## Connects To
<!-- The links are the navigation. A chapter with no Connects To is an island, and the
agent will only ever reach it through the topic index. -->
- **Ch <N>**: <why this chapter relates to that one>
- **<External concept or standard>**: <what it connects with outside this source>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |