Individual skill
reflect-3_attempt_03
Not available
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_005/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.
Read excerpt
# Reflect-3 Finance Close Skill
Use this skill for task_group_005 finance-control tasks that ask for JSON decisions from the shared ERP/compliance API. The common pattern is to reconcile a small scoped payload against current API records, not to summarize source statuses.
## Core Workflow
1. Read the prompt, the answer template, and any scoped local payloads first. Treat local snapshots and batches as scope/context unless the prompt explicitly makes them authoritative.
2. Use the live API records as the system of record for current claim, AP, payment, vendor, compliance, prepaid, GL, and close-log evidence.
3. Build the answer directly from the template. Keep required top-level keys, enum values, booleans, numeric precision, and list ordering exactly as specified.
4. Sort ID lists ascending by the ID type requested. Preserve scope order only when the template says to preserve it.
5. Return JSON only when requested. Do not include explanatory text outside the object.
## Reimbursement And AP Close
- For claim batches, reconcile each claim across claim status/support, AP bill link, AP bill amount/vendor, bill status, and payment status.