Menu

Individual skill

api-finance-close-review

0upvotes

Solve API-backed finance close, reimbursement/AP release, vendor compliance release, account-change review, and prepaid reconciliation tasks using local payload scope plus a runner-provided JSON API.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_005/fewshot/naive/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

# API Finance Close Review

Use this skill for tasks that ask you to return a JSON decision or reconciliation result from a local batch/scope payload and a shared finance, ERP, or compliance API.

## First Steps

1. Read the user prompt, every local payload file under `input/payloads/` or `payloads/`, and the answer template if present.
2. Treat the runner-provided API base URL as the system of record. Do not use local exports, snapshots, or stale payload records as current truth when they conflict with the API.
3. Inspect `/endpoints` when available. Prefer `/api/...` endpoints and fall back to unprefixed equivalents only if needed.
4. Query only the scoped IDs from the prompt or payload unless the template asks for a broader rollup. Use exact-match query parameters by field name, with `limit` and `offset` for pagination.
5. Return one JSON object matching the template exactly. Preserve requested units, date, casing, status labels, and list sort order. Do not include narrative text outside JSON.

Use `Decimal` or equivalent fixed-point arithmetic for money. If the prompt asks for cents, output integer cents; if it asks for dollars, output two-decimal numbers.
Back to top