Menu

Individual skill

clinic-protocol-structured-response

0upvotes

Produce a single strict-JSON answer for protocol-bound clinical decision-support tasks against a synthetic FHIR-like clinic runtime. Use when a task gives a target case id, points to a runtime clinic environment (patients, cases, observations, medications, allergies, problems, imaging, registry, SDOH, protocols) plus a separately-listed access description, and asks for a JSON object conforming to an answer_template.json (e.g. respiratory/CAP triage, pediatric head-injury/concussion, electrolyte repletion, care-management routing, or observation-window retrieval).

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_016/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
Yes
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 → Structured JSON Response

These tasks give you (1) a prompt naming a target case and a decision to make,
(2) a runtime clinic environment plus a *separately listed access description* for
that run, and (3) an `answer_template.json` (usually under `input/payloads/`). Your
job is to read the record and the governing protocol, apply the protocol's rules to
the case data, and return **exactly one JSON object** that conforms to the template.

The template is authoritative for structure; the protocol is authoritative for
clinical logic; the case record is the ground truth. Nothing else is.

## Workflow

1. **Read all three inputs first.** Parse the prompt (what decision, which target