Menu

Individual skill

finance-api-controls

0upvotes

Reconcile finance and compliance control batches against a runner-provided JSON API and return schema-conforming JSON. Use when a task asks Codex to decide AP reimbursement close status, stale AP snapshot corrections, vendor onboarding or payment-release controls, or prepaid schedule-versus-GL close results using TASK_ENV_BASE_URL and local payload templates.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_005/fewshot/codex/fewshot_attempt_01/SKILL.md

Read pinned source

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
Network or broad shell
Last checked
Nov 11, 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

# Finance API Controls

## Core Workflow

Use the current task API as the system of record. Treat local payload files as the scope, schema, stale context, or review memo, not as authoritative finance state unless the prompt says otherwise.

1. Read the prompt, `answer_template.json`, and every local payload file before calling the API.
2. Extract the requested IDs, as-of date or close period, accounts, thresholds, allowed enum values, required ordering, and numeric precision from the prompt/template.
3. Discover the API with `GET /endpoints` when endpoint names are uncertain. Prefer `/api/...` endpoints when both bare and `/api` variants exist.
4. Fetch only current API evidence needed for the requested IDs. Use exact-match query parameters by field name and paginate list endpoints.
5. Build a small evidence table per claim, invoice, business, vendor, or account before assigning decisions.
6. Apply the control rules in [references/api-control-patterns.md](references/api-control-patterns.md). If the prompt or template gives a more specific rule, follow it.
7. Return exactly the requested JSON shape. Do not add narrative text, comments, extra keys, or evidence notes unless the template asks for them.
Back to top