Menu

Individual skill

clinic-decision-support

Protocol-bound clinical decision support for a synthetic FHIR-like clinic REST API. Use when a prompt references a clinic case ID, a structured answer template with controlled enums, and a task environment base URL for fetching patient data, observations, protocols, and related clinical resources. Covers respiratory assessment, pediatric head injury, potassium replacement, care-management routing, observation-window retrieval, and similar protocol-driven structured-answer tasks.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/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
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
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

## Quick Start

Read the prompt to identify the target `case_id`, the `answer_template.json` path,
and the `<TASK_ENV_BASE_URL>`. Then follow this sequence:

1. Read `input/payloads/answer_template.json` first — it defines every field, its
   allowed values, and the output structure.
2. Fetch the case composite at `GET {BASE}/api/cases/{case_id}`. It returns
   `patient`, `case`, `observations`, `findings`, `imaging`, `medications`,
   `allergies`, `problems`, `care_registry`, and `sdoh` in one payload.
3. Identify which protocols are relevant. If the case response names a protocol
   or the task description implies one, fetch it from