Individual skill

clinic-decision-support

Query a synthetic clinic REST API to retrieve clinical data and produce protocol-bound decision-support results as structured JSON. Use this skill whenever the task references a clinic runtime environment (TASK_ENV_BASE_URL), asks you to review patient records or clinical protocols, requires a JSON output conforming to a provided answer template, or mentions clinical decision support, medical protocol assessment, care management routing, potassium replacement, respiratory assessment, head injury triage, lab result interpretation, or FHIR-style API queries — even if the user does not name these terms explicitly.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_016/fewshot/opencode/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: 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.

agent Repository topic
ai Repository topic
benchmark Repository topic
llm Repository topic
self-evolving Repository topic
self-learning Repository topic
skills Repository topic
data Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 7,913 bytes

Read excerpt


# Clinic Decision Support

This skill covers how to work with a synthetic clinic REST API to retrieve clinical data and produce structured decision-support JSON outputs that conform to a provided answer template.

## Core workflow

When a task asks you to produce a clinical decision-support result, follow these steps in order.

### 1. Gather the inputs before calling the API

Read three things first:

- **The prompt** — it identifies the target case ID, the clinical domain, and what decision to produce. It also tells you where the answer template lives (usually `input/payloads/answer_template.json`) and references a runtime environment URL via `<TASK_ENV_BASE_URL>`.
- **The answer template** — a JSON schema that defines every required top-level key, allowed enum values per field, data types, numeric precision, ordering rules, and nullability. Read it completely. Every field in your final output must comply with this schema.