Menu

Individual skill

northwind-erp-control

0upvotes

Solve Northwind Components / Northwind ERP tasks that turn a memo plus live task-environment API data into a strict JSON decision file. Use this skill whenever the prompt mentions Northwind, `<TASK_ENV_BASE_URL>`, `answer_template.json`, dispatch queues, replenishment plans, allocation waves, supplier scorecards, incident reviews, or any other memo-driven ERP workflow that must come back as schema-locked JSON.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_007/fewshot/opencode/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
Yes
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

Use this skill for the Northwind control-desk pattern: read the task memo, query the live ERP API, and return JSON that matches the provided template exactly.

## Workflow
1. Read the prompt, memo, and `answer_template.json` together. Treat the template as the shape contract and the memo as the policy source.
2. Identify the task family and its governing rules: date window, target orders or suppliers, build quantities, exception codes, numeric precision, and sort order.
3. Query only the public task environment API from the prompt's `<TASK_ENV_BASE_URL>`. Use the smallest set of endpoints needed for the task. Common endpoints are:
   - `/manifest` for field discovery when the response shape is unclear
   - `/orders`, `/customers`, `/products`, `/inventory`, `/warehouses`, `/shipping/quote`
   - `/boms`, `/purchase_orders`
   - `/incidents`, `/suppliers`
4. Derive every output field from live records. Do not reuse old answers, cached snapshots, or memo text as if it were ground truth.
5. Build the final object in scratch space first, then serialize it as plain JSON only. Do not add markdown, commentary, or code fences.
Back to top