Menu

Individual skill

northwind-erp-control-json

0upvotes

Solve Northwind Components ERP control tasks that require strict JSON answers from local memo/template payloads and the shared Northwind ERP API. Use for expedite dispatch, mixed-warehouse allocation, kit replenishment, supplier incident scorecards, and procurement quality-hold reviews where Codex must fetch live ERP records, apply memo/template rules, compute inventory or incident metrics, and return only schema-conforming JSON.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_007/fewshot/naive/fewshot_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 ERP Control JSON

Use this skill when a Northwind Components task provides local payloads plus a shared ERP API base URL. Treat the prompt, memo files, and `answer_template.json` as the contract. Fetch live data from the public API; do not inspect environment files, judge APIs, source code, cached answer files, or hidden data.

## Core Workflow

1. Read the prompt, every local payload, and especially `answer_template.json`.
2. Identify the task family from the memo/template keys:
   - Expedite dispatch: order list plus per-order inventory/customer/shipping decisions.
   - Mixed allocation: order wave, line actions, transfer requests, blocked orders, rollup.
   - Kit replenishment: BOM targets, component coverage, transfers, requisitions, exclusions.
   - Supplier scorecard: incidents filtered by date and supplier-level metrics.
   - Procurement quality review: listed suppliers, recent incidents, held POs, release list.
3. Fetch all needed live records from the API base URL supplied in the task. Common endpoints are `/orders`, `/orders/<id>`, `/products`, `/products/<sku>`, `/customers/<id>`, `/inventory?warehouse_id=&sku=`, `/shipping/quote?warehouse_id=&destination_zip=&weight_lb=&speed=`, `/purchase_orders?supplier_id=&sku=&status=`, `/suppliers`, `/incidents?start=&end=&supplier_id=`, and `/boms/<id>`.
Back to top