Menu

Individual skill

northwind-erp-control-desk

0upvotes

Use this skill for Northwind Components ERP tasks that ask for structured JSON decisions for dispatch, allocation, replenishment, procurement control, supplier quality scorecards, BOM kit builds, inventory availability, transfers, purchase orders, incidents, customers, products, warehouses, shipping quotes, or supplier controls. This skill is especially relevant when a prompt provides staged payloads and an answer template and expects exact operational JSON from the live ERP API.

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

# Northwind ERP Control Desk Workflow

Use this workflow to solve Northwind Components operational-control tasks that combine visible task payloads with the public ERP API. The goal is a strict JSON answer matching the provided template, not a narrative report.

## Ground Rules

Read only the prompt, visible payloads, answer template, and public ERP API records made available for the task. Treat the template as the contract: preserve required top-level keys, enum values, list ordering, date formats, and rounding rules exactly.

Before calculating, extract these items from the prompt and payloads:

- Task identifier, wave ID, memo/request ID, analysis window, plan date, target warehouses, order IDs, supplier IDs, BOM IDs, and build quantities.
- Required output keys and all allowed enum values.
- Required sorting rules for records, lines, suppliers, transfers, PO IDs, SKU lists, and summary lists.
- Currency and percentage precision.
Back to top