Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lawve-ai/chronology-builder-andrew-bird
Builds a litigation chronology from the disclosure bundle itself — every entry attributed to its source document, behind a CPR 31.22 implied-undertaking check, because documents disclosed in English proceedings may only be used for those proceedings. Adds a privilege screen and case-theory significance tagging, so the output is court-facing work product, not a loose timeline.
Passed 21 of 22 test cases with the skill, and 6 of 22 without it.
and 19 more in the full report
15 fixed6 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
An event in the chronology describes oral remarks that might constitute a repudiatory breach, but the legal characterisation remains uncertain. Which exact marker tag must be attached?
| Checked | Without skill | With skill |
|---|---|---|
| Applies the tag [UNCERTAIN — legal characterisation]. | Missed | Passed |
The instructions your model reads when the skill loads.
The host workspace enforces the hard gate (matter-slug match against the proceedings reference, privilege posture). If this skill is running, that gate has already passed — this check does not replace it. The skill still performs its own check below and refuses or flags if misuse is indicated; it is not the enforcement.
Before building from any document obtained through standard or extended disclosure in English / Welsh proceedings, confirm the use is permitted:
CPR 31.22(1): A party to whom a document has been disclosed may use the document only for the purpose of the proceedings in which it is disclosed, except where: (a) the document has been read to or by the court, or referred to, at a hearing held in public; (b) the court gives permission; or (c) the party who disclosed the document and the person to whom the document belongs agree.
Misuse of disclosed documents (using them for a different matter, a different claim, a commercial purpose, or external publication) is a contempt of court.
Confirm before extracting from any source that may have come through disclosure:
If the answer indicates "different proceedings" or "external use", refuse to build until permission, the parties' agreement, or open-court reference is established — the implied undertaking would otherwise be breached. Flag prominently in the output header: CPR 31.22 — use restricted to current proceedings unless permitted, agreed, or read in open court.
Equivalent overlay in disclosure pilot / PD 57AD jurisdictions (Business and Property Courts): the implied undertaking applies; PD 57AD does not displace it.
Documents may be subject to legal professional privilege (advice and litigation privilege), common-interest privilege, joint-defence privilege, without-prejudice protection. Extracting privileged content into a chronology that is later shared can risk waiver.
Determine the privilege posture before extracting. Infer from source type (cleared production folder → A; mixed mailbox / dataroom → B; ad-hoc bundle with no review history → B by default; explicit instruction to pause → C). Surface the inferred posture in the output header so counsel can override.
priv: ok / priv: flag / priv: review. SoF variant filters flagged entries by default.test cases passed, vs 6 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.