Menu

Individual skill

procureops-json-solver

0upvotes

Solve ProcureOps task-environment questions that require a strict JSON answer from purchasing, receiving, AP invoice/payment, supplier-risk, budget, approval, contract, sourcing nomination, change-control, or chargeback records. Use this when a prompt mentions the ProcureOps API, TASK_ENV_BASE_URL, purchase orders, receipts, AP holds, supplier risk, contract amendments, release files, or answer_template.json.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_006/fewshot/opencode/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 JSON Solver

## Core Workflow

1. Read the user prompt, every local payload, and `answer_template.json` before fetching records. Treat the template as the output contract: required keys, enum spellings, sorting rules, precision, nullability, and whether list fields are sets.
2. Extract the task slice from the payloads: target dates, program IDs, PO IDs, receipt IDs, invoice IDs, requisition IDs, contract IDs, supplier IDs, SKUs, quantities, tax rates, and any local registers or notes.
3. Fetch ProcureOps records from the base URL supplied by the runner. The local memo usually names anchors; the API is the system of record unless the prompt explicitly makes a local payload authoritative for a control table such as a chargeback register.
4. Join records through IDs, calculate fields from source records, and classify decisions using the controlled values in the template. Do not rely on narrative shortcuts when a source record can verify the value.
5. Return only the final JSON object. Use JSON numbers for amounts and quantities, `null` where the template permits null, and no prose outside the object.

The helper script can snapshot the public API without external dependencies:

```bash
python scripts/fetch_procureops.py "$TASK_ENV_BASE_URL" /tmp/procureops_snapshot.json
Back to top