Menu

Individual skill

procureops-reconciliation

0upvotes

Solve ProcureOps procurement, receiving, AP, contract-change, and payment-release reconciliation tasks using the live API plus task-local payloads, with exact JSON outputs.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_006/self/self_attempt_03/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.

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 Reconciliation SOP

Use this skill for tasks that ask for ProcureOps readiness, receiving closeout, AP close, contract-change, or payment-release decisions. The usual deliverable is a single JSON object matching a task-local `answer_template.json`.

## Allowed Inputs And API Setup

- Read the prompt, the task-local answer template, and local payload files named by the prompt.
- Treat local payloads as scope hints and special business rules. Treat the ProcureOps API as the system of record for operational records.
- Use the base URL supplied by the runner or environment instructions. Start with `GET /`; endpoint names may differ from prose examples. In this environment family, AP and payments endpoints are exposed as `/ap_invoices` and `/payments`, not slash paths such as `/ap/invoices`.
- API collection responses are wrapped as:

```json
{"count": 0, "results": []}
```
Back to top