Menu

Individual skill

reflect-3-procureops

0upvotes

Use this skill for ProcureOps procurement, receiving, AP close, change-control, nomination-readiness, and release/hold JSON tasks. Trigger when a task provides ProcureOps API records plus local payloads and asks for exact JSON with purchase orders, receipts, invoices, contracts, suppliers, approvals, budgets, payments, vendor risk, chargebacks, or controlled decision queues.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_006/reflect-3/reflect-3_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

# Reflect-3 ProcureOps Workflow

Use this skill to solve structured ProcureOps tasks that combine local packet files with live operational API records. The common failure mode is answering from the memo alone. Treat the memo as the target/control sheet and the API as the system of record for operational facts.

## First Pass

1. Read the prompt, the answer template, and every task-local payload the prompt names.
2. Extract the required output shape, allowed enum values, sort orders, target IDs, review/as-of dates, tax rates, opening balances, payment horizons, and any local control rules.
3. Inspect the API root if endpoint names are uncertain. In this task family, useful records are usually exposed as `ap_invoices`, `approval_events`, `budget_snapshots`, `contracts`, `items`, `payments`, `programs`, `purchase_orders`, `purchase_requisitions`, `receipts`, `suppliers`, and `vendor_risk_events`.
4. Query by the IDs from the local packet first, then follow links from those records: invoice to PO and receipt, PO to requisition/contract/program/supplier, supplier to risk events, program to budget snapshot, and invoice to payments.
5. Build the answer against the template, not against prose memory. Return only the JSON object.

## Source Precedence
Back to top