Individual skill
synthetic-clinic-protocol-json
Solve synthetic clinic protocol decision-support tasks that provide a prompt, answer_template.json, environment_access.md, and a read-only clinic runtime API. Use for protocol-bound JSON answers involving cases, patients, observations, imaging, allergies, medications, problems, care-management registry/SDOH data, and clinic protocol materials, including respiratory, head injury, potassium replacement, care-management routing, and lab-window gate tasks.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_016/fewshot/naive/fewshot_attempt_03/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
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Synthetic Clinic Protocol JSON
Produce exactly one JSON object that conforms to the task's `input/payloads/answer_template.json`. Derive every case-specific value from the current prompt, template, runtime records, and protocol materials. Do not use memorized constants from examples.
## Workflow
1. Read the task prompt and `input/payloads/answer_template.json`.
- Extract the target case id, task id, required keys, allowed enum values, required nested keys, nullability, numeric precision, and ordering rules.
- Treat constants in the current template or prompt as authoritative for the current task only.
2. Read the runtime access file supplied with the task.
- Use only the listed base URL, credentials, and allowed read-only endpoints.
- Do not call any judge endpoint. Do not create, update, delete, or place orders.
3. Retrieve the target case and all linked clinical context.
- Start with `/health`, then `/api/cases/{case_id}` when available.