Individual skill
court-closeout-json
Solve court closeout, disposition register, payment plan, probation referral, and license order tasks by reconciling local payloads with a Court Operations Portal and returning schema-exact JSON.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_018/fewshot/naive/fewshot_attempt_01/SKILL.md
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
- Instructions only
- 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
- 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 Skill
Use this skill when a task asks for a clerk-ready JSON answer for court disposition closeout, docket/register reconciliation, traffic citation payment plans, financial petitions, probation referrals, license suspension orders, or similar post-disposition court packets.
## Core Rule
Return only the JSON object requested by the task. The local `input/payloads/answer_template.json` is the output contract: preserve its required top-level keys, field names, allowed enum values, list ordering rules, date/datetime formats, null rules, and currency precision. Do not add explanatory markdown or unsupported fields.
## One-Pass Workflow
1. Read the prompt and every file under `input/payloads/`.
2. Read `answer_template.json` first or revisit it before writing the answer. Treat it as authoritative over natural-language expectations.
3. Extract the target matters: cases, citations, petitions, jurisdiction, hearing/disposition dates, and listed portal endpoints.
4. Query the Court Operations Portal at the task's `<TASK_ENV_BASE_URL>` using only endpoints named or clearly relevant in the prompt. Use `/api/search` to locate identifiers when needed, then fetch structured records from matter-specific endpoints such as cases, citations, charges, docket entries, fee schedules, payment policies, forms, and financial petitions.