Menu

Individual skill

court-closeout-reconciliation

0upvotes

Reconcile court hearing notes, portal records, fee schedules, payment policies, and form metadata into strict JSON closeout packets for criminal, traffic, probation, and payment-plan tasks. Use when a task asks to resolve conflicting court data, compute fees or totals, hold unfinalized matters, and fill a schema-driven answer template.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_018/reflect-3/reflect-3_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
Yes
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 Closeout Reconciliation

Use this workflow whenever a task asks for a structured court closeout, payment-plan packet, probation packet, or sentencing reconciliation.

## Workflow

1. Read the prompt, answer template, and all attached local payloads.
2. Pull the portal records needed to verify identity, status, charges, docket text, fees, policies, petitions, and form fields.
3. Resolve conflicts in this order:
   - signed order, hearing notes, and docket text
   - current portal case, citation, charge, and docket records
   - current fee schedule, payment policy, and form metadata
   - queue, worksheet, draft, or stale carry-forward values
4. Keep only values supported by the controlling source. Do not guess names, contact details, account numbers, license numbers, or fees.