Individual skill

northwind-erp-decisions

Solve Northwind Components ERP decision tasks that combine local memos/templates with live API lookups and require exact JSON output. Use this whenever the prompt mentions the Northwind ERP API, orders, inventory, warehouses, customers, products, BOMs, purchase orders, incidents, suppliers, shipping quotes, expedite queues, replenishment plans, mixed-warehouse transfer decisions, supplier scorecards, or procurement quality holds, even if it does not explicitly say "Northwind" or "JSON".

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_007/fewshot/cc/fewshot_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 Decisions

Use this skill for the Northwind Components task family that turns live ERP data into strict JSON decisions.

## Read first

1. Open the prompt and every file in `input/payloads/`.
2. Treat `answer_template.json` as the contract. Copy its top-level keys, nested keys, enum values, precision, and ordering rules exactly.
3. Treat any memo file as policy. Follow its filters, date windows, and decision rules.
4. If the prompt says to return only JSON, return only JSON. No markdown, no code fences, no commentary.

## Recognize the task family

The template usually tells you what kind of work this is: