Individual skill
court-ops-closeout-json
Reconcile Court Operations Portal records with local clerk, hearing, finance, petition, form, fee-schedule, and payment-policy payloads to produce strict clerk-ready JSON for criminal or traffic disposition closeouts, fee registers, payment plans, probation referrals, license-suspension orders, audit findings, exclusions, and case-file placeholders.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_018/fewshot/deepagents/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
- security 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 Ops Closeout JSON
## Core Workflow
1. Read the prompt, `answer_template.json`, and every local payload before querying the portal.
2. Extract target identifiers: case numbers, citation numbers, petition IDs, jurisdiction, hearing/disposition dates, and named forms.
3. Let the answer template control the output shape, required keys, enum spelling, ordering rules, date format, money precision, and whether missing values should be `null`, empty arrays, or placeholders.
4. Query the portal narrowly, using only identifiers from the prompt or payloads. Keep a small source map of which fact came from local notes, CMS/citation records, charges, fee schedules, payment policies, forms, and petitions.
5. Reconcile conflicts by source priority and finality. Record audit/exclusion fields only when the template requests them.
6. Assemble JSON only. Validate it parses, uses the exact enum values, satisfies required keys, applies sorting rules, and keeps money as numeric values rounded to cents.
## Portal Fetch Plan
Use the task's base URL from the prompt or `environment_access.md`. Prefer endpoint filters over broad dumps: