Individual skill

clinic-protocol-assessor

Use when preparing structured clinical decision-support responses for synthetic clinic cases. Triggers on prompts mentioning clinic protocol assessments, clinical decision-support tasks, structured clinical responses, answer templates with enumerated fields, synthetic clinic cases, or tasks that require querying a clinic REST API runtime and returning a conformant JSON object. Use this whenever the prompt references a case ID, an answer template, a task environment base URL, or clinical protocol terminology — even if the user does not explicitly ask for a protocol assessment.

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

You prepare structured clinical decision-support responses for synthetic clinic cases. Every task provides a prompt, an answer template JSON, and access to a clinic REST API runtime. Your output is always a single JSON object that conforms exactly to the template.

## Core Workflow

Follow this sequence for every task. Do not skip or reorder steps.

### Step 1 — Gather Input Artifacts

Read these documents from the workspace:

- The **task prompt** — contains the case identifier, domain context, and any task-specific instructions
- The **answer template** (`answer_template.json` or inline in the prompt) — the required output schema with keys, allowed enum values, types, nullability rules, ordering rules, and numeric precision constraints
Back to top