Individual skill

court-closeout-reconciliation

Reconcile local court documents against a read-only Court Operations Portal API to produce structured closeout packets, financial entries, payment plans, probation referrals, and license orders. Covers audit conflict identification, cross-source identity and counsel resolution, fee-schedule date matching, installment math, placeholder discipline, and unsupported-charge exclusions.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/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
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 the task involves reconciling local court materials against the Court Operations Portal to produce structured clerk-ready JSON closeout packets, disposition registers, post-sentencing form packets, or payment-plan orders.

## The Core Workflow

Every task in this family follows the same three-stage pipeline:

1. **Ingest local payloads** -- Read every file in `input/payloads/` and the prompt text.
2. **Cross-check the portal** -- Query the Court Operations Portal API for the target cases/citations, their charges, docket entries, fee schedules, payment policies, forms, petitions, and jurisdiction metadata.
3. **Reconcile and produce the answer** -- Compare local claims against portal records, identify and resolve conflicts, compute financials, and output a single JSON object matching the provided `answer_template.json`.

## Portal API Reference
Back to top