Agent skill

book-analyzer

Analyze a book (EPUB/PDF) and generate detailed chapter-by-chapter notes with extracted key concepts. Use when given a book file path to process.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill book-analyzer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 18 KB
Bundled scripts: none
Allowed tools: BashReadWriteEditGrepGlobAgentTodoWrite
Path: skills/analysis/book-analyzer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<Purpose> Full autonomous analysis of book files (EPUB/PDF) into structured notes. Extracts text, detects chapters, analyzes each chapter via parallel agents, synthesizes across chapters, and optionally integrates into an Obsidian vault with wikilinks and extracted Term notes. </Purpose> <Use_When> - User provides a path to an EPUB or PDF book file - User says "analyze this book", "process this book", "read this book" - User wants structured notes from a book-length document (20+ pages) </Use_When> <Do_Not_Use_When> - Short documents under 20 pages — use /paper or /process instead - User wants to read or search specific sections — just use Read tool directly - User wants EPUB output from markdown — wrong direction - URL-only input with no file on disk — use /research instead </Do_Not_Use_When> <Why_This_Exists> Book notes that merely transcribe content are useless — the value is in synthesis. Most book notes in a vault end up sparse because processing a full book manually is exhausting. This skill automates the mechanical work (extraction, splitting, formatting) while delegating the intellectual work (synthesis, assessment, connections) to specialized agents with strict quality con

What's inside
Steps it walks through
  1. Stage 1: PARSE ARGUMENTS AND EXTRACT
  2. Stage 2: STRUCTURE
  3. Stage 3: ANALYZE (parallel, file-based)
  4. Stage 4: SYNTHESIZE + SECTION WRITE (parallel)
  5. 4a. Book Synthesizer (Opus)
  6. 4b. Section Writers (Sonnet, one per batch)
  7. Stage 4.5: ASSEMBLE FINAL NOTE (lightweight concatenation)
  8. Stage 4.6: VERIFY FINAL NOTE (quality gate)
  9. Stage 5: INTEGRATE
  10. If in vault context (Obsidian):
  11. If NOT in vault context (plain markdown):
Ships with 1 file
  • metadata.json
Commands it runs
Find skill directory — check common locations
for dir in .claude/skills/book-analyzer ~/.claude/skills/book-analyzer; do
if [ -f "$dir/scripts/extract_epub.py" ]; then SKILL_DIR="$dir"; break; fi
done
python3 "$SKILL_DIR/scripts/extract_epub.py" "INPUT_PATH" "$WORK_DIR"
mkdir -p "$WORK_DIR/analyses"
mkdir -p "$WORK_DIR/sections"
python3 .claude/scripts/create-note.py book "{Title}" author="{Author}" year={YEAR}
More from claude-skill-registry
All skills →
About this skill
What does the book-analyzer skill do?

Analyze a book (EPUB/PDF) and generate detailed chapter-by-chapter notes with extracted key concepts. Use when given a book file path to process.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill book-analyzer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going