Individual skill
court-packet-assembler
Assemble court closeout and sentencing packet JSON from staged hearing notes, petitions, worksheets, form excerpts, templates, and Court Operations Portal records. Use when a task provides an answer template plus local payloads and asks for reconciled dispositions, fee tables, payment plans, probation or license orders, placeholders, exclusions, or register totals.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_018/fewshot/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
- Yes
- 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
- operations Derived category
- productivity Derived category
- productivity-notes 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
SKILL.mdcore · 2,564 bytesagents/openai.yamlasset · 320 bytes
Read excerpt
# Court Packet Assembler
Use this skill for staged court packet tasks where the answer must be a single JSON object matching `answer_template.json`.
## Workflow
1. Read `prompt.txt`, every file under `payloads/`, and `answer_template.json` first.
2. Read `environment_access.md` for the portal base URL. Query only the listed endpoints the packet needs, usually jurisdictions, cases or citations, charges, docket-entries, fee-schedules, payment-policies, forms, financial-petitions, and search.
3. Treat signed orders, hearing notes, portal records, and current fee or policy data as authoritative. Treat worksheets, queue extracts, draft forms, stale memos, and older revisions as conflict sources to reconcile, not as final truth.
4. Follow the template exactly: required keys, nesting, enum values, ordering rules, date formats, currency precision, and `null` handling. Return JSON only.
5. Surface every material conflict in the designated audit, exclusion, or placeholder section. Do not silently merge contradictory facts.
6. Use the exact placeholder the packet requires, usually `TBD from case file`, for missing identifiers, addresses, phone numbers, license numbers, officer details, or similar required form fields.
7. Exclude fees, charges, or matters unless a current order, current schedule, or current policy supports them. Keep pending or unsigned matters out of posted financial totals.
8. Compute payment-plan schedules from the approved balance and installment amount, including any final remainder installment and any required return-to-court date.