Individual skill
procureops-json-reconciler
Solve ProcureOps packet tasks that combine a local memo/packet with the shared ProcureOps API and require exact JSON output for nomination readiness, receiving closeout, AP close, change-control, or release/hold decisions. Use this whenever a prompt asks for a structured JSON answer from ProcureOps records, especially when the packet names target IDs, a date slice, or an answer template.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_006/fewshot/cc/fewshot_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.
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
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# ProcureOps Packet Reconciler
Use this skill for ProcureOps tasks where the answer is a strict JSON object built from a local packet plus the shared ProcureOps API.
## Core Workflow
1. Read the prompt, all packet files under `input/payloads/`, and the answer template before you look at the API.
2. Treat the packet as the scope definition and the API as the source of truth. If they conflict, trust the API for record facts and the packet for task scope.
3. Identify the task family: nomination readiness, receiving closeout, AP close, change-control, or AP release/hold.
4. Start from the IDs named in the packet, then walk outward through linked records: program, supplier, item, requisition, contract, PO, receipt, invoice, payment, approval, budget, and vendor risk.
5. Use `/manifest` first only when you need a quick inventory of anchor IDs or record counts.
6. Build the output to match the template exactly. Preserve key names, nesting, enum values, rounding, and list ordering.
7. Return JSON only. No prose, markdown, or extra wrapper text.
