Individual skill
task-group-005-finance-reconciliation
Solve task_group_005 finance close, AP reimbursement, prepaid, vendor onboarding, and payment-release tasks using local scope payloads plus the current ERP/compliance API.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_005/fewshot/naive/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 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
- 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 Finance Reconciliation
Use this skill when a task asks for a finance close, AP reimbursement, prepaid schedule, vendor onboarding, or vendor account-change release decision from the shared `task_group_005` API.
## Core Workflow
1. Read the prompt, every local payload, and the answer template. Treat local payloads as scope, batch context, stale snapshots, or output schemas. Treat the API as the system of record unless the prompt explicitly says otherwise.
2. Use the runner-provided `<TASK_ENV_BASE_URL>`. Strip any trailing slash. Start with `GET /endpoints` if endpoint names are uncertain.
3. Prefer `/api/...` endpoints and fall back to the non-API aliases when needed. Use exact-match query parameters by field name. Paginate list endpoints with `limit` and `offset` until all records are fetched.
4. Fetch only records needed for the scoped IDs, accounts, entity, period, and review date. Cross-check linked records rather than trusting a single status field.
5. Follow the answer template exactly: required keys, enum values, top-level order when specified, JSON only, no narrative. Sort IDs ascending unless the template says to preserve local scope order.
6. Use `Decimal` or integer cents internally for money. Round output amounts to the template precision, usually two decimal JSON numbers. If the prompt conflicts with the template, the template's type and precision control the final JSON shape.
Useful endpoints: