Individual skill
reflect-3_attempt_01
Solve task_group_005 ERP finance, AP, prepaid, and compliance release-control tasks using current API evidence and strict JSON schemas.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_005/reflect-3/reflect-3_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 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
- legal Derived category
- finance Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Task Group 005 Reflect Skill
Use this workflow for ERP finance-control tasks that combine staged task payloads with the shared JSON API. Treat local payloads as scope, stale context, or schema instructions; treat the API as the system of record unless the prompt explicitly says otherwise.
## Core Workflow
1. Read the prompt, answer template, and any scoped payload first. Copy required IDs, dates, accounts, ordering rules, enum values, and precision rules from those files.
2. Query the shared API records needed for each scoped object. Prefer exact-match parameters for IDs and use the canonical `/api/...` endpoints when both aliases exist.
3. Reconcile current evidence, not stale exports or source review labels alone. A stale local row can explain what changed, but current claim, bill, payment, vendor, compliance, GL, and close-log records decide the answer.
4. Build the output directly against the answer template. Preserve required top-level keys, enum spellings, ordering rules, and two-decimal USD amounts.
5. Before finishing, re-check every list for the requested sort order and every numeric field for sign convention, especially variances defined as schedule minus GL.
## AP Claims And Reimbursements
