chronology

Extract dated events from litigation documents into a merged Turkish chronology.

100|16|Updated May 13, 2026
One-click install
npx skills add https://github.com/ZekaiSuni/claude-for-legal-turkish --skill chronology-zekaisuni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chronology
Source: https://github.com/ZekaiSuni/claude-for-legal-turkish/tree/main/litigation-legal/skills/chronology
Command: npx skills add https://github.com/ZekaiSuni/claude-for-legal-turkish --skill chronology-zekaisuni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns declared litigation inputs into a clear, date-based chronology while preserving evidentiary discipline, avoiding unsourced facts, and highlighting risks like missing proof or deadline impacts.

Core Features & Use Cases

  • Dava teorisine bağlı kronoloji üretimi: Dated events are extracted and tagged to the relevant matter theory layer (critical/relevant/background).
  • Duplicate merging + evidence fidelity: Events are merged when repeated and events without a supporting source are not treated as certain facts.
  • KVKK/kişisel veri uyarısı: Personal data, special categories, and sensitive third-party information are flagged and minimized in outputs.
  • Deadline and risk notes: Adds a deadline effects section (limitation/response/mediation/appeal/enforcement) without guessing trigger dates.

Quick Start

Ask it to generate a working chronology for your matter using the attached pleadings and evidence files, for example: Provide the chronology for the matter slug "acme-co-vs-xyz" in working format using your uploaded documents.

Frequently Asked Questions about chronology

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

FAQPage Schema
How do I build a litigation chronology from multiple case documents?

The Skill builds a litigation chronology by extracting dated events from declared uploads and pleadings, applying deduplication, importance tagging, and KVKK privacy flagging to produce a sourced timeline aligned with your case theory.

What is the best way to track deadline risks in a Turkish litigation timeline?

The best way to track deadline risks is generating a timeline that adds notes for limitation, response, mediation, appeal, and enforcement impacts. This Skill extracts dated events and flags deadline risks without guessing trigger dates.

Can I generate a chronology that complies with KVKK privacy requirements?

Yes, you can generate a KVKK-compliant chronology. The Skill flags personal data, special categories, and sensitive third-party information during document extraction, then minimizes these details in the final timeline output to maintain privacy compliance.

How does duplicate merging work when extracting events for case management?

Duplicate merging works by identifying repeated dated events across multiple uploaded pleadings and records, combining them into single timeline entries. The Skill preserves evidentiary discipline by refusing to treat unsourced events as certain facts.

Are limitations applied to unsourced facts in a generated litigation timeline?

Yes, limitations are applied to unsourced facts. The Skill refuses to assert unsourced facts as certainty in the chronology, preserving evidentiary discipline by only treating events with supporting source documents as verified timeline entries.

Does litigation chronology generation work without declared source documents?

No, litigation chronology generation requires declared source documents and uploads to extract dated events. The Skill maintains evidentiary discipline by refusing to assert unsourced facts as certainty, requiring explicit inputs for accurate timeline construction.