Individual skill

procureops-packet-reconciliation

Use for ProcureOps API task packets that ask for JSON-only sourcing nomination readiness, receiving closeout, AP invoice hold/release, AP close/vendor-balance reconciliation, or change-control decision files. Guides reading local input/payloads answer_template and memo/packet files, fetching ProcureOps endpoints from TASK_ENV_BASE_URL, joining supplier/item/program/requisition/contract/purchase-order/receipt/invoice/payment/approval/budget/risk records, computing rounded USD and quantity reconciliations, and emitting template-exact JSON.

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

## Core Rules

- Read the prompt, `input/payloads/answer_template.json`, and every other file under `input/payloads/` before doing calculations.
- Treat the API as source of truth for operational records. Treat local payloads as the source for task scope, target IDs, special business controls, local chargeback excerpts, alias notes, and requested output template.
- Return only the JSON object requested by the template. Do not include Markdown, comments, or explanatory prose.
- Follow the template over this skill when they disagree: key names, required fields, enum values, list ordering, and precision all come from the template.
- Use native JSON numbers for numeric fields. Round USD amounts to cents, percentages and ratios to the precision named by the template, and sort any list described as sorted or set-like.
- Filter dated evidence using the task's as-of, close, review, or memo date when one is provided. Include records on or before that date unless the template says otherwise.

## Fetching The API

Allowed endpoints are usually `/manifest`, `/suppliers`, `/items`, `/programs`, `/contracts`, `/purchase_requisitions`, `/purchase_orders`, `/receipts`, `/ap/invoices`, `/ap/payments`, `/approvals`, `/budget_snapshots`, and `/vendor_risk_events`.