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
- Read
prompt.txt, every file underpayloads/, andanswer_template.jsonfirst. - Read
environment_access.mdfor 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. - 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.
- Follow the template exactly: required keys, nesting, enum values, ordering rules, date formats, currency precision, and
nullhandling. Return JSON only. - Surface every material conflict in the designated audit, exclusion, or placeholder section. Do not silently merge contradictory facts.
- 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. - 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.
- Compute payment-plan schedules from the approved balance and installment amount, including any final remainder installment and any required return-to-court date.
- Sort arrays and totals exactly as the template instructs.
Packet Shapes
- Build
audit_findings/case_dispositions/fee_reconciliation/docket_entries/register_totalsfor disposition closeouts. - Build
matters/excluded_charges/batch_totalsfor citation payment-plan closeouts. - Build
case_memo/cc1375/cc1379/budget_review/placeholder_fields/excluded_financial_itemsfor post-sentencing packets. - Build
petitions/probation_referrals/license_orders/placeholder_casesfor petition-and-supervision packets.