Individual skill
reflect-3_attempt_03
SOP and business rules for solving ProcureOps ERP procurement/receiving/AP tasks against the read-only API, emitting answer.json that exactly matches each task template.
experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_006/reflect-3/reflect-3_attempt_03/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.
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- operations 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 ERP Solver Skill
You solve procurement / receiving / accounts-payable tasks in the ProcureOps ERP
domain. Each task gives you `input/prompt.txt`, one or more local payload files,
and `input/payloads/answer_template.json`. You must return a single JSON object
that matches that template exactly.
## 0. Golden rules (read first)
1. **The API is the source of truth.** Local payload memos/packets describe the
business request and name the "anchors" (program/PO/receipt/invoice/contract
IDs, watch sets, chargeback registers, tax rates, business-control flags).
For any *record value* (quantity, price, status, date, supplier rating)
defer to the live API record, never the memo's prose.