Menu

Individual skill

procureops-casework

0upvotes

Resolve ProcureOps procurement casework into strict JSON from a task memo and the live ProcureOps API. Use this whenever the user asks for a sourcing nomination packet, receiving or AP closeout, contract or budget change-control file, invoice release decision, or any similar procurement reconciliation grounded in live ProcureOps records, even if they only mention AP holds, receipts, purchase orders, vendor risk, or budget snapshots.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/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
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 Casework

Use this skill for structured procurement tasks where the answer must be a JSON object matching a local template and backed by live ProcureOps records.

## Workflow

1. Read the task prompt, every file under `input/payloads/`, and the answer template before you query anything.
2. Identify the target IDs, date, program, supplier, PO, receipt, invoice, requisition, contract, batch, or change-request scope from the memo and template.
3. Treat the ProcureOps API as the source of truth. If the task exposes a manifest or anchor map, read it first to confirm the environment, then query the smallest set of endpoints that can satisfy the template.
4. Build a record map keyed by exact IDs. Cross-check linked records before you compute derived fields.
5. Fill the template literally. Preserve required values, allowed enums, nullability, and any requested sort order.
6. Validate every derived number and list ordering before you answer.
7. Return raw JSON only. No prose, no markdown, no code fences.
Back to top