Individual skill

procureops

ProcureOps procurement operations skill. Use for sourcing nomination readiness, receiving closeout, AP payment-hold reconciliation, contract change control, AP release and exception review, or any task that requires cross-referencing ProcureOps purchase orders, receipts, invoices, contracts, suppliers, budgets, approvals, and risk events. Use this skill whenever the user mentions ProcureOps, procurement data, purchase orders, AP holds, receiving reconciliation, vendor risk, or budget/contract analysis against operational records.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_006/fewshot/cc/fewshot_attempt_02/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
Yes
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 Procurement Operations

Analyze ProcureOps operational data by cross-referencing entities across the REST API and applying procurement-domain decision rules.

## Quick start

Every ProcureOps task follows the same core pattern:

1. **Read payload files** -- local memos, packets, or templates under `input/payloads/` that identify target entities (PO IDs, receipt IDs, invoice IDs, program IDs) and business rules.
2. **Query the API** -- fetch all relevant records from the ProcureOps endpoints listed in `references/api_schema.md`. Always fetch full endpoint collections; filter client-side by the IDs named in payloads or discovered through cross-referencing.
3. **Cross-reference entities** -- use `references/computations.md` to trace entity relationships (PO to receipt to invoice to payment, program to budget, supplier to risk events, requisition to approvals).
4. **Compute and decide** -- apply formulas from `references/computations.md` for financials, headroom, variances, and decision rules.
5. **Produce JSON** -- return only JSON matching the provided answer template. No prose outside the JSON object.
Back to top