Menu

Individual skill

fewshot_attempt_01

0upvotes

Not available

experiments/claude_code_kimi2_6_enabled/reports/skills/task_group_003/fewshot/fewshot_attempt_01/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 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
# Task Group 003 – CRM Service Ticket & Case Resolution SOP

## 1. Input / Output Conventions
- The solver receives one or more payload files plus an `answer_template.json`. **Use the template schema exactly**; do not add or remove fields.
- **Preserve order**: arrays of decisions must follow the ascending order of `case_id` or `ticket_id` as they appear in the input payload, unless the template explicitly says otherwise.
- **Empty / default values**:
  - String fields that are not applicable → `""`
  - Numeric fields that are not applicable → `0.0`
  - Boolean fields that are not applicable → `false`
- **Summary blocks** (e.g., `batch_summary`, `queue_summary`, `worklist_summary`) must be derived directly from the decision array. Counts must be exact integers and keys must match the enums/status values defined in the template.
- **Enum casing**: use the exact uppercase, underscore-separated values shown in the template (e.g., `PENDING_ACTION`, `TIER2_SUPPORT`, `DEVICE_SETTING_FIX`).

## 2. Remote API Endpoints to Inspect
The environment exposes the following endpoints. Query them when the payload does not supply the needed state, or when the task explicitly requires live data.
Back to top