Menu

Individual skill

clinic-protocol-json

0upvotes

Use when solving synthetic-clinic protocol tasks that provide environment_access.md, a clinic runtime base URL, and input/payloads/answer_template.json, and require one schema-conformant JSON object for clinical decision support, observation-window retrieval, medication or lab recommendations, respiratory or head-injury assessment, potassium replacement, or care-management routing.

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

Use the prompt, `input/payloads/answer_template.json`, and `environment_access.md` as the task contract. Return exactly one JSON object and no markdown or narrative.

1. Read the prompt and template before fetching data. Extract the target case id, task id, required top-level keys, allowed enum values, nullability, ordering rules, precision rules, and safety-check fields.
2. Read `environment_access.md` for the base URL and allowed endpoints. Fetch only allowed read endpoints. Do not mutate the runtime, place orders, or invent unavailable endpoints.
3. Build a case bundle from runtime facts: case, patient, encounter context, observations, medications, allergies, problems, imaging, care registry, social context, and protocol materials. Match records by case id, patient id, encounter id, protocol id, date windows, observation code, and final/preliminary status as applicable.
4. Apply the clinic protocol text first. Use general clinical knowledge only to interpret protocol terms when the runtime protocol is silent, and keep the answer inside the template's controlled values.
5. Fill every required key and nested required key. Use `null` only where the template permits it. Do not add extra top-level keys.
6. Validate the JSON mechanically before finalizing.

Helpful commands:
Back to top