Menu

Individual skill

fewshot_attempt_02

0upvotes

Not available

experiments/claude_code_kimi2_6_enabled/reports/skills/task_group_007/fewshot/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.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

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.

Declared tags are partial or unavailable.

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
# Skill: Northwind Components ERP Decision Tasks (task_group_007)

## Overview
These tasks require querying a shared Northwind ERP API (default `http://127.0.0.1:8007`) and producing strictly-formatted JSON decisions. The output schema is always defined in `input/payloads/answer_template.json` and must be matched exactly. Each task is driven by a memo or request file in `input/payloads/`.

## General Workflow
1. Read the task prompt (`input/prompt.txt`) to identify the decision type.
2. Read the answer template (`input/payloads/answer_template.json`) to learn the exact required keys, types, enums, and sorting rules.
3. Read any memo/request payload in `input/payloads/` for target IDs, date windows, or policy rules.
4. Start or connect to the ERP API (base URL from prompt/memo, typically `http://127.0.0.1:8007`).
5. Fetch live records for every entity referenced. Do not use cached or assumed inventory snapshots.
6. Apply the business rules described in the memo/template, compute derived values, and assemble the JSON.
7. Validate: correct keys, correct enum values, all lists sorted per template, currency rounded to 2 decimals, percentages rounded as specified.
8. Return **only** the JSON object.
Back to top