Individual skill

reconcile-court-closeout

Reconcile court closeout and post-sentencing packet tasks from hearing notes, clerk memos, worksheets, intake packets, and Court Operations Portal data. Use when the work asks for schema-driven JSON outputs covering dispositions, fee reconciliation, payment plans, probation referrals, license-suspension orders, docket/register entries, or exclusion of stale or unsupported charges.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_018/fewshot/fewshot_attempt_01/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.

agent Repository topic
ai Repository topic
benchmark Repository topic
llm Repository topic
self-evolving Repository topic
self-learning Repository topic
skills Repository topic
operations Derived category
data Derived category
productivity Derived category
productivity-notes Derived category

Files and excerpt

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

Browse files

SKILL.mdcore · 2,870 bytes
SKILL.mdcore · 2,870 bytes
agents/openai.yamlasset · 278 bytes

Read excerpt


# Court Closeout Reconciler

## Workflow

1. Read the prompt, answer template, and every payload completely before deciding anything.
2. Inventory the required top-level keys, enums, sort rules, and precision rules from the template first.
3. Read `environment_access.md` for the running base URL, then use only the portal endpoints the prompt calls for.
4. Use portal lookups to verify the live record set:
   - `/api/jurisdictions` and `/api/citations` for citation-based tasks, court codes, and defendant/violation lookups
   - `/api/cases`, `/api/charges`, `/api/docket-entries` for identity, status, plea, and disposition facts
   - `/api/fee-schedules` and `/api/payment-policies` for current financial rules
   - `/api/forms` for form IDs, labels, and required fields
   - `/api/financial-petitions` for petition intake and budget math
   - `/api/search` when a fact is split across notes, templates, or portal records