Individual skill

northwind-erp-decision-json

Use this skill whenever a task asks for a Northwind Components or shared ERP API dispatch, allocation, replenishment, procurement-control, supplier incident scorecard, BOM, inventory, purchase order, shipping quote, or answer_template JSON. It helps Codex read local task payloads, query the public ERP API, compute decisions and summaries, and return strict JSON matching the provided template.

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

Use this skill for Northwind Components tasks where local payload files define a memo/request and an `answer_template.json`, and the correct answer must be computed from the shared ERP API.

The goal is a single valid JSON object. Do not return markdown fences, commentary, assumptions, or partial records unless the user explicitly asks for analysis instead of the final answer.

## Files To Use

1. Read the user prompt and every file under `input/payloads/`.
2. Treat the local memo/request as task configuration: target IDs, dates, wave names, requested warehouses, build quantities, recommendation policies, allowed actions, sort rules, and precision rules.
3. Treat the public ERP API as the source of truth for live records. Do not inspect task-environment source files, database files, fixtures, or hidden evaluator files.
4. Read `input/payloads/answer_template.json` before computing. Build the output from that template, not from memory.

Optional helpers bundled with this skill:
Back to top