Individual skill

clinic-decision-support

Structured clinical decision-support for a synthetic clinic FHIR-like REST API. Use when the task prompt references a synthetic clinic case ID, a task environment base URL, and an answer_template.json payload — typically for protocol-bound assessments involving respiratory, head-injury, potassium replacement, care-management routing, or observation-window retrieval tasks.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_016/fewshot/codex/fewshot_attempt_03/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 Decision Support

## Workflow

Every task follows a single general workflow:

1. **Parse the prompt** for the target `case_id` and `task_id`.
2. **Read `input/payloads/answer_template.json`** to understand the exact output
   schema, required keys, enum values, and safety-check fields.
3. **Read `environment_access.md`** for the `<TASK_ENV_BASE_URL>` and allowed
   endpoint list. Use the base URL and endpoint names verbatim.
4. **Fetch the case**: `GET /api/cases/{case_id}` and extract the linked
   `patient_id` (may be a direct field or nested under `subject.reference`).
5. **Fetch the patient**: `GET /api/patients/{patient_id}`.
Back to top