Menu

Individual skill

northwind-erp-structured-decisions

0upvotes

Use this skill for Northwind Components ERP tasks that require a strict JSON answer from live API records, especially prompts about expedite queues, allocation waves, BOM kit replenishment, purchase orders, supplier incidents, supplier quality holds, inventory coverage, shipping quotes, or operational control decisions. Trigger this whenever the user provides a Northwind ERP prompt with an answer_template.json or asks for a structured dispatch, replenishment, allocation, or supplier-quality decision file.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_007/reflect-3/reflect-3_attempt_02/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

# Northwind ERP Structured Decisions

Use this workflow to solve Northwind Components ERP tasks that combine staged task inputs with live public API data and require JSON matching a provided answer template.

## Ground Rules

Read the task prompt, every visible input payload, and the answer template before querying the API. The template is the contract: preserve required keys, enum values, sort orders, field names, number precision, and JSON-only output.

Use only the public ERP API and the task's visible input files. Do not inspect environment source directories, hidden outputs, answer files, eval reports, or unrelated attempts. During test solving, do not use any training or judging endpoint.

Build small local indexes after fetching API data:

- Products by `sku`
- Customers by `customer_id`
Back to top