Menu

Individual skill

task-group-007-fewshot-attempt-03

0upvotes

Use for Northwind Components ERP decision tasks that require JSON answers built from task memos/templates plus the shared ERP API, including expedite dispatch, transfer allocation, kit replenishment, supplier incident scorecards, and procurement quality holds.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_007/demonstration_skill/demonstration_skill_attempt_03/demonstration-skill-attempt-03/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 Skill

## Core Workflow

1. Read the prompt, payload memo, and answer template first. The template is the contract: preserve its top-level keys, field names, enums, sorting rules, and rounding precision.
2. Use the public ERP API for live records. Do not inspect environment source files or cached internal data.
3. Resolve only the population requested by the memo:
   - If the memo lists explicit order IDs or supplier IDs, use only those IDs, even when an API wave/query returns additional records.
   - If the memo asks for an entire wave, include every order/line in that wave.
   - If the memo defines an incident window, filter incidents by `open_date` inclusively.
4. Join records from the relevant endpoints, compute the requested classifications and summaries, then return one JSON object only.
5. Sort every list exactly as the template states. Sort IDs lexicographically unless a different ordering is specified.

## API Usage