Menu

Individual skill

court-packet-reconciliation

0upvotes

Reconcile court closeout, sentencing, traffic, petition, and post-disposition packet materials into strict schema-matched JSON. Use when a task combines hearing notes, docket entries, case files, intake worksheets, petitions, fee schedules, payment policies, form metadata, or portal records and requires conflict resolution, payment-plan math, unsupported-fee exclusion, placeholder handling for missing identifiers, and ordered structured output.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_018/self/self_attempt_02/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Court Packet Reconciliation

## Workflow
1. Read the schema or answer template first. Note required keys, enums, ordering rules, date and currency formats, and any required placeholder text.
2. Read every provided local payload completely. Treat signed orders, entered docket notes, current case records, current fee schedules, payment policies, and form metadata as controlling over drafts, queue exports, scratchpads, or legacy worksheets.
3. If a court portal is provided, verify the matter against the relevant endpoints before finalizing:
   - case, citation, charge, docket, fee schedule, payment policy, form, and search endpoints as available
   - use search only to resolve identifiers or locate the current record
4. Resolve conflicts by source priority:
   - entered judgment, signed order, or docket entry
   - hearing notes or sentencing intake
   - current portal case, charge, fee, policy, and form records
   - local memo, petition, or worksheet
   - draft, archived, stale, or carry-forward values
Back to top