Individual skill
court-clerk-reconciliation
Court-clerk reconciliation and financial closeout workflow for criminal, traffic, and post-sentencing dockets. Use when a deputy clerk task requires: (1) cross-referencing local hearing notes, audit memos, finance worksheets, petition summaries, or form excerpts against a Court Operations Portal REST API, (2) resolving identity/counsel/fee/status/departure conflicts across conflicting sources, (3) computing per-case financial totals (fines, costs, assessments, user fees, surcharges), (4) structuring approved post-disposition payment plans with installment math, (5) preparing CC-1375 probation referrals, CC-1379 license-suspension/installment orders, or local payment-plan forms, (6) identifying unsupported or stale charges for exclusion, or (7) assembling docket-register entries with batch totals from a multi-case closeout batch.
experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_018/fewshot/deepagents/fewshot_attempt_03/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
- No
- 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
- operations Derived category
- security 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 · 6,845 bytesSKILL.mdcore · 6,845 bytesreferences/fee-rules.mddoc · 5,984 bytesreferences/forms-reference.mddoc · 4,721 bytesreferences/portal-query-patterns.mddoc · 5,282 bytesreferences/reconciliation-rules.mddoc · 5,313 bytes
Read excerpt
# Court Clerk Reconciliation
## Overview
Produce structured JSON closeout packets by reconciling local case materials against a Court Operations Portal. Follow a fixed reconciliation hierarchy, use the portal to verify records against current schedules and policies, compute financial totals and payment plans, and flag all unsupported charges for exclusion.
## Core Workflow
1. Read every local payload file and the answer template.
2. Query the portal for each target case, its charges, fee schedules, payment policies, forms, and any jurisdiction/citation/docket records needed to fill the template.
3. Apply the reconciliation hierarchy (see [reconciliation-rules.md](references/reconciliation-rules.md)).
4. Compute case-level financials, payment plans, and register totals. Apply exclusion rules for unsupported charges (see [fee-rules.md](references/fee-rules.md)).
5. Map form fields and use the exact placeholder `"TBD from case file"` for any required field the available materials cannot fill (see [forms-reference.md](references/forms-reference.md)).
6. Assemble the answer object sorted by case/citation number ascending, with ISO dates and currency to two decimal places. Use only the enum values declared in the answer template.