Menu

Individual skill

procureops-reconciliation

0upvotes

Solve ProcureOps sourcing, receiving, AP close, change-control, and invoice-release reconciliation tasks. Use when a task provides a local memo or answer_template and asks Codex to query the read-only ProcureOps API, join suppliers, items, programs, contracts, requisitions, purchase orders, receipts, AP invoices/payments, approvals, budgets, and vendor-risk records, compute USD or quantity decisions, and return exact JSON only.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_006/fewshot/codex/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

# ProcureOps Reconciliation

Use this skill to produce controlled JSON answers for ProcureOps operational review tasks.

## Workflow

1. Read the prompt, `input/payloads/answer_template.json`, and every local payload. Treat the template as the output contract. Treat local payloads as scope, target IDs, dates, and any task-local register data that is not available from the API.
2. Query the API named in the prompt. The API is the source of truth for operational records unless the prompt explicitly says a local payload field is authoritative for a task-local control such as a chargeback register or stale alias note.
3. Build indexes by ID before calculating: suppliers by `supplier_id`, programs by `program_id`, contracts by `contract_id`, requisitions by `requisition_id`, purchase orders by `po_id`, receipts by `receipt_id` and `po_id`, invoices by `invoice_id` and `po_id`, payments by `invoice_id`, approvals by `object_id`, budgets by `program_id`, risks by `supplier_id`.
4. Filter to the task scope from the local payload. For date-bounded tasks, include only records with relevant dates on or before the as-of or close date unless the template asks for future scheduled activity through a stated horizon.
5. Calculate fields from joined records, then shape the result exactly to the template. Use JSON types, enum values, required keys, and list ordering from the template.
6. Return only the final JSON object. Do not include prose, markdown fences, citations, or source notes outside the requested JSON.

## API Helper
Back to top