Menu

Individual skill

procureops-reconciliation

0upvotes

Use this skill whenever the user asks for a ProcureOps procurement, receiving, AP invoice, payment-hold, sourcing nomination, contract-change, budget, supplier-risk, or strict JSON decision file based on the ProcureOps API and local input payloads. This is especially important when the task mentions purchase orders, receipts, AP invoices, contracts, requisitions, budget snapshots, approval events, chargebacks, vendor risk, controlled reason codes, or an answer_template.json.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_006/self/self_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
Instructions only
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 SOP

Use this skill to solve ProcureOps tasks that combine a task-local memo or packet with the live ProcureOps API and require a strict JSON answer. The API is the system of record; local payloads define scope, date, requested IDs, business rules, and output schema.

## First Pass

1. Read the prompt, every task-local payload referenced by the prompt, and the answer template before querying records.
2. Extract the scope anchors:
   - as-of or close date
   - target program, PO, receipt, invoice, requisition, contract, supplier, SKU, batch, packet, or chargeback IDs
   - explicit inclusion/exclusion rules
   - enum values, ordering requirements, rounding precision, and required keys from the template
3. Use the ProcureOps base URL provided by the environment or runner. If a prompt mentions local service URLs, still prefer the provided environment access details for the actual run.
4. Confirm the live endpoint list with `GET /`. Public endpoint names use underscores, for example `/ap_invoices` and `/payments`; prompts may use prose such as `/ap/invoices`, but the live endpoint is `/ap_invoices`.
Back to top