Individual skill
fewshot_attempt_01
Not available
experiments/claude_code_glm_5_2_max/reports/skills/task_group_018/fewshot/fewshot_attempt_01/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.
Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.
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
Declared tags are partial or unavailable.
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 · 13,713 bytesSKILL.mdcore · 13,713 bytesSKILL.mdcore · 13,713 bytesSKILL.mdcore · 13,713 bytesSKILL.mdcore · 13,713 bytesreferences/financial_and_plan_math.mddoc · 5,982 bytesreferences/portal_endpoints.mddoc · 5,791 bytesreferences/reconciliation_playbook.mddoc · 6,940 bytesreferences/validation_checklist.mddoc · 5,018 bytes
Read excerpt
# Court Operations Closeout Skill
Reusable method for producing clerk-ready **closeout packages** — structured JSON that reconciles a batch of court matters after disposition. The inputs are always: (1) a prompt naming the batch and target cases/citations/petitions, (2) local clerk payloads (hearing notes, audit memos, finance extracts, worksheets, form excerpts), and (3) a live **Court Operations Portal** reachable over the network. The output is always one JSON object matching the per-task `answer_template.json`.
Use this skill whenever you must reconcile courtroom notes or finance extracts against a court portal, resolve audit conflicts (identity, counsel, status, fee schedule, departures), post or hold financial entries, build payment plans, or fill referral/license/installment forms — and return a single schema-shaped JSON object.
## What you need from the task directory
For each run, locate and read, before doing anything else:
1. `input/prompt.txt` — the batch, the court, the target case/citation/petition identifiers, and which portal endpoints are useful.
2. `input/payloads/answer_template.json` — **the authoritative output schema**. It declares the required top-level keys, per-item required keys, enums, ordering rules, and the currency/date conventions. Every field you emit must be valid against this template. Treat it as the contract.
3. Every other file under `input/payloads/` — clerk notes, audit memos, finance queue extracts, worksheets, form/form-field excerpts, petition summaries. Read all of them; conflicts between them are the point of the task.
Reach the environment **only** through `environment_access.md` (base URL and the allowed `GET /api/...` endpoint list). Do not attempt to read server-side files. The portal is open within the network — no credentials.