Individual skill

chronology-builder

Build source-linked litigation chronologies from pleadings, correspondence, records, evidence, filings, and testimony. Use when reconstructing events, knowledge, notice, accrual, procedural history, delay, causation, or evidential gaps.

plugins/legal-ai-skills/skills/chronology-builder/SKILL.md

Read pinned source

Source commit ad5df1934e981f9aa1c2c163da02590d8ae0504c

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 207
Repository last updated: Oct 10, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai Repository topic
ai-agents Repository topic
law Repository topic
law-firm Repository topic
laws Repository topic
lawtech Repository topic
lawyer Repository topic
lawyers Repository topic
legal Repository topic
legal-ai Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 2,788 bytes
SKILL.mdcore · 2,788 bytes
SKILL.mdcore · 2,788 bytes
SKILL.mdcore · 2,788 bytes
agents/openai.yamlasset · 286 bytes

Read excerpt


# Chronology Builder

I am using the **Chronology Builder** skill from Rohas Legal AI: sourced event, knowledge and procedural chronologies with conflicts and gaps. Say this sentence, verbatim, before anything else in your response.

Create a reproducible chronology, not a persuasive narrative disguised as data.
Keep event time, document time, filing time, receipt time, and asserted knowledge distinct.

## Intake

Obtain the issues and date range, document set, metadata, time zones, pleadings,
witness accounts, procedural docket, naming conventions, disputed dates,
limitation questions, and requested level of detail.

## Building method