Individual skill
court-packet-reconciliation
Prepare clerk-ready court closeout, disposition, payment-plan, supervision, and form-packet JSON outputs from mixed local records and official case/fee/policy/form data. Use when a task requires reconciling hearing notes, worksheets, case records, charges, payment petitions, fee schedules, policies, forms, missing identifiers, pending matters, and stale or conflicting financial entries into a strict answer template.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_018/reflect-3/reflect-3_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
- data 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.
Read excerpt
# Court Packet Reconciliation
## Workflow
1. Read the prompt, local payloads, and answer template before filling any fields. Treat the template as the contract: required keys, enum spellings, sort order, date format, null handling, and currency precision all control the output.
2. Build a short private reconciliation table per matter. Track identity, status, plea/finding, sentence, fee basis, payment-plan basis, form requirements, missing fields, exclusions, and totals.
3. Compare each source against the role it is best suited for:
- Use courtroom notes, signed-order notes, sentencing intake, and petition intake for what the court actually ordered.
- Use official case/citation records for verified identity, DOB, case status, counsel, and filing metadata unless the local material flags the field as missing or unresolved.
- Use current fee schedules and payment policies for amounts, eligibility, account fees, minimum payments, due dates, and priority rules.
- Use current form metadata and local form excerpts for form IDs, labels, account-reference handling, required fields, and placeholder text.
4. Resolve conflicts explicitly in the output when the schema has audit or exclusion fields. Do not carry stale worksheet/import values into the corrected disposition or financial totals.
5. Produce only the requested JSON object unless the user asks for explanation.
