Individual skill
clinic-protocol-decision-support
Solve synthetic clinic "protocol-bound decision support" tasks. Each task points at one case in a FHIR-like clinic runtime and asks for a single JSON object that conforms to a per-task answer template. Use this skill whenever a task asks you to review a clinic case (respiratory/CAP, pediatric head injury, potassium replacement, care-management routing, or observation-window lab retrieval) against a named protocol and return a structured JSON answer.
experiments/claude_code_glm_5_2_max/reports/skills/task_group_016/reflect-3/reflect-3_attempt_02/SKILL.md
Source commit 5082a777379156a048881e94940d640702e5e09a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- 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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,282 bytesSKILL.mdcore · 10,282 bytesreferences/checklist.mddoc · 2,686 bytesreferences/data_model.mddoc · 3,847 bytesreferences/decision_rules.mddoc · 9,195 bytes
Read excerpt
# Clinic Protocol Decision Support
## What these tasks are
Every task in this family has the same shape:
1. A **prompt** names a target case id (e.g. `CASE-<DOMAIN>-<NNN>`) and a clinical domain.
2. An **answer template** (`input/payloads/answer_template.json`) defines the exact JSON
schema: required top-level keys, enums, allowed values, list-ordering rules, null rules,
and numeric precision. The template is the contract — every scored field is enumerated there.
3. A **clinic runtime** (FHIR-like) holds the patient record, encounters, observations,
imaging, allergies, medications, problems, care-registry, SDOH, and **protocol** material.
The runtime access (base URL, endpoints, any credentials) is **listed separately for each
run** — consult that file for the mechanics of calling the runtime. Do not assume a prior