building-chronologies

Extract dated events from legal documents into sourced chronology tables with flagged conflicts and gaps.

46|25|Updated May 7, 2026
One-click install
npx skills add https://github.com/LegalQuants/lq-skills --skill building-chronologies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: building-chronologies
Source: https://github.com/LegalQuants/lq-skills/tree/main/skills/building-chronologies
Command: npx skills add https://github.com/LegalQuants/lq-skills --skill building-chronologies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

A lawyer needs a reliable, source-attributed chronology that answers what happened when, based strictly on supplied legal materials rather than guesswork.

Core Features & Use Cases

  • Sourced event extraction: Converts documents (e.g., emails, pleadings, correspondence, witness evidence, disclosure exports) into a structured sequence of dated events with supporting quotes and identifiers.
  • De-duplication and conflict detection: Merges repeated events while preserving multiple source trails, flags contradictions, and marks disputed or low-confidence entries for lawyer review.
  • Gap and verification support: Produces explicit lists of missing periods, missing counterparties/custodians, referred-but-unsupplied items, and verification checklists to guide further document requests.
  • Multiple output shapes: Generates a working chronology plus optional witness-specific, issue-specific, or statement-of-facts variants while preventing unverified inference.

Quick Start

Use building-chronologies to create a working chronology from the attached disclosure and correspondence bundle, citing each event with a quote, source identifier, and confidence, and listing gaps where key sources are missing.

Frequently Asked Questions about building-chronologies

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

FAQPage Schema
How do I build a legal chronology from disclosure documents and emails?

Building a legal chronology involves converting bundles of disclosure exports and emails into a structured sequence of dated events with mandatory source identifiers, quotes, and confidence scores.

What is source conflict detection in litigation timeline building?

Source conflict detection in litigation timeline building flags contradictions and disputed entries across evidentiary materials, marking low-confidence events for lawyer review while preserving multiple source trails during de-duplication.

How do I identify missing evidence and source gaps in a legal chronology?

Identifying missing evidence in a legal chronology produces explicit lists of missing periods, referred-but-unsupplied items, and missing counterparties, generating verification checklists to guide further document requests.

Can I convert a sourced chronology into a statement of facts narrative?

Yes, you can convert a sourced chronology into a statement-of-facts narrative, generating witness-specific or issue-specific variants while preventing unverified inference from the underlying evidentiary materials.

Does legal timeline building work with pleadings and witness statements?

Yes, legal timeline building works with pleadings, witness statements, correspondence, and disclosure exports, extracting dated events from these evidentiary materials to support litigation and investigation workflows.

What are the limitations of automated chronology generation for litigation support?

Automated chronology generation requires strict event-date discipline and prevents unverified inference, meaning it cannot guess missing dates and relies entirely on supplied legal materials rather than external guesswork.