Individual skill

procureops-packets

Solve ProcureOps packet tasks that ask for a readiness packet, closeout reconciliation, change-control decision, AP release file, AP close, or similar structured JSON output built from the shared ProcureOps API and task-local payloads. Use this whenever a prompt mentions ProcureOps, TASK_ENV_BASE_URL, input/payloads/answer_template.json, or one of those packet types.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_006/fewshot/cc/fewshot_attempt_01/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: Yes
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.

Browse files

SKILL.mdcore · 3,072 bytes
references/procureops_workflow.mddoc · 3,626 bytes

Read excerpt


# ProcureOps Packets

Use this skill for structured ProcureOps JSON tasks. The output contract is always the same: read the local payloads and answer template, query the live ProcureOps API, compute the requested fields, and return JSON only.

## Workflow

1. Read `input/prompt.txt`, every file under `input/payloads/`, and `input/payloads/answer_template.json` first. Treat the template as the schema contract.
2. Read `environment_access.md` to get `TASK_ENV_BASE_URL`.
3. Fetch `GET /manifest` if you need to confirm the environment or record counts.
4. Query only the endpoints the packet needs: `/items`, `/suppliers`, `/programs`, `/contracts`, `/purchase_requisitions`, `/purchase_orders`, `/receipts`, `/ap/invoices`, `/ap/payments`, `/approvals`, `/budget_snapshots`, `/vendor_risk_events`.
5. Build an evidence map keyed by the IDs named in the memo and template. Prefer live records over local notes when they conflict.
6. Compute the derived fields from live records and the template rules.
7. Serialize the final object exactly to the template shape. No prose, no markdown, no extra keys.
8. Before returning, sort, deduplicate, and round exactly as requested.