Menu

Individual skill

task-group-005-finance-reconciliation

0upvotes

Use this skill for task_group_005 finance, ERP, AP, reimbursement, prepaid close, vendor onboarding, compliance, or account-change release tasks that require using the shared JSON API plus local payload templates to return a decision JSON. Trigger whenever the prompt mentions the runner-provided API base URL, current ERP/compliance evidence, AP bills/payments, claims, vendors, UBOs, bank/tax/license screening, GL balances, or prepaid schedules.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_005/fewshot/cc/fewshot_attempt_03/SKILL.md

Read pinned source

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.

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

# Task Group 005 Finance Reconciliation

Use this skill to solve finance close and compliance release tasks backed by the shared task API. The local files define the requested scope and JSON schema; the API is the current system of record.

## Core Workflow

1. Read the prompt, every file under `input/payloads/`, and especially the answer template.
2. Get the API base URL from the prompt placeholder replacement, the runner environment, or the provided task environment variable. Check `/endpoints` first when endpoint names are uncertain.
3. Prefer `/api/...` endpoints, with the non-`/api` alternatives as fallbacks. The API supports exact-match query parameters by field name and `limit`/`offset` pagination.
4. Fetch only the records in scope whenever possible. Do not treat local stale snapshots, batch notes, or review status fields as final evidence when current API records disagree.
5. Build the response exactly to the template:
   - Use the template's top-level keys and required values.
   - Preserve any specified ordering: ID lists usually sort ascending, while invoice result lists often preserve payload order.
   - Return JSON only, with no commentary.
Back to top