bible-keeper

Consolidate story artifacts into a Markdown show bible with changelog tracking.

30|4|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/kaigani/codeywood --skill bible-keeper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bible-keeper
Source: https://github.com/kaigani/codeywood/tree/main/skills/core/bible-keeper
Command: npx skills add https://github.com/kaigani/codeywood --skill bible-keeper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill consolidates all disparate story artifacts into a single, authoritative living document, the SHOW_BIBLE.md, ensuring consistency and providing a clear overview of the project's canon.

Core Features & Use Cases

  • Consolidated Reference: Integrates character sheets, relationship maps, episode beats, and scripts into one master document.
  • Change Tracking: Maintains a changelog for all updates to the bible.
  • Consistency Monitoring: Actively checks for and flags contradictions in character details, timelines, and relationships.
  • Use Case: After a new character sheet is finalized, the Bible Keeper automatically updates the 'Characters' section of the SHOW_BIBLE.md, adds a changelog entry, and verifies the character's age against the established timeline.

Quick Start

Update the show bible with the latest character sheets and relationship map.

Frequently Asked Questions about bible-keeper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain story bible consistency across multiple character sheets and episode scripts?

A consolidated story bible solves inconsistency by integrating character sheets, relationship maps, and episode scripts into one master document. It actively monitors for contradictions in character details, timelines, and relationships across all integrated story elements.

What is the best way to track changes in a project's story canon documentation?

Tracking changes in story canon documentation requires a living document with an integrated changelog. This approach logs all updates to character sheets and episode beats, ensuring every modification to the project's canon is recorded and visible.

Do I need Python to generate a markdown story bible from character sheets?

Yes, Python is required to generate a markdown story bible from character sheets. The consolidation process relies on Python for file processing and markdown generation to integrate disparate story artifacts into the master document.

How does a story bible check for timeline and relationship inconsistencies?

A story bible checks for timeline and relationship inconsistencies by actively monitoring integrated character details against established episode beats. It verifies a character's age against the timeline when their sheet is finalized and flags contradictions.

Can I integrate relationship maps and episode beats into one master story document?

Yes, you can integrate relationship maps and episode beats into one master story document. This consolidation creates an authoritative reference that provides a clear overview of the entire project's canon in a single file.