Menu

Individual skill

court-closeout-reconciliation

0upvotes

Use this skill for clerk-ready court closeout, disposition register, traffic citation, sentencing packet, financial petition, probation referral, license suspension, payment-plan, fee reconciliation, or Court Operations Portal JSON tasks. Trigger whenever the user asks to reconcile local court payloads with portal records and return a structured JSON answer for criminal or traffic matters.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_018/fewshot/cc/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 to prepare structured court-operations JSON from local payloads plus the Court Operations Portal. The common failure mode is trusting one noisy source too much. Treat the task as reconciliation: identify the target matters, gather exact portal records, resolve conflicts by evidence strength, compute money and schedules, then validate against the provided template.

## Core Workflow

1. Read the user prompt, `answer_template.json`, and every local payload file before querying the portal.
2. Extract the target identifiers: case numbers, citation numbers, petition IDs, jurisdiction, hearing/disposition dates, and required output sections.
3. If the prompt uses `<TASK_ENV_BASE_URL>`, read `environment_access.md` in the workspace and use its `base_url`.
4. Query the portal only for target records and the relevant jurisdiction metadata:
   - Cases: `/api/cases?case_number=...`
   - Charges: `/api/charges?case_number=...`
   - Docket: `/api/docket-entries?case_number=...`
   - Citations: `/api/citations?citation_number=...`
Back to top