Menu

Individual skill

court-closeout-json

0upvotes

Use this skill for court-operations tasks that require clerk-ready JSON closeout packets, disposition registers, payment plans, financial-petition reviews, probation referrals, license orders, fee reconciliation, docket actions, placeholders, and audit findings from local payloads plus a Court Operations Portal API.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_018/fewshot/deepagents/fewshot_attempt_01/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
Network or broad shell
Last checked
Nov 11, 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 JSON

## Core Workflow

1. Read the prompt, `input/payloads/answer_template.json`, and every local payload before writing anything. Treat the template as the contract for top-level keys, required fields, enum spellings, sorting, date formats, null handling, and currency precision.
2. Extract target identifiers: case numbers, citation numbers, petition IDs, jurisdiction codes, hearing/disposition dates, and named local files. Do not query unrelated matters.
3. Fetch portal records for each target. Use targeted filters first:
   - Criminal matters: `/api/search?q={case_number}`, `/api/cases?case_number={case_number}`, `/api/charges?case_number={case_number}`, `/api/docket-entries?case_number={case_number}`.
   - Traffic matters: `/api/citations?citation_number={citation_number}`.
   - Financial petitions: `/api/financial-petitions?petition_id={petition_id}` and, when needed, `/api/financial-petitions?case_number={case_number}`.
   - Jurisdiction context: `/api/jurisdictions?jurisdiction_code={jurisdiction_code}`, `/api/fee-schedules?jurisdiction_code={jurisdiction_code}`, `/api/payment-policies?jurisdiction_code={jurisdiction_code}`, `/api/forms?jurisdiction_code={jurisdiction_code}`.
4. Reconcile sources instead of transcribing one source. Local hearing or sentencing notes usually explain what the judge ordered; portal case records usually control verified identity, status, active forms, active policies, and current fee schedules; local worksheets and scratchpads are lower-confidence audit inputs.
5. Produce one JSON object only. Validate that it parses, contains every required key, uses enum values exactly, respects ordering rules, and that totals equal the included line items.
Back to top