Individual skill
reflect-3
Use this skill for ProcureOps procurement, receiving, AP close, AP release, sourcing nomination, contract amendment, budget, supplier-risk, purchase-order, receipt, invoice, payment, and chargeback reconciliation tasks. It is especially useful when the user provides a local memo or packet plus a ProcureOps API and asks for strict JSON matching a template.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_006/reflect-3/reflect-3_attempt_02/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
Read excerpt
# Reflect-3 ProcureOps Reconciliation
Use this workflow when a task asks for a controlled ProcureOps decision file or reconciliation JSON. The recurring pattern is: a local prompt and payload define scope and business rules, while the ProcureOps API supplies operational records.
## Source Precedence
1. Read the prompt, answer template, and every task-local payload before querying data.
2. Treat the answer template as the contract for field names, enum values, nullability, ordering, and rounding.
3. Treat local memos or packets as authoritative for scope, target IDs, review/as-of dates, special business rules, chargeback registers, stale-alias notes, and locally supplied control assumptions.
4. Treat the ProcureOps API as authoritative for live program, supplier, item, requisition, contract, PO, receipt, invoice, approval, budget, payment, and vendor-risk facts.
5. If a local note says old aliases are absent from the shared environment and provides generated IDs, use the generated IDs. Do not invent missing legacy IDs.
6. Do not expand a task's target package merely because other historical records share a requisition, contract, supplier, or SKU. Use same-object records only when the template asks for context such as excluded same-PO receipts, contract usage, payment schedules, or supporting evidence.
## API Habits