analise-consistencia-narrativa-tempo-e-eventos

Validates causal and temporal consistency of branching story timelines using event graphs.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/Ryanzucchi/Eldritch_Lich --skill analise-consistencia-narrativa-tempo-e-eventos-ryanzucchi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analise-consistencia-narrativa-tempo-e-eventos
Source: https://github.com/Ryanzucchi/Eldritch_Lich/tree/main/.agents/skills/analise-consistencia-narrativa-tempo-e-eventos
Command: npx skills add https://github.com/Ryanzucchi/Eldritch_Lich --skill analise-consistencia-narrativa-tempo-e-eventos-ryanzucchi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writers working with branching plots, alternate timelines, and parallel story universes often introduce plot holes such as conflicting character ages, impossible event sequences, or contradictory outcomes when merging branches. This Skill detects those causal and temporal collisions before they corrupt the main storyline. ## Core Features & Use Cases - Branch Mapping: Creates event-graph branches that inherit state from a parent node up to the divergence point. - Temporal Reasoning (NoT): Reconstructs the chronological causal chain of each branch step by step to verify absolute time, character ages, and event ordering. - Merge Collision Detection: Compares two branches (e.g., version A vs. version B) and flags causal incompatibilities, such as a character using an object that was destroyed in the other branch. - Visual Signaling: Highlights conflicting edges in red on the timeline and plot map, with a limit of 3 active branches to avoid cognitive overload. - Use Case: An author drafts an alternate timeline where the protagonist dies in 1118, then tries to merge it with a branch where the protagonist signs a treaty in 1120. The Skill blocks the merge and reports the causal collision. ## Quick Start Ask the assistant to compare the main timeline with the alternate branch and report any temporal or causal conflicts before merging.

Frequently Asked Questions about analise-consistencia-narrativa-tempo-e-eventos

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

FAQPage Schema
How do I detect plot holes when merging two story timelines?▼

Compare the branches event by event using a causal chain reconstruction. The Skill checks absolute time accumulation, character ages at convergence points, and goal conflicts, then reports collisions such as a character acting after their death in the merged timeline.

What is an event graph for narrative consistency checking?▼

An event graph (GraphStory) models story events as nodes with causal edges, allowing branches to inherit state from a parent node up to the divergence point. This structure lets the system trace chronological chains and detect contradictions across parallel plot versions.

Can this approach handle multiple alternate universes at once?▼

Yes, but visualization is limited to 3 active branches simultaneously by default (MAX_ACTIVE_BRANCHES) to avoid cognitive overload and rendering memory issues. Inactive branches are collapsed and their consistency processing is paused until focused.

When should I not use branching timeline validation?▼

Skip it for purely linear, single-path novels with no logical branches, and for spelling or style checking, which are outside its scope. It is designed specifically for causal and temporal validation of ramified plots.

What are the limitations of automated timeline merging for stories?▼

Automated merging of complex temporal graphs is experimental and prone to state bugs. The recommended v1 fallback treats branches as independent project clones, disabling automatic merging and dynamic state inheritance so authors manage versions manually.