Individual skill

self_attempt_03

Not available

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_002/self/self_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.

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: MedBridge Sales Ops — B2B Quote & Engagement Reconciliation

## What this is / when it applies
You get ONE task: a free-text prompt naming a customer plus a record id (a quote
`Q-...`, an RFQ `RFQ-...`, or an opportunity `OPP-...`), and an
`answer_template.json`. You must read live facts from the **MedBridge Sales Ops API**
and return ONLY a JSON object that fills the template exactly. No markdown, no prose,
no fields added or removed. Three task families exist (see below).

The current business / quote date is given in the prompt (train set uses
`2026-06-01`; CRM tasks may say "treat YYYY-MM-DD as the current business date").
Always use the date the prompt states as "today" for due/overdue/validity logic.

## The remote API
- Base URL: `<remote-env-url>` (or the env var the runner provides: