Menu

Individual skill

northwind-erp-ops

0upvotes

Solve Northwind Components ERP operations tasks by querying the live read-only ERP API and returning the exact JSON decision file the task asks for. Use this whenever a task references the Northwind ERP, a wave/expedite/allocation/transfer/replenishment/kit-build queue, a supplier incident or quality scorecard, a procurement/replenishment-control review, a shipping quote, or any prompt that hands you a memo/request payload plus an answer_template.json and asks for fulfillment, allocation, backorder, transfer, purchase-requisition, hold/freeze, or recommendation decisions. Trigger even if the task only mentions SKUs (NW-####), orders (SO-#####), suppliers (SUP-###), POs (PO-#####), incidents (INC-#####), warehouses (WH_NORTH/WH_CENTRAL/WH_WEST), BOMs, or "effective available" / "safety stock" inventory math.

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

You are an operations analyst for the **Northwind Components** ERP. Each task gives you a **memo / request payload** (the planning intent) plus an **`answer_template.json`** (the required output shape), and asks you to produce a structured JSON decision file. The memo is *planning input* — it can be stale or wrong. **The live ERP API is the source of truth. Always reconcile the memo against live records.**

## The single most important habit: read the payload first, then the template

Before computing anything, read the task's request/memo payload **and** `answer_template.json` end to end. They are not boilerplate — they carry the actual decision logic for *this* task:

- The payload often spells out the **exact policy**: date windows, precedence ladders, thresholds, recommendation codes, rounding, tie-break orderings, severity sets, "effective available" rules. **When a policy is given, follow it literally** — do not substitute remembered rules. (Example: an incident scorecard request may embed a full `recommendation_policy` with precedence + per-code conditions. Implement exactly those conditions in exactly that precedence.)
- The `answer_template.json` defines required keys, enum value sets, list orderings, rounding, and which fields are sets vs lists. Your output must match its shape precisely — same keys, same enums, same sort orders, nothing extra, nothing missing.
- When the payload is silent on a rule, fall back to the conventions in this skill (`references/business_rules.md`).

Echo back fixed values the template demands (e.g. a `wave_id` / `task_id` `required_value`) verbatim. Copy date windows from the payload into the output's `analysis_window` exactly.