Menu

Individual skill

procureops-solver

0upvotes

Solve ProcureOps operational-data tasks using the shared ProcureOps REST API. Use this skill whenever the task involves ProcureOps records (programs, suppliers, items, contracts, purchase orders, receipts, AP invoices, payments, approvals, budgets, vendor risk events) or references a ProcureOps API base URL. Trigger on mentions of procurement, sourcing, receiving, AP close, change control, chargebacks, nomination packets, exception review, or any ProcureOps domain term. Do not attempt to solve these tasks without this skill.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/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
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.

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 Solver

Solve structured procurement-operations tasks that require querying a shared
ProcureOps REST API, cross-referencing records across endpoints, applying
business rules, and filling a JSON answer template.

## Core Workflow

Every ProcureOps task follows this sequence:

1. **Parse the prompt and payloads.** Identify which API endpoints are needed,
   what local memos constrain the scope, and what the answer template requires.
   The prompt may name specific programs, suppliers, receipts, invoices, or POs;
   treat those as the initial scope anchor.
Back to top