Calendar litigation and arbitration deadlines from a scheduling order. Parses a PDF scheduling order, identifies key dates, computes backward deadlines using the applicable rules (Colorado CRCP, Federal FRCP, or arbitration forum rules for AAA/JAMS), and generates an .ics calendar file for Outlook or Google Calendar import.
SkillScore78Maintained
Automatic
◆Legal & Contracts pack
Last verified 8/16/2026
What it changes
Passed 15 of 19 test cases with the skill, and 9 of 19 without it.
Without skill48%
With skill78%
Checks it passed that the model alone missed
Executes the generate_ics.py script with the --google flag
Marks critical deadlines with triple exclamation marks in the summary presentation
Includes the duration_days key set to integer value 5 on the trial event JSON object
and 5 more in the full report
8 fixed10 passed either way4 still failing1 broke
Pass-rate lift
+30 pp
Tokens
+219%
Agent turns
0%
Response time
-37%
Model gemini-3.6-flashMeasured 8/16/2026v118 of 23 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
For the matter 'Apex Logistics v. Zenith Manufacturing', should calendar entry titles be formatted as 'Discovery Cutoff — Apex Logistics v. Zenith Manufacturing' or 'Apex Logistics v. Zenith Manufacturing — Discovery Cutoff'?
What was checked, without and with the skill
Checked
Without skill
With skill
Formats calendar titles with the matter name placed first before the deadline description
Missed
Passed
case-20 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md393 lines6 filesincludes scripts
Litigation Deadline Calendar
This skill takes a scheduling order (PDF upload), determines the applicable
procedural rules, extracts key dates, computes all backward deadlines, and
generates an .ics calendar file the user can import into Outlook or Google
Calendar.
Quick Start Workflow
Gather information from the user
Parse the scheduling order PDF
Verify the rules are current
Compute deadlines using the scripts
Generate .ics file and deliver to user
Step 1: Gather Information
Ask the user for the following. They may provide some of this upfront; fill
in what you have and ask for the rest.
Required:
The scheduling order PDF (uploaded file)
Matter name (how the user wants it displayed on calendar entries, e.g., "Smith v. Jones Co.")
Proceeding type: litigation or arbitration
If litigation:
Jurisdiction: Try to determine from the scheduling order first. Look for
the court name, case number format, or header to identify the jurisdiction.
Common patterns:
"District Court, ___ County, Colorado" → Colorado
"United States District Court" → Federal
"Superior Court of California" → California
State name in the court caption → that state
If the scheduling order clearly identifies the jurisdiction, confirm it with
the user: "This appears to be a [State] case based on the court name. Can you
confirm?"
If you cannot determine the jurisdiction from the PDF, always ask the user
explicitly. Never guess or default. The tool will raise an error if no
Mandatory external verification workflow for ALL non-trivial factual claims before presenting them as true. This skill MUST be used whenever Claude is asked to research any topic, answer factual questions, provide current information, draft documents containing factual claims, give legal advice or cite legal authority, discuss current events or public figures, provide technical or scientific information, state statistics or data points, or answer ANY question where the answer could have changed