Menu

Individual skill

task-group-005-finance-controls

0upvotes

Use this skill for task_group_005 shared ERP, AP, compliance, vendor onboarding, prepaid close, reimbursement close, stale AP export, account-change release, or finance-risk JSON tasks that require calling a runner-provided task API and returning an answer_template-shaped JSON object. It guides API discovery, current-record reconciliation, close-control decisions, and strict schema output.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_005/fewshot/cc/fewshot_attempt_01/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 Controls

Use this skill when the task asks for finance-risk, AP reimbursement, vendor onboarding, prepaid close, stale AP snapshot, or account-change payment-release decisions from a shared ERP/compliance API.

## Core Workflow

1. Read the prompt and every local payload in `input/payloads/`.
2. Treat `answer_template.json` as the output contract: preserve required keys, enum values, order requirements, numeric precision, and ID ordering.
3. Use the runner-provided API base URL as the system of record. Local snapshots and batch files define scope and context, but current API records decide the answer unless the prompt says otherwise.
4. Call `/endpoints` first when available. Prefer `/api/...` endpoints, but fall back to the non-API aliases named in the prompt or endpoint list.
5. Fetch only the scoped records needed for the requested IDs/accounts/period, plus related bills, payments, vendors, compliance details, GL balances, and close logs when relevant.
6. Build a scratch reconciliation table before writing final JSON. Record the source evidence for each ID, especially status, amount, vendor, payment, bank, screening, tax, license, and data-quality fields.
7. Return only the requested JSON object when the prompt asks for JSON only. Do not include narrative text, citations, or extra properties.
Back to top