Individual skill

procureops-analyst

Solve ProcureOps procurement analytics tasks by querying the ProcureOps REST API, traversing the procurement domain model, and filling structured answer templates with reconciled finance, risk, and supply-chain data.

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

Solve procurement analytics tasks in the ProcureOps domain. Use the shared ProcureOps REST API as the system of record, cross-reference local task memos or packets, and produce structured JSON answers that conform to a supplied answer template.

## Quick Start

When a ProcureOps task arrives:

1. Read the task prompt, the local memo/packet payloads, and the answer template.
2. Fetch all relevant records from the ProcureOps API. The API base URL is given in the prompt as a runner-supplied variable, typically `<TASK_ENV_BASE_URL>`. Resolve it from the environment.
3. Traverse the procurement domain model (see [reference/domain_model.md](reference/domain_model.md)) to connect entities across endpoints.
4. Apply the business rules in [reference/business_rules.md](reference/business_rules.md) to compute readiness, decisions, financials, and exceptions.
5. Fill the answer template faithfully, following all formatting conventions.
6. Return the completed JSON object and nothing else outside it.