Individual skill
procureops-control-files
Solve ProcureOps business-control JSON tasks that require combining local packet or memo anchors with the shared read-only ProcureOps API for sourcing nomination readiness, receiving/AP reconciliation, payment hold/release closeout, contract amendment change control, supplier risk context, budget checks, and chargeback-based AP release files.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_006/fewshot/naive/fewshot_attempt_02/SKILL.md
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- legal Derived category
- finance Derived category
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 Control Files
Use this skill for ProcureOps tasks that ask for a JSON control file from local payloads plus the ProcureOps API. Always produce only the JSON object requested by the task.
## Core Workflow
1. Read `input/prompt.txt`, every file under `input/payloads/`, and especially `answer_template.json`.
2. Treat the local memo or packet as the source for scope: target program IDs, invoice IDs, PO IDs, receipt IDs, requisitions, contracts, dates, tax rates, chargeback registers, and allowed output labels.
3. Treat the API as the source of truth for operational records: suppliers, items, programs, contracts, requisitions, purchase orders, receipts, invoices, payments, approvals, budgets, and vendor risk.
4. Fetch only needed read-only endpoints from `<TASK_ENV_BASE_URL>`. Endpoint responses use `{ "count": n, "results": [...] }`; index `results` by ID.
5. Join records by stable IDs first, then by PO, requisition, supplier, SKU, program, and dates. Do not trust a local narrative when it conflicts with an API record, except for local-only registers such as chargeback excerpts.
6. Apply the template exactly: required keys, enum labels, ordering, numeric precision, and whether list fields are sets.
7. Use date cutoffs from the task (`as_of`, `close_date`, `review_as_of`) when evaluating receipts, invoices, approvals, payments, budget snapshots, and risk events unless the template explicitly asks for current records.
