agentleFS
Sign inStart free
ThomasHoussinThomasHoussin/Claude-Book/.claude/skills/book-analyzer/SKILL.md

book-analyzer

Skill112 starsChanged 10 months agoMITView on GitHub

Analyze source books to extract structured bible files (style, characters, structure, universe). Use when analyzing novels, stories, or any narrative text to create a reusable writing bible for style matching and story generation.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. tuan3w/obsidian-vault-agent★ 39same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create all output files following templates in bible/.

    line 63
  2. Distinctive:

    Every trait, pattern, or rule must be supported by:

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Book Analyzer

Extract structured bible files from source books for the writing framework.

Quick Start

# Analyze a single book
Analyze analysis/src/[book].txt

Output structure in analysis/output/[book-slug]/:

├── style.md
├── structure.md
├── characters/
│   └── [character].md
└── universe/
    └── [location].md

Workflow

1. Read source completely

Load the full text, note overall structure and length.

2. Extract style

  • Identify POV (first/third limited/omniscient)
  • Identify tenses (primary, secondary)
  • Sample 50 sentences for average length
  • List 20-30 characteristic vocabulary items
  • List dialogue tags used
  • Estimate dialogue-to-prose ratio
  • Note description techniques

3. Extract characters

For each significant character:

  • Identity (name, age, role)
  • Physical description
  • 3-5 core personality traits with evidence
  • 5-10 dialogue quotes showing voice
  • Relationships mapped

4. Extract structure

  • Map acts (setup/development/climax/resolution)
  • Note chapter count and length range
  • Analyze chapter openings and endings
  • Identify recurring patterns
  • Track mystery mechanics if applicable

5. Extract universe

For each significant location:

  • Physical description with quotes
  • Atmosphere and sensory details
  • Story function

6. Generate files

Create all output files following templates in bible/.

Evidence-Based Extraction

Every trait, pattern, or rule must be supported by:

  • Direct quotes (with chapter reference)
  • Quantitative data (averages, counts, percentages)

Bad: "Claude is stubborn" Good: "Claude is stubborn (Ch.2: refuses to answer to 'Claudine'; Ch.5: insists on leading despite danger)"

Output Format

Follow templates exactly:

  • bible/style.md → output/[book]/style.md
  • bible/characters/_template.md → output/[book]/characters/[name].md
  • bible/universe/_template.md → output/[book]/universe/[name].md
  • bible/structure.md → output/[book]/structure.md

For detailed extraction checklists, see references/extraction-guide.md.

Output Language

French (for extracted content and quotes) English (for metadata and structural annotations)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free