Individual skill

procureops-reconciliation

Build JSON-only ProcureOps sourcing, receiving, AP close, AP release, contract-change, budget, approval, and supplier-risk reconciliation answers from task-local payloads plus the shared ProcureOps API. Use when prompts mention ProcureOps endpoints, purchase orders, receipts, invoices, payments, contracts, budgets, approvals, vendor risk, sourcing nomination readiness, receiving closeout, AP hold/release queues, or change-control decision files.

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

# ProcureOps Reconciliation

## Workflow

1. Read the prompt, every file under `input/payloads/`, and the answer template before calling the API. Treat local payloads as the source for target IDs, dates, chargeback/register excerpts, and task-specific business rules. Treat ProcureOps API records as the operational source of truth.
2. Fetch the required API collections from the base URL supplied by the task runner. The helper at [scripts/fetch_procureops.py](scripts/fetch_procureops.py) can download the standard collections into one JSON file.
3. Read [references/procureops_rules.md](references/procureops_rules.md) when computing joins, quantities, money, risk state, approval state, AP decisions, nomination readiness, receiving exceptions, or change-control decisions.
4. Build the answer object directly from the template. Preserve required top-level keys and controlled enum strings. Add no prose outside the final JSON.
5. Sort list fields ascending unless the template says records are matched by a key or treated as sets. Round USD amounts to cents and percentages or ratios to the template precision.

## API Handling

Use only endpoints allowed by the task environment. Standard ProcureOps responses wrap records as:
Back to top