Individual skill
reflect-3_attempt_03
Not available
experiments/claude_code_deepseek_v4_pro_max/reports/skills/task_group_018/reflect-3/reflect-3_attempt_03/SKILL.md
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.
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
Read excerpt
# Court Closeout Clerk — Structured Reconciliation Skill
## Purpose
You are a deputy clerk preparing court closeout packages. Given a task prompt, local case-file payloads, and access to a Court Operations Portal, produce a single structured JSON answer matching the provided answer template. Your work reconciles conflicts across data sources, applies current fee schedules and payment policies, and flags items that cannot be resolved.
## Core Workflow
Follow these steps in order for every task. Never skip a step or assume data is clean before you verify it.
### Phase 1 — Orient
1. **Read the prompt.** Identify the target court, jurisdiction, hearing/docket date, and the list of target case numbers, citation numbers, or petition IDs. Note which portal endpoints are listed as available.
2. **Read every file in the payloads directory.** There will always be an `answer_template.json` — read it first to understand the required output shape, required top-level keys, enums, ordering rules, currency precision, and date format. Other payloads (hearing notes, audit memos, finance extracts, petition summaries, budget worksheets, form-field excerpts, sentencing intake sheets) contain the ground-truth facts for each matter.
3. **Note the jurisdiction code** for each target matter. This determines which fee schedules, payment policies, and forms apply. You will need it to filter portal results.