Menu

Individual skill

clinic-protocol-json

0upvotes

Produce schema-constrained JSON answers for synthetic clinic runtime tasks that require reviewing case records, observations, medications, allergies, imaging, care-registry, SDOH, and protocol materials from allowed clinic API endpoints. Use for protocol-bound clinical decision-support, observation-window retrieval, lab replacement, respiratory, head-injury, and care-management routing tasks that provide an answer_template.json and TASK_ENV_BASE_URL-style access.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_016/fewshot/codex/fewshot_attempt_01/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

# Clinic Protocol JSON

## Core Workflow

1. Read the user prompt and `input/payloads/answer_template.json` completely before calling the runtime. Treat the template as the output contract: required keys, enum values, nullability, precision, sorting, constants, and "no extra keys" rules override prose habits.
2. Extract the `task_id`, target `case_id`, runtime base URL, and any explicit window, target code, protocol scope, or endpoint limits from the prompt and environment access file.
3. Retrieve the target case first:

```bash
python scripts/collect_clinic_context.py --base-url "$TASK_ENV_BASE_URL" --case-id "$CASE_ID" --out /tmp/clinic_context.json
```

Use the generated context as source material, not as an answer. If the case bundle already contains patient, findings, observations, medications, allergies, problems, imaging, registry, or SDOH sections, prefer those over broad collection scans. Use collection endpoints only to fill missing pieces or verify distractors.
Back to top