Individual skill

procureops-finops

Structured analysis of ProcureOps procurement and financial-operations data through a shared REST API. Use when the task is to produce a machine-readable JSON answer (reconciliation, nomination, change-control, AP close, or receiving-release file) from ProcureOps API records and task-local memos. The API exposes suppliers, items, programs, contracts, purchase requisitions, purchase orders, receipts, AP invoices, AP payments, approvals, budget snapshots, and vendor risk events. All amounts are in USD.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/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
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
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 FinOps Analysis

## Quick start

1. Read the task prompt and any task-local payload files (memos, templates, registers).
2. Pull all relevant endpoint data from `<TASK_ENV_BASE_URL>` in a single batch of parallel fetches.
3. Cross-reference records across endpoints using the entity relationship map.
4. Apply the calculation patterns below to produce the required numeric values.
5. Return only valid JSON matching the supplied answer template. No prose outside the JSON.

## Endpoints

Fetch all relevant endpoints in parallel the first time. Re-fetch only when additional data is needed.