Individual skill

procureops-reconciliation

Solve ProcureOps sourcing nomination, receiving closeout, AP close, change-control, and release JSON tasks from a local packet or memo plus the live ProcureOps API. Use when a prompt asks for a strict JSON object that reconciles procurement records, budgets, approvals, receipts, invoices, vendor risk, or chargebacks.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_006/fewshot/codex/fewshot_attempt_02/SKILL.md

Read pinned source

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
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 · 3,391 bytes
SKILL.mdcore · 3,391 bytes
SKILL.mdcore · 3,391 bytes
agents/openai.yamlasset · 242 bytes

Read excerpt


# ProcureOps Reconciliation

## Overview
Use this skill for packet-driven ProcureOps tasks that must return JSON only. Treat the memo or packet as scoping guidance and the ProcureOps API as the source of truth.

## Workflow
1. Read the prompt and answer template first. Capture required keys, allowed enums, sort order, precision, and the as-of date.
2. Use the packet or memo to identify target IDs, aliases, and any special scope notes. Use live API records for values.
3. Query only the record families the template needs: programs, suppliers, items, requisitions, contracts, purchase orders, receipts, invoices, approvals, payments, budget snapshots, vendor-risk events, and chargebacks or hold records.
4. Populate the JSON directly from the template. Do not add prose, commentary, markdown, or extra keys.
5. Normalize values exactly:
   - Round USD to cents unless the template asks for another precision.
   - Sort ID lists ascending unless the template says they are sets or already sorted by a field.
   - Use `0.00`, `0`, `null`, or `[]` only when the template or prompt calls for them.