Individual skill

court-closeout-json

Prepare clerk-ready JSON answers for Court Operations Portal closeout tasks involving criminal dispositions, traffic citations, sentencing/probation/license packets, financial petitions, fee schedules, payment plans, form metadata, register totals, unsupported charge exclusions, and missing-field placeholders. Use when a prompt asks Codex to reconcile local court payloads with portal endpoints and return an answer_template.json-shaped court operations result.

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

Use this skill to produce a single schema-valid JSON object for court closeout and post-disposition packet tasks. The task usually provides local payloads plus a Court Operations Portal base URL. Treat the local payloads and portal records as evidence to reconcile, not as text to summarize.

## First Pass

1. Read the prompt, `answer_template.json`, and every local payload before deciding any values.
2. Extract target identifiers, court/jurisdiction, docket or hearing date, requested portal endpoints, output keys, enum values, ordering rules, date rules, currency rules, and placeholder text.
3. Build a small evidence table for each target matter: local final hearing/order facts, worksheet or queue values, portal case/citation/petition rows, charge rows, docket rows, current fee schedules, payment policy, and form metadata.
4. Return JSON only. Do not include markdown, citations, comments, or explanatory prose.

## Portal Queries

Use the task base URL from the prompt or `environment_access.md`. Query only target identifiers and their jurisdictions.
Back to top