Individual skill

court-closeout-reconciliation

Reconcile a court clerk closeout / post-disposition packet against the Court Operations Portal and emit the exact JSON required by answer_template.json. Use when a task gives you local court payloads (hearing/bench notes, finance queue or worksheet, financial petition + budget, form excerpts, audit memo) plus a Court Operations Portal base URL, and asks for a structured closeout: disposition register, identity/counsel audit, fee reconciliation, installment / extended payment plan, probation & license orders, or a post-sentencing field packet. Handles the AR criminal, OR traffic, and VA post-sentencing variants of these tasks.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_018/fewshot/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 & Post-Disposition Reconciliation

## What these tasks are

A deputy-clerk task. You are handed **local paper-trail materials** (bench/hearing
notes, a finance queue or clerk worksheet, a financial petition + budget, form
excerpts, an audit memo) that are **known to be noisy** — they contain draft
values, stale carry-forwards, bench shorthand, ambiguous counsel labels, and
sticky-note "should we add X fee?" questions. Your job is to **reconcile them
against the authoritative Court Operations Portal** and produce one JSON object
that a clerk could post to the register.

The output shape, keys, enums, ordering, and rounding are dictated by the task's
`input/payloads/answer_template.json`. **That template is the contract** — read it
Back to top