Menu

Individual skill

harborview-clinic-protocol-answers

0upvotes

Use for protocol-bound clinical decision-support tasks against the Harborview synthetic-clinic runtime API. Each task names a target case id and provides an answer_template.json contract; the job is to retrieve the case from the clinic runtime, apply the case's machine-readable clinic protocol, filter out seeded distractor records, and emit exactly one JSON object that conforms to the template. Covers the recurring families: adult respiratory / CAP assessment, pediatric head-injury triage, potassium repletion & escalation, care-management routing, and observation-window / protocol-gate retrieval.

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

# Harborview synthetic-clinic protocol answers

A task in this family gives you: (1) a `prompt.txt` naming a **target case id** and
what to decide, and (2) `input/payloads/answer_template.json` — the **exact output
contract**. Network access (base URL + allowed endpoints) is in a separate
`environment_access.md`. Your deliverable is **one JSON object** matching the
template, with no prose around it.

The answer is never a matter of general clinical judgment. Every scored field is
determined by **the case's data in the runtime** plus **the case's protocol** (also
in the runtime). Retrieve both, apply the protocol literally, and format to the
template.

## Golden rules
Back to top