Menu

Individual skill

northwind-erp-control-desk

0upvotes

Use this skill for Northwind Components ERP tasks that require joining API records with a local memo and returning strict JSON decisions for order dispatch, inventory allocation, BOM replenishment, supplier incident scorecards, or supplier quality hold controls. Trigger whenever the user mentions Northwind ERP, shared ERP API, orders, waves, warehouses, inventory, BOMs, purchase orders, incidents, suppliers, allocation, expedite queues, replenishment, or supplier quality review.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_007/self/self_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 Control Desk SOP

This skill is for solving Northwind Components tasks that provide a prompt, a local memo/request file, an answer template, and a live ERP API. The winning pattern is disciplined data joining: read the task contract, fetch only the relevant ERP records, compute derived fields explicitly, then emit exactly the JSON shape requested by the template.

## First Pass

1. Read the task prompt, every visible memo/request payload, and the answer template before calling the API.
2. Treat the answer template as the output contract. Mirror its top-level keys, enum strings, sort orders, summary fields, and rounding rules.
3. Use the API base URL supplied by the runner or environment access note. The public API index is available at `GET /`; use it to confirm endpoints.
4. Do not inspect local environment source files, hidden answer files, judge endpoints, prior runs, or any gold outputs. The API and visible task inputs are enough.
5. Keep scratch calculations in tables or short scripts when the task has more than a few records. These tasks are easy to get wrong by mental arithmetic.

Common API endpoints:
Back to top