Individual skill
procureops-erp-answers
Produce the required JSON answer for ProcureOps ERP "Procurement Supplier and Receiving Control" tasks: sourcing nomination readiness, receiving/AP three-way reconciliation, AP close hold/release queues, contract + budget change-control decisions, and AP release/chargeback netting. Use this whenever a task points at the ProcureOps API (a localhost service exposing /programs, /suppliers, /contracts, /purchase_orders, /receipts, /ap/invoices, /ap/payments, /approval_events, /budget_snapshots, /vendor_risk_events) and asks for a JSON answer matching an answer_template.json, even if the prompt only says "nomination packet", "receiving closeout", "AP close", "change control decision file", "release file", "budget headroom", "vendor risk", or "reconciliation". Treat the live API as the source of truth over any local memo/export. Reach for this skill before hand-rolling any procurement/AP/ERP computation.
experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_006/demonstration_skill/demonstration_skill_attempt_01/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
- 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
SKILL.mdcore · 9,336 bytesSKILL.mdcore · 9,336 bytesSKILL.mdcore · 9,336 bytesreferences/api_fields.mddoc · 4,556 bytesreferences/business_rules.mddoc · 11,212 bytesreferences/task_families.mddoc · 3,274 bytesscripts/validate_answer.pyruns · 3,023 bytes
Read excerpt
# ProcureOps ERP answer builder
You are turning a task prompt plus a local memo/payload into one JSON object that
matches a provided `answer_template.json`, using the live ProcureOps ERP API as
the system of record. The five task families you will see are nomination
readiness, receiving/AP reconciliation, AP close, change-control decision, and
AP release/chargeback netting — but the *mechanics* below transfer to any
unseen task in this domain. Lead with the rules, not with memorized answers.
## Golden rules (true for every task)
1. **The API is the source of truth; the local memo is a pointer, not data.**
Memos and exports name the anchors (program, POs, invoices, receipts) and
give business controls (tax rate, cutoff date, "exclude cancelled POs",