agentleFS
ThomasHoussinThomasHoussin/Claude-Book/.claude/skills/bible-merger/SKILL.md

bible-merger

Skill112 starsChanged 10 months agoMITView on GitHub

Merge multiple book analyses into a unified bible. Use after analyzing several books from a series to consolidate characters, style patterns, and structure into a single canonical reference.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After analyzing multiple books from the same series or author.

    line 19
  2. Distinctive:

    Core traits: keep only if demonstrated in ALL appearances

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Bible Merger

Consolidate multiple book analyses into one canonical bible.

Quick Start

# Merge all analyses
Merge analysis/output/*/ into bible/

When to Use

After analyzing multiple books from the same series or author. The merger:

  • Identifies consistent patterns (→ rules)
  • Tracks character evolution
  • Extracts the author's true voice

Merge Process

1. Inventory sources

List all analysis/output/*/ directories to merge.

2. Merge style

Compare style.md across all sources:

  • Keep: patterns appearing in ALL books
  • Range: metrics with variation (use min-max range)
  • Flag: book-specific vocabulary (note but don't enforce)
  • Pick: best reference excerpts from each

3. Merge characters folder

For each character appearing in multiple books:

  • Core traits: keep only if demonstrated in ALL appearances
  • Evolution: note changes across books
  • Speech: merge dialogue examples, identify constants
  • Relationships: note any evolution

For single-book characters:

  • Include if significant
  • Mark as "source: [book]"

4. Merge structure

Identify the formula:

  • Chapter length range across all books
  • Consistent act structure
  • Patterns appearing in every book

5. Merge universe folder

  • Recurring locations: full treatment, consolidate descriptions
  • Book-specific locations: include with source note
  • Contradictions: later books take precedence

Conflict Resolution

Conflict TypeResolution
Style patternsPrefer most common
Character traitsPrefer shown-in-action over told
FactsPrefer later books
All conflictsDocument: "Sources vary: book-1 says X, book-3 says Y"

Output

Merge report

Generate analysis/merge-report.md:

# Merge Report

## Sources
- [Book 1]: [path]
- [Book 2]: [path]

## Consistency Analysis
- Highly consistent: [list]
- Some variation: [list]  
- Book-specific: [list]

## Character Coverage
- [Character]: appears in [X/Y] books

## Conflicts Resolved
- [Description]: chose [resolution]

Merged bible

Complete bible/ directory with consolidated files.

Output Language

French (for content) English (for report and metadata)

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.