auditoria-global-consistencia-entidades

Detects plot holes by auditing entity continuity across chapters using temporal entity graphs.

Updated Jul 19, 2026

Search Tags:#novel writing #plot holes #nlp #narrative consistency #entity tracking #temporal graph #continuity audit

Ready to run

npx skills add https://github.com/Ryanzucchi/Eldritch_Lich --skill auditoria-global-consistencia-entidades-ryanzucchi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: auditoria-global-consistencia-entidades
Source: https://github.com/Ryanzucchi/Eldritch_Lich/tree/main/.agents/skills/auditoria-global-consistencia-entidades
Command: npx skills add https://github.com/Ryanzucchi/Eldritch_Lich --skill auditoria-global-consistencia-entidades-ryanzucchi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long novels accumulate logical inconsistencies: characters who act after dying, objects used without being owned, and characters who teleport between locations. Manually tracking these across dozens of chapters is error-prone, and pure vector-similarity (RAG) checks miss binary contradictions. ## Core Features & Use Cases - Temporal Entity Graph (GTE): Extracts event triples (subject, action, object, location, narrative time) from chapter text and models them as time-indexed graph edges. - Boolean Consistency Rules: Runs imperative checks for location continuity, inventory possession, and vital status (e.g., dead characters performing actions). - Conflict Propagation & Reporting: Flags inconsistent scenes, propagates the flag to causally dependent scenes, and highlights failures on the author's timeline and wiki. - Use Case: After marking a chapter as complete, the audit detects that Lord Valerius speaks in chapter 12 despite dying in chapter 10, and reports a VITAL_STATUS_VIOLATION with the conflicting scenes. ## Quick Start Ask the assistant to audit the completed chapters of the manuscript for physical and logical continuity conflicts across characters, locations, and items.

Frequently Asked Questions about auditoria-global-consistencia-entidades

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

FAQPage Schema

How do I detect plot holes across multiple novel chapters?▼

Extract event triples (subject, action, object, location, narrative time) from each chapter and load them into a temporal entity graph. Then run boolean rules checking location continuity, item possession, and vital status to flag contradictions like dead characters acting.

Why use a temporal graph instead of RAG for story consistency checking?▼

Vector similarity search treats contradictory facts as semantically similar, so it misses binary conflicts such as a character being dead versus alive. A temporal graph with imperative boolean rules evaluates physical state transitions deterministically.

What consistency rules does narrative entity auditing check?▼

It checks three rule families: location continuity (no teleportation without a travel edge), inventory possession (an item must be owned before use), and vital status (no active verbs from characters recorded as dead at an earlier narrative time).

Can consistency auditing cause false positives with flashbacks?▼

Yes. Actions inside memories, dreams, or flashbacks can trigger false vital-status violations. Mitigate this by modeling scene-type and narrative-time metadata so flashback events are excluded from linear continuity checks.

When should I not run a global consistency audit on a manuscript?▼

Avoid running it during free-form brainstorming drafts where chapter chronology is undefined, and avoid real-time checks while typing. The global graph scan is computationally expensive and should run asynchronously or on chapter completion.