Create Claude skills from book content (markdown files). Transforms long-form book knowledge into structured, context-efficient skill packages with granular reference files, workflows, and use-case guidelines. Use this skill when: - Converting a book (markdown) into a reusable Claude skill - Creating knowledge bases from technical books, guides, or documentation - Building skills that need progressive disclosure of large content - Structuring book knowledge for efficient context loading
View on GitHubskills/skill-from-book/SKILL.md
February 1, 2026
Select agents to install to:
npx add-skill https://github.com/bmad-labs/skills/blob/main/skills/skill-from-book/SKILL.md -a claude-code --skill skill-from-bookInstallation paths:
.claude/skills/skill-from-book/# Skill From Book
Transform book content into structured, context-efficient Claude skills.
## Overview
This skill guides you through converting a book (in markdown format) into a well-organized skill with:
- Granular knowledge files (one concept per file)
- Workflows for repeatable tasks
- Use-case guidelines (mapping tasks to relevant files)
- Progress tracking for multi-session work
- Subagent extraction tasks
## CRITICAL INSTRUCTIONS
**YOU MUST FOLLOW THIS WORKFLOW STRICTLY. DO NOT SKIP OR REORDER PHASES.**
1. **DO NOT read the book markdown file content before starting Phase 1**
2. **MUST read each reference file BEFORE starting its corresponding phase**
3. **MUST complete each phase before moving to the next**
4. **MUST use subagents for extraction tasks**
5. **MUST propose workflows to user before finalization**
---
## Workflow
### Phase 1: Analysis
**STOP! Before proceeding, you MUST:**
1. Read `references/analysis-guide.md` completely
2. Only then proceed with the steps below
**Phase 1 Steps:**
1. **Extract TOC and outline ONLY** (DO NOT read full book content)
```bash
# Count total lines
wc -l book.md
# Extract headers/TOC - THIS IS ALL YOU NEED
grep -E "^#{1,3} " book.md
```
2. **Identify knowledge categories from outline**
- Core principles/philosophy
- Rules and guidelines
- Examples (good vs bad)
- Patterns and anti-patterns
- Checklists and quick references
3. **Define use cases**
- Who will use this skill?
- What tasks will they perform?
- What questions will they ask?
4. **Ask user to confirm** the identified categories and use cases before proceeding
---
### Phase 2: Planning
**STOP! Before proceeding, you MUST:**
1. Read `references/extraction-patterns.md` completely
2. Read `references/file-templates.md` completely
3. Only then proceed with the steps below
**Phase 2 Steps:**
1. **Design file structure with required files per category**
Each category MUST contain these 3 basic fi