Menu

Individual skill

clinic-protocol

0upvotes

Structured clinical protocol decision support for synthetic clinic FHIR-like REST APIs. Use when the task directs you to a clinic runtime with TASK_ENV_BASE_URL and a case ID to produce protocol-bound structured JSON answers for respiratory assessment (RESP-CAP-2026), pediatric head injury (PEDS-HEAD-2026), potassium replacement (K-REPLETION-2026), care management routing (CM-HIGH-RISK-2026), or observation-window retrieval (OBS-WINDOW-2026). Also use for any task that requires reading a clinic case endpoint, applying a protocol from /api/protocols, and returning an answer conforming to a JSON template with controlled enum values.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_016/fewshot/deepagents/fewshot_attempt_02/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 Protocol

## Overview

This skill covers structured protocol-driven clinical decision support against a synthetic clinic REST API. The solver reads a target case, retrieves protocol rules, applies those rules to clinical observations and patient context, and returns a single JSON object with controlled values.

## Core Workflow

Every task follows the same five-step pattern:

### Step 1: Read the answer template

The prompt directs you to `input/payloads/answer_template.json`. Read it first. The template defines every required top-level key, allowed enum values, field types, numeric precision rules, and output constraints. The template is the authoritative shape for your answer — never add extra keys or use prose where an enum is required.
Back to top