Individual skill

court-closeout-reconciler

Prepare clerk-ready JSON court closeout, disposition register, payment plan, probation referral, and license/payment order packets from local payloads plus a Court Operations Portal. Use for criminal or traffic matters requiring reconciliation of case/citation status, charges, docket entries, fee schedules, payment policies, forms, financial petitions, placeholders, exclusions, and batch totals against an answer_template.json.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_018/fewshot/deepagents/fewshot_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 Closeout Reconciler

## Core Workflow

1. Read the user prompt, then read `input/payloads/answer_template.json` before drafting any output. Treat the template as the contract for top-level keys, enum values, null handling, date formats, currency formats, and sorting.
2. Inventory and read every file in `input/payloads/`. Parse JSON/CSV as structured data, and use Markdown notes as evidence with headings tied to target matters.
3. Identify target matter keys from the prompt and payloads: case numbers, citation numbers, petition IDs, jurisdiction codes, hearing dates, disposition dates, and named forms.
4. Query the Court Operations Portal named in the prompt, or read `environment_access.md` if that file is present and the prompt uses a placeholder base URL. Use only the listed task-environment endpoints.
5. Reconcile evidence matter by matter. Record conflicts and exclusions explicitly when the requested answer shape provides fields for them.
6. Assemble JSON only. Do not include Markdown, comments, citations, or explanatory prose outside fields requested by the template.

## Portal Collection

Use portal data to verify, not to replace stronger local hearing facts. Useful endpoints commonly include: