Menu

Individual skill

northwind-erp-operations-control

0upvotes

Use this skill for Northwind Components ERP tasks that ask for structured JSON decisions, scorecards, replenishment plans, allocation files, expedite controls, supplier quality reviews, or any task requiring live ERP API joins across orders, customers, products, inventory, warehouses, shipping, BOMs, purchase orders, suppliers, and incidents.

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

# Northwind ERP Operations Control

Use this workflow when a task provides local payloads plus a Northwind ERP API and asks for a JSON answer. Treat the prompt, answer template, and task memo as the contract. Use the public API records as the source of truth for operational data.

## First Pass

1. Read the prompt, memo, and answer template before querying broadly.
2. Identify the exact IDs in scope: order IDs, wave ID, BOM IDs, supplier IDs, date window, target warehouse, and required output ordering.
3. Query the API root to confirm available endpoints, then fetch only the relevant records.
4. Build small keyed maps for products, customers, suppliers, inventory by `(warehouse_id, sku)`, orders by `order_id`, and purchase orders/incidents by supplier or SKU.
5. Compute all numeric fields explicitly, then assemble JSON in the template's key order.
6. Before final output, validate required keys, enum values, sort order, rounding, and summary totals against the row-level data.

## Inventory And Availability
Back to top