entity-tracker

Extract narrative entities into a persistent ENTITY_STATE.yaml from manuscript chapters.

92|28|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/felipelobomotta-blip/book-genesis-v4 --skill entity-tracker-felipelobomotta-blip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: entity-tracker
Source: https://github.com/felipelobomotta-blip/book-genesis-v4/tree/main/skills/optional/entity-tracker
Command: npx skills add https://github.com/felipelobomotta-blip/book-genesis-v4 --skill entity-tracker-felipelobomotta-blip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Entity-tracker eliminates continuity drift by maintaining a single, persistent YAML “source of truth” for characters, locations, objects, timeline, organizations, and world rules across the manuscript.

Core Features & Use Cases

  • Builds persistent entity memory: Creates ENTITY_STATE.yaml from foundation.md, outline.md, and chapter files.
  • Updates incrementally: Processes only specified chapters to extend or revise tracked entities without rebuilding everything.
  • Flags contradictions without fixing them: Detects conflicting facts and records them as unresolved conflicts or knowledge gaps for downstream continuity review.

Quick Start

Use the entity-tracker skill in BUILD mode to generate ENTITY_STATE.yaml from your existing foundation.md, outline.md, and all current chapters.

Frequently Asked Questions about entity-tracker

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

FAQPage Schema
How do I track manuscript entity continuity and prevent narrative drift?

Track manuscript entity continuity by maintaining a persistent structured ENTITY_STATE.yaml that extracts and tracks characters, locations, objects, and world rules. It serves as a single source of truth to eliminate continuity drift across long-form book production.

How do I extract and update narrative entities from specific book chapters?

Extract and update narrative entities by processing specified manuscript chapters incrementally in UPDATE mode. This extends or revises tracked entities in the YAML state file without rebuilding the entire entity history from scratch.

Can I use a YAML schema to manage worldbuilding rules and timeline entries?

Yes, you can manage worldbuilding rules and timeline entries using a YAML schema. The process requires strict YAML schema conformance to record narrative entities, timeline entries, objects, and world rules extracted from manuscript chapters.

What's the best way to detect continuity conflicts and knowledge gaps in a manuscript?

Detect continuity conflicts and knowledge gaps by flagging contradictory facts during chapter extraction. The system records these as unresolved conflicts or knowledge gaps for downstream continuity review without automatically fixing them.

How do I build a persistent source of truth for characters and locations from existing manuscript files?

Build a persistent source of truth by running the entity-tracker in BUILD mode. It generates the ENTITY_STATE.yaml file by extracting and merging narrative data from your existing foundation.md, outline.md, and all current chapter files.

Does entity tracking work for incremental chapter revisions during long-form book production?

Yes, entity tracking works for incremental chapter revisions during long-form book production. The system applies chapter-scoped extraction with deterministic sources and incremental merge logic to update the YAML state without processing the entire manuscript.