Menu

Individual skill

procureops-packet-builder

0upvotes

Build structured ProcureOps JSON packets from task-local memos/templates and live API records for sourcing nomination, receiving closeout, AP close reconciliation, contract change control, and AP release or hold workflows. Use when a task mentions ProcureOps, the shared task environment, a local memo or answer template, or asks for a JSON decision file, reconciliation packet, hold or release queue, or nomination packet.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_006/fewshot/opencode/fewshot_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 Packet Builder

## Overview
Produce one JSON object that matches the task template exactly. Treat the memo and answer template as the output contract; treat ProcureOps API data as the source of truth for records, IDs, and calculations.

## Workflow
1. Read `input/payloads/answer_template.json` and the local memo first.
2. Extract the scope IDs, dates, and any explicit business rules from the memo.
3. Use the runner-provided ProcureOps base URL and read `/manifest` when you need current anchor IDs or record counts.
4. Fetch only the records in scope from ProcureOps.
5. Cross-check memo claims against live records; prefer live records when they conflict.
6. Compute every field from source data, not from assumptions.
7. Sort set-like lists ascending unless the template says otherwise.
8. Round USD amounts to cents and ratios or percentages to the precision named by the template.
Back to top