Individual skill
task-group-006-fewshot-attempt-03
Solve ProcureOps procurement, receiving, AP close, change-control, and release-decision tasks that provide local input payloads plus a shared ProcureOps API, returning strict JSON matching the task answer template.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_006/demonstration_skill/demonstration_skill_attempt_03/demonstration-skill-attempt-03/SKILL.md
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# ProcureOps JSON Answer Skill
Use this skill for task-group prompts that ask for a JSON answer from local payload files and the ProcureOps API. The local payload names the target records and sometimes adds business controls; the API is normally the source of truth for operational records.
## Core Workflow
1. Read the prompt, every file under the task's `input/payloads/`, and the answer template.
2. Query the ProcureOps service. Use the base URL from the prompt/runner, commonly `<environment_base_url>`. If localhost curl uses a proxy, call it as `curl --noproxy '*' -sS "$BASE/<endpoint>"`.
3. Extract only records in scope:
- IDs explicitly named in the prompt or local payload.
- Records linked to those IDs by `po_id`, `receipt_id`, `invoice_id`, `supplier_id`, `program_id`, `contract_id`, `requisition_id`, or `sku`.
- For slice/close tasks, do not include unrelated records just because they share a supplier or program unless the template asks for aggregated context.
4. Derive fields and controlled decisions from the template wording. Return only one JSON object. Do not include prose.
5. Sort all ID lists ascending unless the template says otherwise. Treat set fields as de-duplicated. Round USD amounts to cents; use requested quantity precision for quantities and percentages.