Menu

Individual skill

court-closeout-reconciliation

0upvotes

Use this skill for clerk-ready court disposition closeouts, sentencing registers, traffic violation payment plans, financial petitions, probation referrals, license-suspension orders, and related court operations JSON packets. It is especially important whenever a task combines local payload files with a Court Operations Portal and asks for strict schema JSON, fee reconciliation, payment schedule math, placeholder handling, exclusions, audit findings, or docket/register totals.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_018/fewshot/opencode/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.

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 preparing structured court closeout or post-disposition JSON from local case materials and the Court Operations Portal. The core job is to reconcile competing sources, follow the supplied answer template exactly, and compute only supported financial and schedule fields.

## Operating Rules

- Return JSON only when the prompt asks for JSON. Do not include markdown, notes, citations, or explanations outside the object.
- Use only the user-provided local files and the task's Court Operations Portal. Do not infer laws, fee amounts, contact details, identifiers, or form fields from general knowledge.
- Treat `input/payloads/answer_template.json` as the contract for shape, enum spellings, required keys, sort order, date formats, null handling, and placeholder values.
- Read every local payload before finalizing. Local notes often explain stale worksheets, unsigned orders, amended charges, excluded fees, and placeholder policy.
- Query the portal endpoints named in the prompt. Portal responses use `{ "count": ..., "results": [...] }`; work from `results`.

## Portal Workflow
Back to top