Individual skill

synthetic-clinic-protocol-json

Use this skill whenever a task asks for a protocol-bound JSON clinical decision-support answer from a synthetic clinic runtime, a target case id, environment_access.md, and input/payloads/answer_template.json. It helps retrieve the case/protocol evidence, apply clinic-specific rules instead of outside medical knowledge, preserve source identifiers, avoid unsupported clinical claims, and return schema-only JSON.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_016/fewshot/opencode/fewshot_attempt_02/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

Use this skill for synthetic clinic tasks where the answer must be one JSON object that conforms to a provided `answer_template.json`. The key risk is not general medical reasoning; it is missing a clinic-specific protocol detail, using a preliminary or wrong-patient record, or drifting from the exact schema.

## Required Inputs

Read these before deciding:

- The user prompt, especially the target case id and the requested clinical domain.
- `environment_access.md` for the base URL and allowed endpoints.
- `input/payloads/answer_template.json` for required keys, enum values, nullability, ordering, constants, and numeric precision.
- The runtime case record and the applicable protocol material.

Do not use memorized example outcomes. Solve from the current runtime data and the current template.