Individual skill

northwind-erp-control-desk

Use this skill for Northwind Components ERP evaluation tasks that ask for strict JSON decisions using the shared ERP API, especially dispatch expedite queues, mixed-warehouse allocation, kit replenishment, supplier incident scorecards, procurement quality holds, inventory coverage, purchase orders, BOMs, shipping quotes, customers, suppliers, and products. It gives SOPs for API usage, field conventions, stock math, decision precedence, ordering, rounding, and common pitfalls.

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

Use this skill when a task gives a Northwind Components memo plus an `answer_template.json` and asks for a structured ERP decision file. The work is usually less about prose and more about carefully joining live ERP records, applying the memo policy, and emitting exact JSON.

## Access And Source Discipline

1. Read only the visible task prompt, payload memo/request files, `answer_template.json`, and the environment access note supplied for the run.
2. Use the ERP API base URL from the environment access note. If a prompt mentions local startup commands or a local `127.0.0.1` URL, treat that as task boilerplate unless the run explicitly provides that service. In this environment the remote API is the intended source.
3. Do not inspect environment source files, previous answers, hidden outputs, judge endpoints, or task folders outside the visible input area.
4. Start by requesting `GET /` from the base URL and confirm the available endpoint list. Quote URLs that contain `?` or `&` when using a shell, or the shell may interpret them as patterns.
5. Return only the JSON object requested by the template. Do not add explanation, markdown, comments, or extra keys.

## Core API Endpoints