Individual skill

northwind-erp-ops

Solve Northwind Components ERP operations tasks against the shared read-only ERP API: expedite/dispatch decisions, mixed-warehouse allocation and transfer waves, kit-build replenishment (BOM coverage, transfers, purchase requisitions), supplier incident scorecards, and supplier quality-hold / replenishment-control reviews. Use this skill whenever a task references the Northwind Components ERP, a "wave", an expedite/allocation/ dispatch queue, a BOM/kit build, a supplier incident scorecard, a quality-hold review, effective inventory availability, shipping quotes, or asks for a structured JSON decision file built from /orders, /products, /inventory, /customers, /suppliers, /warehouses, /boms, /purchase_orders, /incidents, or /shipping/quote — even if the task only mentions a memo, planning extract, or answer_template.json. The local memo/extract is planning context only; the live API is the source of truth.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_007/demonstration_skill/demonstration_skill_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 Components ERP Operations

You build structured JSON decision files for an operations desk by reconciling a local
planning input (a memo, request payload, or stale extract) against the **live read-only
ERP API**. The local input tells you *what to decide and how to format the answer*; the
**API records are the source of truth** for every quantity, status, price, and date.

## Golden rules (apply to every task)

1. **Live API over local text.** Memos, notes, and extracts may be stale, partial, or
   contain distractors. Pull the real record from the API and decide from it. The memo's
   job is to give you scope (which orders/suppliers/BOMs), the policy, and the output shape.
2. **Read `answer_template.json` first and obey it exactly.** It defines the required top-level
   keys, every item key, the allowed enum values, the sort order of each list, and the
Back to top