employment-law-ops
Turn an events JSON list (date + description per event) into a sorted chronological markdown table suitable for attaching to demand letters or filing as an exhibit. Use when assembling a factual timeline for an employment matter. Practice-management tooling, not legal advice.
$ skillbank install employment-law-ops@1.0.0 # pins exactly 1.0.0 · README + changelog included
Employment Law Ops
Overview
Practice-management tooling, not legal advice. Verify all deadlines, fees, and procedures against your jurisdiction's current rules.
Building the timeline for a demand letter or filing is formatting work, not analysis: dates arrive out of order in emails, texts, and personnel files, and the exhibit needs them sorted, numbered, and dated cleanly. This skill reads a JSON array of events, validates every date is a real YYYY-MM-DD calendar date, sorts chronologically, and writes a numbered Markdown table (with a Source column when you supply one). Verify every date and fact against source documents — the tool formats exactly what you give it. All data stays local — nothing is uploaded.
Installation
1. Copy the employment-law-ops/ directory anywhere convenient. 2. Make the script executable (Unix):
chmod +x scripts/chronology.py
No pip install needed — standard library only (Python 3.9+).
Configuration
No config files. A sample 6-event timeline ships at references/samples/events.json.
Inputs
| Command / flag | Arguments | Returns | |---|---|---| | chronology.py --in events.json --out chronology.md [--title "..."] | JSON array of {"date": "YYYY-MM-DD", "description": "...", "source": "..." (optional)} | Sorted, numbered Markdown table with event range summary |
Invalid dates (including impossible ones like 2026-02-30), empty descriptions, or malformed JSON produce a clear stderr message and a nonzero exit — never a traceback.
Worked example
Practice-management tooling, not legal advice. Verify all deadlines, fees, and procedures against your jurisdiction's current rules.
Sample input (references/samples/events.json) — six events in a retaliation timeline, deliberately out of order:
[
{"date": "2026-06-02", "description": "Filed written complaint about unpaid overtime with HR", "source": "email to HR, 9:41 AM"},
{"date": "2026-04-15", "description": "Hired as shift supervisor, $24/hr", "source": "offer letter"},
{"date": "2026-07-10", "description": "First written warning issued, citing 'attitude'", "source": "personnel file"},
{"date": "2026-05-20", "description": "Requested overtime records from payroll; request denied verbally", "source": "contemporaneous notes"},
{"date": "2026-08-01", "description": "Terminated, stated reason 'restructuring'", "source": "termination letter"},
{"date": "2026-06-25", "description": "Asked coworker to corroborate overtime hours", "source": "text messages"}
]
Run it:
$ ./scripts/chronology.py --in references/samples/events.json --out /tmp/chronology.md --title "Chronology of Retaliation"
wrote 6-event chronology -> /tmp/chronology.md
Output (/tmp/chronology.md) — events sorted and numbered, disclaimer top and bottom:
# Chronology of Retaliation
| # | Date | Event | Source |
|---|---|---|---|
| 1 | 2026-04-15 | Hired as shift supervisor, $24/hr | offer letter |
| 2 | 2026-05-20 | Requested overtime records from payroll; request denied verbally | contemporaneous notes |
| 3 | 2026-06-02 | Filed written complaint about unpaid overtime with HR | email to HR, 9:41 AM |
| 4 | 2026-06-25 | Asked coworker to corroborate overtime hours | text messages |
| 5 | 2026-07-10 | First written warning issued, citing 'attitude' | personnel file |
| 6 | 2026-08-01 | Terminated, stated reason 'restructuring' | termination letter |
**6 events**, 2026-04-15 to 2026-08-01.
Version history
Changelog
1.0.0 — 2026-09-27
- Initial release: scripts/chronology.py — sorted chronological markdown table from an events JSON; sample 6-event timeline in references/samples/events.json.