Menu

Individual skill

erp-finance-release-control

0upvotes

Use this skill for task_group_005 style ERP finance/compliance API tasks that ask for strict JSON decisions about reimbursement AP batches, stale AP exports, prepaid close reconciliations, vendor onboarding release, or payment release after account-change events. It helps join local batch payloads to the shared API, apply close/release-control rules, calculate currency fields, and return only schema-conforming JSON.

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

# ERP Finance Release Control

Use this when a task asks you to decide finance close or release posture from a local prompt/payload plus the shared ERP/compliance API. The API is the current system of record unless the prompt explicitly says otherwise; local CSV exports and batch files define scope and context.

## Operating Pattern

1. Read the prompt and every local payload. Treat `answer_template.json` as the output contract: keys, enum values, ordering, precision, and fixed required values come from the template.
2. Get the API base URL from the runner-provided `TASK_ENV_BASE_URL` or the prompt placeholder. Use only the task API, not local source data, to resolve current ERP/compliance facts.
3. Query exact-match filters by field name, and paginate when `total` exceeds returned `count`. Prefer `/api/...` endpoints, falling back to the non-`/api` aliases if needed.
4. Build a small evidence table before writing JSON: one row per claim, business, invoice, or account with the decisive source fields and final classification.
5. Emit exactly one JSON object, with no narrative. Sort IDs ascending unless the template says to preserve payload order. Output currency as numbers rounded to two decimals.

Optional helper: `scripts/fetch_task_group_005.py` fetches filtered API snapshots without third-party packages.
Back to top