Individual skill

procureops-analyst

Analyze ProcureOps procurement records from a shared REST API to produce structured JSON answers for sourcing nomination, receiving closeout, AP close, change-control, and AP release workflows. Use this skill whenever the task mentions ProcureOps, a ProcureOps API, procurement readiness, receiving closeout, AP close, change control, sourcing nomination, AP release, vendor reconciliation, purchase orders, requisitions, contracts, budget snapshots, invoices, payments, or any supplier-facing procurement data analysis that references a shared task-environment API.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_006/fewshot/cc/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 Analyst

Produces structured JSON answers for procurement workflows by fetching ProcureOps REST API records, cross-referencing them by foreign key, and applying task-specific computation rules.

## How to use this skill

When a task references the ProcureOps API at a task-environment base URL, follow the workflow below. Read [references/api_schema.md](references/api_schema.md) when you need endpoint shapes or field details.

Start by reading the task prompt and every local payload file under the input directory. Then fetch the API records you need, cross-reference them by their foreign keys, compute the required values, and produce a single JSON answer matching the task's answer template.

## Workflow

### 1. Read the task and local inputs