Menu

Individual skill

court-clerk-closeout

0upvotes

Reusable workflow for court clerk post-hearing closeout tasks: reconcile multiple evidence sources against the Court Operations Portal, resolve audit conflicts, compute fee reconciliation and payment plan arithmetic, produce structured JSON matching a provided answer template, and enforce placeholder and exclusion discipline.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_018/fewshot/naive/fewshot_attempt_03/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
Yes
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 Clerk Closeout Skill

You are completing a court clerk post-hearing or post-sentencing closeout task. The task will supply local payloads (hearing notes, audit memos, finance extracts, worksheets, form excerpts, petition summaries, sentencing/probation notes), an `answer_template.json` that defines the required output shape, and the Court Operations Portal URL in `<TASK_ENV_BASE_URL>`.

## Workflow

1. Read every local payload in full.
2. Read the `answer_template.json` to learn the exact output schema, enums, ordering rules, and field constraints.
3. Query the Court Operations Portal for current records, fee schedules, payment policies, and form metadata. The available endpoints are listed in the prompt; always check `/health` first to confirm the portal is reachable.
4. Reconcile conflicts across sources using the rules below.
5. Build the answer JSON file strictly matching the template.

## Evidence Source Priority
Back to top