Menu

Individual skill

clinic-protocol-json

Solve synthetic clinic runtime tasks that ask for protocol-bound clinical decision-support or care-management results as a strict JSON object. Use this whenever a prompt provides a TASK_ENV_BASE_URL, environment_access.md, a target clinic case id, and an input/payloads/answer_template.json schema for respiratory, head-injury, potassium, lab-window, care-management, or similar structured clinic protocol assessments.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_016/fewshot/cc/fewshot_attempt_02/SKILL.md

Read pinned source

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
Local scripts
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 JSON

Use this skill to turn a target synthetic clinic case into the exact JSON object required by the task's answer template. The runtime API is the source of facts; the template is the output contract; the applicable protocol is the decision rulebook.

## Workflow

1. Read the user prompt and `input/payloads/answer_template.json` before deciding any field. Extract the target `case_id`, `task_id`, required keys, enum values, numeric precision, ordering rules, nullability, and any safety-check meanings.
2. Read `environment_access.md` for the base URL and allowed endpoints. Use only read-only calls unless the task explicitly permits otherwise; these tasks usually say not to mutate or place orders.
3. Collect target context from the runtime. If Python is available, run the bundled collector from the skill directory:

   ```bash
   python scripts/collect_clinic_context.py --env-file /path/to/environment_access.md --case-id TARGET_CASE_ID > /tmp/clinic_context.json
   ```