Menu

Individual skill

reflect-3_attempt_02

Not available

experiments/claude_code_kimi2_6_enabled/reports/skills/task_group_002/reflect-3/reflect-3_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
# MedBridge Sales Ops API Task Skill

## Overview
Tasks in this benchmark require querying a shared MedBridge Sales Ops API and producing JSON answers that match a strict `answer_template.json` schema. The API exposes collections: `customers`, `products`, `quotes`, `rfqs`, `freight-quotes`, `opportunities`, `invoices`, `payments`, `revenue-journals`, `events`, `vouchers`, and `policies`.

## General Approach
1. **Read the prompt and template first.** The prompt names a customer, quote/RFQ/opportunity ID, and product. The `input/payloads/answer_template.json` dictates the exact shape, field names, and enums of the answer.
2. **Fetch base collections** (`/api/customers`, `/api/products`, `/api/policies`) once, then query specific records by ID (`/api/quotes/<id>`, `/api/rfqs/<id>`, `/api/opportunities/<id>`, etc.).
3. **Use `/api/search?q=<text>`** when the prompt uses a name variant that does not match the API `customer_name` exactly.
4. **Derive all numbers from the API** (unit prices, freight costs, totals, balances). Do not hard-code.
5. **Match the template exactly.** Missing keys, extra keys, or wrong enum values lower the score even if the data is conceptually correct.

## Data Mapping Patterns

### Quotes / RFQs with Product Pricing