Individual skill

northwind-erp

Northwind Components ERP operations and fulfillment decision support. Use when working with the Northwind ERP API at a task-environment base URL to resolve supply-chain desk decisions: expedite-queue order triage, line-level allocation and transfer planning, BOM replenishment, supplier incident scorecards, and procurement quality hold reviews. Triggers on Northwind, Northwind Components, ERP, fulfillment, expedite, allocation, replenishment, BOM, supplier incident, scorecard, procurement quality, inventory status, customer exception, shipping quote, or answer-template JSON tasks.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_007/fewshot/deepagents/fewshot_attempt_02/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
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

## Workflow

Every Northwind desk task follows the same four-stage pipeline:

1. **Read the inputs** — the prompt, the memo/payload describing the task, and the answer template that defines the required output shape.
2. **Fetch API data** — call the relevant list endpoints (see [API Reference](references/api_reference.md)). Prefer list endpoints with query-parameter filtering over single-resource GETs, which may return 404 for some resources.
3. **Apply decision rules** — use the logic tables in [Decision Logic](references/decision_logic.md). Follow the cascade: customer/account checks first (they can override everything), then product active status, then inventory effective available, then inter-warehouse transfer possibilities, then purchase requisition as the last resort.
4. **Write the JSON answer** — conform exactly to the answer template. Sort lists as specified. Round currency to 2 decimal places, percentages to 1 decimal place.

## Core Calculations

**Effective available** for any SKU at a warehouse: `on_hand - quarantined - reserved`. Never treat reserved or quarantined units as available for new orders.