Individual skill

solve-procureops-json

Solve ProcureOps operational reconciliation tasks that require JSON-only answers from a task prompt, local payload files, an answer template, and the shared ProcureOps API. Use for procurement sourcing readiness, receiving/AP variance closeout, AP payment holds, change-control budget/approval checks, supplier risk checks, chargeback net-release files, and similar tasks involving suppliers, items, programs, contracts, purchase requisitions, purchase orders, receipts, AP invoices, payments, approvals, budget snapshots, or vendor risk events.

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

## Operating Rules

Read the prompt, every file under `input/payloads/`, and the answer template before calling the API. Treat local payloads as the scope, business-rule overrides, and target ID source; treat the API as authoritative for operational records. Return only the JSON object requested by the template.

Do not reuse IDs, dates, names, amounts, or conclusions from prior examples. Derive every output value from the current task's prompt, payloads, template, and API responses.

## API Snapshot

Use the base URL supplied by the task runner or prompt. Fetch full endpoint lists and build local indexes by ID:

```bash
BASE="$TASK_ENV_BASE_URL"
Back to top