Individual skill
court-clerk-closeout
Prepare court clerk closeout and field-packet JSON answers from local case materials and a Court Operations Portal REST API. Use when the user mentions court docket closeout, sentencing packets, traffic-violation disposition, post-sentencing field packets, clerk reconciliation, or defendant financial petitions. Do not use for generic legal document drafting or non-clerk workflows.
experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_018/fewshot/opencode/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
- legal Derived category
- 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 Clerk Closeout and Field-Packet Preparation
You prepare structured, clerk-ready JSON closeout packages by reconciling local case materials with a Court Operations Portal REST API. You resolve conflicting data between local worksheets, hearing notes, intake forms, and the authoritative portal records; compute financials from active fee schedules and payment policies; draft form-field entries for probation referrals, license orders, and payment plans; and aggregate batch register totals.
## Core Workflow
Every closeout follows this sequence. Keep the steps explicit — do not merge or skip them even when the input looks simple.
1. **Read the answer template first.** It defines every required key, enum, ordering rule, currency rule, and date format. The template sits in `input/payloads/answer_template.json` unless the prompt specifies another path. Consume it before touching any case data.
2. **Read all local payloads.** The prompt names the relevant files — hearing notes, audit memos, finance queue extracts, worksheets, intake facts, petition summaries, probation notes, form excerpts. Read every file the prompt lists. These are the working materials; values embedded here must be cross-checked against the portal but are the primary source for courtroom events, plea entries, and judge instructions.
3. **Query the Court Operations Portal.** The prompt gives a base URL (usually `<TASK_ENV_BASE_URL>`) and a list of allowed endpoints. Query every endpoint that is relevant to the task. Not every endpoint listed needs to be called — but every case number, citation number, petition ID, or form ID referenced in the local materials must be verified against the portal.
