Individual skill

procureops-task-solver

Solve ProcureOps task-group JSON packets from local memos and the shared task API. Use when prompts reference ProcureOps, the task environment, and templates for nomination readiness, receiving closeout, AP close, change-control, or AP release decisions.

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

Browse files

SKILL.mdcore · 3,869 bytes
SKILL.mdcore · 3,869 bytes
agents/openai.yamlasset · 257 bytes

Read excerpt


# ProcureOps Task Solver

## Overview
Use this skill to turn a task-local memo or packet plus the ProcureOps API into the exact JSON requested by the template.

## Procedure
1. Read the prompt, the answer template, and every local payload file first.
2. Read `environment_access.md` to get the task API base URL and allowed endpoints.
3. Call `GET /manifest` first, then fetch only the record collections needed for the packet.
4. Treat the API as source of truth. Use local payloads for target IDs, dates, aliases, chargeback excerpts, and other task-scoped hints.
5. Resolve IDs outward from the memo to programs, suppliers, items, requisitions, contracts, purchase orders, receipts, invoices, approvals, budget snapshots, payments, and vendor-risk events.
6. Fill the answer template exactly. Return JSON only.

## Shared Rules