Individual skill
court-packet-reconciliation
Reconcile court hearing notes, finance queues, payment petitions, and portal records into clerk-ready JSON packets, including dispositions, fees, payment plans, placeholders, and form metadata.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_018/fewshot/fewshot_attempt_02/SKILL.md
Source commit 5082a777379156a048881e94940d640702e5e09a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 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
- 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,838 bytes
Read excerpt
# Court Packet Reconciliation
Use this skill when a task asks for a structured court closeout or packet answer from local notes plus the court portal.
## Workflow
1. Read `answer_template.json` first. Treat its keys, enums, ordering rules, and placeholder token as the contract.
2. Pull facts from the local payloads and, when provided, verify against the portal endpoints named in the prompt or environment file.
3. Resolve conflicts using this order:
- signed order or explicit docket entry
- hearing notes / sentencing notes
- corroborating memo, petition, or intake sheet
- draft queue / worksheet
- stale or archived values only if the template or current policy explicitly requires them