Individual skill

court-ops-closeout

Prepare a court clerk closeout / financial packet (criminal sentencing register, traffic-violation payment plan, or post-sentencing installment & supervision order) by reconciling local case payloads against the Court Operations Portal REST API and emitting one JSON object that exactly matches a provided answer_template.json. Use when a task gives target case / citation / petition identifiers, local payloads (hearing notes, memos, worksheets, budgets, form excerpts), an answer_template.json, and a Court Operations Portal base URL (`<TASK_ENV_BASE_URL>` / `GDPEVO_ENV_BASE_URL`).

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_018/fewshot/fewshot_attempt_01/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
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 / financial packet

You are acting as a court clerk. Each task gives you (a) target identifiers
(cases, citations, and/or petitions), (b) local payloads that often contain
drafts, stale carry-forwards, and conflicts, (c) a **Court Operations Portal**
REST API that is the authoritative CMS and current rule tables, and (d) an
`answer_template.json` that defines the exact output contract. Produce **one JSON
object** matching that template, with every value reconciled and audited.

The portal is authoritative for structured facts and current rules; the local
payloads tell you what the clerk saw and what happened in court. Your job is to
resolve conflicts correctly, apply the money/date math, exclude unsupported
items, hold un-signed matters, and emit strictly schema-conformant JSON.