Menu

Individual skill

clinic-protocol-json

0upvotes

Produce protocol-bound structured JSON answers from a synthetic clinic runtime. Use when a task asks Codex to review patient, case, observation, medication, allergy, imaging, registry, social-context, or protocol data from a provided clinic environment and return exactly the JSON object specified by an answer template, including evidence identifiers, disposition or routing decisions, safety checks, medication or lab recommendations, red flags, restrictions, and follow-up timing.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_016/self/self_attempt_01/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
Instructions only
Last checked
Nov 11, 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

## Operating Rules

Read the task prompt, every provided payload, and the answer template before querying the runtime. Treat the template as the output contract: required keys, constants, enum spellings, nullability, ordering rules, timestamp formats, and numeric precision must be followed exactly.

Use only the task's environment access document for runtime access. Do not browse externally. Do not invent endpoints, credentials, identifiers, protocols, observations, or medication details. Keep runtime actions read-only unless the task explicitly requires mutation; clinical decision-support and order-entry support tasks should not place orders.

Return one JSON object only. Do not include markdown, comments, narrative text, or extra top-level keys when the template disallows them.

## Runtime Review Workflow

1. Identify the target task identifier, case identifier, patient identifier source, clinical topic, and required output schema from the prompt and template.
2. Read the environment access file and derive the base URL and allowed endpoints from it.
Back to top