Menu

Individual skill

procureops-solver

Solve ProcureOps procurement reconciliation tasks by reading the supplied payloads, fetching live API records, cross-referencing across endpoints, applying business rules, and returning template-conformant JSON.

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

## Overview

This skill handles procurement operations tasks that require reconciliation across a ProcureOps API and local task payloads. Every task follows the same pattern: consume a local memo or packet naming target entities, fetch live records from a shared ProcureOps API at `<TASK_ENV_BASE_URL>`, cross-reference those records across multiple endpoints, apply standard business rules, and return a single JSON object that exactly conforms to an answer template supplied in the payloads directory.

## API Access

All tasks use the same ProcureOps API. The base URL is always provided as `<TASK_ENV_BASE_URL>` by the runner. Authentication is none. Use only GET requests.

**Allowed endpoints** (every endpoint is read-only):

| Endpoint             | Description                              |
|----------------------|------------------------------------------|