Menu

Individual skill

court-closeout-reconciliation

Reconcile court closeout packets into schema-valid JSON using local payloads and Court Operations Portal records. Use for criminal sentencing closeouts, traffic violation dispositions, payment petitions, installment plans, probation referrals, license suspension orders, fee schedule and payment-policy checks, unsupported-fee exclusions, placeholder handling, docket/register actions, and batch totals.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_018/fewshot/naive/fewshot_attempt_02/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
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 skill when a task asks for a clerk-ready JSON closeout packet based on local court materials plus a Court Operations Portal. The output must follow the provided `answer_template.json`, not a prose summary.

## Workflow

1. Read the prompt, `answer_template.json`, and every local payload.
2. Identify the target matters, jurisdiction, hearing/disposition dates, named portal endpoints, required sort rules, enums, placeholder text, and currency/date formatting rules.
3. Resolve the portal base URL from the task materials. Fetch each endpoint named in the prompt. If endpoint filtering is available, query by target case, citation, petition, jurisdiction, or form family; otherwise fetch and filter locally. Use `/api/search` to cross-check identities, stale references, or records not obvious from endpoint names.
4. Build a source table per matter:
   - local hearing or sentencing notes
   - petition or financial worksheet data
   - portal case/citation/charge/docket records
   - current fee schedules and payment policies