Individual skill

procureops

Complete ProcureOps procurement API tasks including sourcing nomination readiness, receiving closeout, AP payment-hold reconciliation, change-control decisions, and AP release files. Use when the task references a ProcureOps API base URL, mentions procurement records (suppliers, contracts, POs, receipts, invoices, payments, approvals, budget snapshots, vendor risk events), asks for a JSON answer following an answer template, or involves any ProcureOps workflow such as nomination readiness, 3-way match reconciliation, AP hold/release queues, contract/budget headroom analysis, or chargeback processing against receiving exceptions.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_006/fewshot/codex/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

## Overview

This skill covers the ProcureOps procurement API and the five standard workflow patterns that appear in procurement operational tasks. The API exposes 13 read-only endpoints across the procure-to-pay lifecycle. Every task provides a local payload (memo, packet, or register) naming the target records and an answer template describing the expected JSON output.

## Core Workflow

Follow this sequence for any ProcureOps task:

1. **Read the local payload(s)** -- memos, packets, and chargeback registers name the target records and provide business controls (tax rates, budget exposure rules, approval criteria, chargebacks).
2. **Read the answer template** -- this defines required keys, field types, allowed enum values, rounding rules, sort order, and set/list semantics. The template is the contract for output shape.
3. **Fetch all API endpoints** -- pull every endpoint listed in [references/api_endpoints.md](references/api_endpoints.md) using `<TASK_ENV_BASE_URL>`. See [references/api_endpoints.md](references/api_endpoints.md) for the endpoint catalog, ID prefix conventions, and cross-entity join keys.
4. **Join and reconcile** -- use the join keys from the endpoint reference to cross-match records by `program_id`, `po_id`, `supplier_id`, `contract_id`, `requisition_id`, `invoice_id`, `sku`, or `po_line_id` as appropriate. See [references/domain_concepts.md](references/domain_concepts.md) for entity relationships and computation formulas.
Back to top