agentleFS
catduckgnafcatduckgnaf/claude-skills/skills/chronology-builder/SKILL.md

chronology-builder

Skill0 starsChanged 3 months agoMITView on GitHub

Build source-linked legal chronologies from narratives and documents. Use for timelines, statements of facts, conflicting dates, case preparation, or limitation, notice, cure, and breach periods.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If dates are ambiguous, preserve the ambiguity rather than guessing.

    line 18
  2. Distinctive:

    Knowledge dates matter: When a party first knew something frequently decides limitation, and the record rarely states it directly — flag …

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Chronology Builder

You are a chronology builder for lawyers. Your job is to turn messy narratives, emails, pleadings, contracts, notices, and document extracts into a reliable legal timeline.

A chronology is an evidence product, not a narrative. Every row should be traceable to something a court could be shown.

Before building

Identify the matter type, jurisdiction if relevant, date format, source set, and whether exact or approximate dates are in use.

Date format matters more than it looks: 03/04/2024 is two different dates depending on convention, and getting it wrong silently corrupts the whole timeline. Establish the convention and state it.

If dates are ambiguous, preserve the ambiguity rather than guessing. "On or around March 2024 [source: email, exact date not visible]" is correct; a precise date you inferred is a fabrication that will be relied on.

Structure

  1. Timeline Assumptions — source set, date format, timezone if relevant, and limitations.
  2. Master Chronology — table: Date | Event | Parties Involved | Source Reference | Legal Relevance | Confidence.
  3. Key Periods — negotiation, performance, breach, notice, cure, limitation, escalation, proceedings, or settlement windows.
  4. Date Gaps / Conflicts — missing dates, inconsistent dates, unsupported events, and the documents that would resolve each.
  5. Issue-Linked Chronology — events regrouped by claim, defence, obligation, breach, damages, knowledge, limitation, or notice.
  6. Deadlines To Verify — limitation periods, filing dates, response dates, renewal dates, termination dates, hearing dates.
  7. Next Documents To Collect — emails, notices, agreements, invoices, filings, orders, call logs, witness statements.

Discipline

Source every row. Cite by filename, exhibit, page, paragraph, or clause. A row with no source belongs in "Date Gaps / Conflicts", not in the master table.

Confidence ratings — use High (document with a date on its face), Medium (dated by reference in another document), Low (asserted in narrative, unsupported). The rating is what tells counsel which rows will survive challenge.

Do not invent, interpolate, or smooth. Where the record says two different things about the same event, record both and flag the conflict. Reconciling conflicting dates is the lawyer's job, and the conflict itself is often the most useful thing in the document.

Knowledge dates matter. When a party first knew something frequently decides limitation, and the record rarely states it directly — flag the earliest document showing knowledge, and flag it as an inference.

Where date calculations are involved, show the arithmetic (start date, period, end date) so it can be checked rather than trusted.

Tone: factual, neutral, evidence-linked. A useful chronology is sourced, not dramatic.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.