Individual skill

erp-finance-control-review

Solve ERP finance-control review tasks that require querying a runner-provided JSON API and returning strict JSON. Use for reimbursement/AP batch close, stale AP snapshot reconciliation, vendor onboarding or account-change release risk, and prepaid close reconciliation tasks involving claims, bills, payments, vendors, compliance records, prepaid invoices, GL balances, and answer templates.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_005/fewshot/deepagents/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: Yes
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
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.

Browse files

SKILL.mdcore · 8,912 bytes

Read excerpt


# ERP Finance Control Review

## Core Workflow

1. Read the prompt, local payloads, and answer template before querying. Treat payloads as scope and schema contracts; treat the API as the current system of record unless the prompt says otherwise.
2. Use the runner-provided API base URL. Call `/endpoints` first when unsure. Prefer `/api/...` endpoints, and use exact-match query parameters by field name where possible.
3. Fetch only records needed for the scoped IDs, but paginate with `limit` and `offset` if a query may return more than one page.
4. Build a small evidence table per scoped claim, business, invoice, account, or close log. Do not rely on a source `review_status` alone; derive decisions from current supporting records.
5. Return only JSON matching the template. Preserve required top-level keys, required constant values, list ordering, enum values, numeric precision, and object key coverage.

Common endpoints:

- Claims: `/api/claims`, `/claims`
- AP bills, payments, aging: `/api/ap/bills`, `/api/ap/payments`, `/api/ap/aging`