菜单
Use when users say "build a chronology", "make a timeline", "what happened when", "chronology from disclosure", "source the key events", or need legal documents, correspondence, pleadings, witness evidence, or disclosure materials turned into a sourced event chronology.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ThomasMoreAI/legal-skills-open --skill building-chronologies命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | building-chronologies |
| title | building-chronologies |
| description | Use when users say "build a chronology", "make a timeline", "what happened when", "chronology from disclosure", "source the key events", or need legal documents, correspondence, pleadings, witness evidence, or disclosure materials turned into a sourced event chronology. |
| author | LegalQuants |
| author_url | https://github.com/LegalQuants/lq-skills/tree/main/skills/building-chronologies |
| license | Apache-2.0 |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | litigation |
| language | en |
| tags | ["chronology","timeline","evidence","disclosure","source-attribution"] |
Do not use this skill to fill gaps from memory. A chronology is only as reliable as its sources.
Audience: litigators, trainees, paralegals, and litigation-support teams building first-pass chronologies for lawyer review.
Work shape: bounded extraction with accretive judgment. The skill extracts dated events from sources, then applies judgment to de-duplicate, flag conflicts, and surface gaps. It does not decide what happened.
privilege_review and do not include it in an externally shareable chronology without lawyer approval.This skill works in three modes:
If documents cannot be retrieved or supplied, do not infer events from model memory. Mark missing periods, missing sources, and source requests explicitly.
Confirm:
If source coverage is thin, say so before drawing conclusions.
For each source, extract only events with a reliable date or date range:
Each event should include:
dateactoreventsourcesource_identifier, such as Bates number, file name, email metadata, exhibit number, bundle tab, or pathquoteconfidenceissue_tagsnotesUse ISO dates where possible. If only month or year is known, preserve that uncertainty.
Distinguish event_date from document_date and date_extracted_from. Do not use file metadata as the event date unless the metadata itself is the fact being recorded.
Use these confidence values:
high - contemporaneous source directly states the event and date.medium - source supports the event, but date, actor, or context needs checking.low - event is inferred from incomplete material.date_uncertain - event happened, but exact date is unclear.source_conflict - sources disagree materially.Use the event confidence and date_certainty together. High confidence requires a contemporaneous source and clear event date. Medium confidence means the event is sourced but date, actor, or context needs checking. Low confidence means the entry is inferred, pleaded-only, or source-limited. source_conflict always requires lawyer review before advocacy use.
When multiple documents describe the same event:
When sources conflict, classify the entry as source_conflict or needs_lawyer_review.
After extraction, list:
Gaps are part of the work product. Do not hide them.
Recommended table:
| Date | Date Certainty | Actor | Event | Source Identifier | Source Date | Quote | Confidence | Tags | Notes | |---|---|---|---|---|---|---|---|
Then add:
Only produce a narrative statement of facts after the working chronology is complete. The narrative must:
Stop and route to the responsible lawyer when there is suspected privilege, irreconcilable source conflict on a key event, an unfamiliar jurisdiction or procedural regime, OCR/source quality too poor to support extraction, or a user asks for merits inference rather than chronology mapping.
Build a working chronology from this folder of correspondence and pleadings. Cite every event to a source, quote the key words, and list gaps separately.
For a compact output pattern, see examples/output.md.
For event/date discipline, significance tags, and gap handling, see references/chronology-model.md.