Menu

Individual skill

clinic-protocol-decision-support

0upvotes

Produce a single strict-JSON answer for a protocol-bound clinical decision-support task against the synthetic Harborview / GDPEVO clinic runtime. Use whenever a prompt names a target case id like CASE-XXX-NNN, points to a runtime at <TASK_ENV_BASE_URL> with GET /api/... endpoints, and requires output conforming to input/payloads/answer_template.json. Covers adult respiratory / CAP assessment, pediatric head injury triage, potassium repletion, observation-window / protocol-gate retrieval, and care-management routing — and generalizes to unseen case types that follow the same shape.

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

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

# Clinic protocol decision-support (GDPEVO synthetic clinic)

## What these tasks look like

Every task in this family shares one shape:

1. A `prompt.txt` names exactly **one target case id** (e.g. `CASE-RESP-102`) and tells
   you to review it in a runtime environment at `<TASK_ENV_BASE_URL>`.
2. `input/payloads/answer_template.json` is a **strict contract**: required top-level
   keys, enum-constrained values, types, null rules, numeric precision, and ordering
   rules. This file — not your medical judgment about wording — defines every allowed
   value. Read it first and last.
3. A separate `environment_access.md` lists the base URL, credentials (usually `none`),
   and the exact allowed endpoints for this run.
Back to top