Individual skill
court-closeout-json
Prepare structured court clerk closeout JSON from local payloads and a Court Operations Portal. Use for criminal disposition registers, traffic violation payment plans, sentencing closeout packets, probation or license-suspension forms, financial petitions, fee-schedule reconciliation, unsupported-fee exclusions, placeholder handling, and exact answer_template-driven JSON outputs.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_018/fewshot/cc/fewshot_attempt_03/SKILL.md
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- finance Derived category
- operations Derived category
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
## Operating Rule
Use this skill when a task asks for a clerk-ready JSON closeout or packet using local payloads plus a Court Operations Portal. Treat the prompt, local payloads, portal records, and `answer_template.json` as the complete source of truth. Return JSON only when the task asks for JSON; do not add markdown or explanatory prose.
## First Pass
1. Read the prompt and identify every target case number, citation number, petition ID, jurisdiction, hearing/disposition date, and requested output file/template.
2. Read `input/payloads/answer_template.json` before deriving values. Copy its required top-level structure, exact key names, enums, sort rules, date rules, numeric precision, and null/placeholder rules.
3. Read all other local payloads. Build a matter-by-matter evidence ledger with local hearing facts, queue or worksheet facts, petition facts, form excerpts, and conflict notes.
4. Query the portal for each target identifier and jurisdiction. Use direct filters first:
- `/api/cases?case_number=...`
- `/api/charges?case_number=...`