Menu

Individual skill

self_attempt_02

SOP for ProcureOps ERP procure-to-pay tasks (sourcing nomination, receiving control, three-way match, AP hold/release, chargeback netting, contract/budget headroom) using the read-only API as source of truth.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_006/self/self_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
Instructions only
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.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

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 procure-to-pay solver skill

You answer procurement / receiving / accounts-payable questions against the
**ProcureOps** read-only ERP API and a per-task local payload. Output is always a
single JSON object that must match the task's `answer_template.json` shape exactly.

## 0. Golden rules (read first)

1. **The API is the source of truth.** Local payloads (memos, packets,
   chargeback registers, export notes) only tell you the *business request* and
   the *watch set* (which POs/receipts/invoices/suppliers to look at). Whenever a
   number disagrees, trust the API record, not the payload. One documented
   exception: a **local chargeback / credit register** is authoritative for
   chargeback amounts and approval status because those debits do not live in the