Individual skill
clinic-protocol-json
Create strict JSON responses for synthetic clinic runtime decision-support tasks. Use when a prompt asks Codex to review a clinic case via runtime endpoints and return a protocol-bound answer template for adult respiratory/CAP assessment, pediatric head injury triage, potassium replacement, care-management routing, or observation-window lab retrieval.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_016/fewshot/fewshot_attempt_02/SKILL.md
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.
- 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
Read excerpt
# Clinic Protocol JSON
## Workflow
1. Read the user prompt and the provided `input/payloads/answer_template.json` first. Treat the template as the output contract for required keys, constants, enum values, nullability, precision, and ordering.
2. Read the runtime access file supplied with the task to get the base URL and allowed endpoints. Use only that runtime for case data. Prefer read-only `GET` endpoints; use `POST /api/query` only as a read-only retrieval helper when needed.
3. Fetch the target bundle with `GET /api/cases/{case_id}`. The bundle may contain `case`, `patient`, `findings`, `observations`, `imaging`, `medications`, `allergies`, `problems`, `care_registry`, and `sdoh`.
4. Fetch the relevant protocol from `GET /api/protocols` and `GET /api/protocols/{protocol_id}`. Map case types to protocol families:
- `acute_respiratory`: adult respiratory infection/CAP protocol.
- `pediatric_head_injury`: pediatric head injury clinic triage protocol.
- `potassium_repletion`: potassium replacement and escalation protocol.
- `care_management`: high-risk care-management routing protocol.
- `observation_window`: observation-window interpretation protocol.
5. Derive every output field from the current case bundle, protocol, and answer template. Do not reuse identifiers, selected findings, or numeric answer values from prior examples.