Menu

Individual skill

synthetic-clinic-protocol-json

0upvotes

Complete protocol-bound synthetic clinic decision-support tasks that require querying a local clinic runtime and returning an exact JSON object. Use for respiratory/CAP assessment, pediatric head-injury triage, potassium replacement support, care-management routing, and observation-window or lab-gate tasks when prompts provide environment_access.md plus an answer_template.json schema.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_016/self/self_attempt_03/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

# Synthetic Clinic Protocol JSON

## Core Workflow

1. Read the task prompt, `environment_access.md`, and the full `input/payloads/answer_template.json` before querying or answering.
2. Extract the target `case_id`, expected `task_id`, required top-level keys, allowed enum values, required nested keys, numeric precision, ordering rules, and nullability rules.
3. Use only the runtime base URL and endpoints listed in `environment_access.md`. Do not use external web sources. Do not mutate the runtime or place orders; treat any POST endpoint as read-only querying support only if the environment documents it as safe.
4. Retrieve `GET /api/cases/{case_id}` first. It usually bundles the case, patient, findings, observations, imaging, allergies, medications, problems, care registry, and SDOH records. Use list endpoints only to resolve missing context or compare distractors.
5. Retrieve the matching protocol with `GET /api/protocols/{protocol_id}`. Map case types as:
   - `acute_respiratory` -> `RESP-CAP-2026`
   - `pediatric_head_injury` -> `PEDS-HEAD-2026`
   - `potassium_repletion` -> `K-REPLETION-2026`
   - `care_management` -> `CM-HIGH-RISK-2026`
   - `observation_window` -> `OBS-WINDOW-2026`
Back to top