Menu

Individual skill

procureops-control-file-reconciler

0upvotes

Reconcile ProcureOps API records and local task memos into strict JSON control files for nomination readiness packets, receiving closeouts, AP close reconciliations, change-control decisions, and AP release/hold reviews. Use this skill whenever a prompt mentions ProcureOps, `<TASK_ENV_BASE_URL>`, a local memo/payload folder, or an `answer_template.json` and asks for exact JSON only.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_006/fewshot/opencode/fewshot_attempt_01/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 Control File Reconciler

Use this skill for structured ProcureOps tasks that end in a single JSON object.

## Workflow
1. Read the prompt, the local memo or payload files, and the answer template together. Treat the template as the schema contract.
2. Use the ProcureOps API as the source of truth for live records. Use the runner-provided base URL from the task environment; do not hardcode it.
3. Identify the task family and follow [references/procureops-playbook.md](references/procureops-playbook.md).
4. Populate the JSON exactly as the template requires. Do not add prose, markdown, or extra keys.
5. Before finalizing, verify sorting, rounding, enum values, and source IDs against the template.

## Non-negotiable rules
- Prefer API records over memo wording when they differ.
- Use the memo for scope, aliases, cutoff dates, and local hints the API cannot express.
Back to top