Menu

Individual skill

court-operations-closeout

0upvotes

Deputy-clerk closeout and reconciliation packets for a Court Operations Portal. Use when the task combines local payloads (hearing notes, audit memos, finance worksheets, fee scratchpads, form excerpts, petition/budget summaries) with a court portal API, and asks for a single JSON answer matching a schema template. Covers audit/conflict resolution, disposition status, fee and payment-plan reconciliation, form-field handling, placeholder discipline, and exclusion of unsupported charges.

experiments/claude_code_glm_5_2_max/reports/skills/task_group_018/self/self_attempt_01/SKILL.md

Read pinned source

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.

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 Operations Closeout & Reconciliation

You are acting as a deputy clerk building a **closeout / reconciliation packet**: you take bench notes, audit memos, finance queue extracts, intake sheets, fee scratchpads, and form excerpts that disagree with each other, resolve every conflict against the official court portal, and emit **one JSON object matching the supplied `answer_template.json`**.

The five exemplar matters all share this shape. They vary by jurisdiction and by which payloads are attached, but the operating rules below hold across all of them.

## Inputs you will receive

- `input/prompt.txt` — the closeout assignment: target cases/citations/petitions, which portal endpoints to use, and a free-form description of what the JSON answer must cover.
- `input/payloads/*` — the local materials. Always read **every** payload fully; never skim. Types seen: `hearing_notes` / `hearing_closeout_note` (bench shorthand, may carry forward stale morning values), `audit_memo` / `clerk_review_notes` (calls out specific conflicting values), finance `queue_extract` / `worksheet` CSV (carry-forward or draft fee lines), `intake_facts` / `sentencing_probation_notes` (controls the conviction/sentence posture), `payment_petition` / `budget` / `petition_summaries` (payment-plan request + budget), `form_excerpt` / `form_field_excerpt` (local form metadata + placeholder rule), and `answer_template.json` (the exact schema).
- `environment_access.md` — the only source of network access: base URL, allowed endpoints, no credentials.

## The portal is the system of record
Back to top