Individual skill
task-group-005-erp-finance-control
Solve task_group_005 ERP finance-control evaluations by reconciling current API data for reimbursement AP close, vendor onboarding/account-change release, prepaid close, and stale AP snapshots.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_005/self/self_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.
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
- data 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 ERP Finance Control
Use this skill when a task asks for JSON decisions from the task_group_005 ERP finance API. The recurring pattern is: local files define the scope and answer schema, while the API is the system of record.
## Ground Rules
- Read the prompt, local scope/batch payload, and `answer_template.json` first. Build the answer shape from the template, not from memory.
- Use the runner-provided API base URL when present. Otherwise use the task group's environment access base URL or local `<environment_base_url>` if the runner says it is active.
- Use only documented API endpoints. Do not inspect local environment source or data directories.
- Treat local CSV exports as stale context unless the prompt explicitly says otherwise. Current API records override stale snapshots.
- API list endpoints return `{count,data,total,...}` and support exact-match query params, `limit`, and `offset`. Paginate if `total > count`.
- Return JSON only when requested. Do not add narrative, comments, markdown fences, or extra keys.
- Obey each schema's ordering and units exactly: some reimbursement totals are integer USD cents, while other templates require USD numbers with two decimals.
