Menu

Individual skill

clinic-decision-support

0upvotes

Protocol-bound clinical decision-support task. Use when solving a task that asks for a structured JSON response based on synthetic-clinic runtime data accessed via REST endpoints, including case/patient reviews, protocol assessments, lab-based decisions, care-management routing, or observation-window retrieval. Trigger whenever the prompt mentions a clinic runtime environment, an answer template, a case identifier, or structured clinical decision support with enumerated output fields.

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

Use this skill for any task that involves querying a synthetic clinic REST runtime to produce a protocol-bound structured JSON clinical decision-support response.

## Workflow

Follow this sequence for every task. The steps are ordered to keep data fetches parallel where possible and to fill the output template correctly on the first pass.

### 1. Read the answer template first

The prompt always references an input payload template (`input/payloads/answer_template.json` or similar). Read it before you read anything else from the runtime. The template defines:

- Every required top-level key
- Allowed enumeration values for each controlled field
Back to top