Menu

Individual skill

clinic-decision-support

0upvotes

Use for synthetic-clinic decision-support tasks that require querying a FHIR-like REST API at TASK_ENV_BASE_URL and producing a structured JSON response conforming to a supplied answer_template.json. Always use this skill when the prompt mentions a synthetic clinic case ID (CASE-*), a clinic runtime environment, protocol-bound clinical assessments, order-entry decision support, care-management routing, or lab-observation window retrieval tasks. This skill is essential whenever the task combines a clinic API with a JSON answer template containing enum-constrained fields.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_016/fewshot/cc/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
Yes
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 Skill

When a task asks you to query a clinic runtime API and return a structured JSON
decision-support response, follow the two-pass process described here. The
templates are dense and the enum constraints are tight; a systematic approach
avoids drift.

## Core Principle

**Read everything before you query anything.** The answer template, the
environment access listing, and the prompt together define every field you will
need. If you start calling the API before you understand what the template
requires, you will miss data or call the wrong endpoints and have to backtrack.
Back to top