Individual skill

ehr-quality-json

Use this skill for EHR quality-governance tasks that require normalized JSON from a read-only healthcare API, including duplicate-chart merge packets, referral coordination, referral batch audits, care-transition packets, ServiceRequest validation, active clinical-list reconciliation, ICD-10 checks, provider lookups, and answers constrained by input/payloads/answer_template.json. Use whenever the prompt mentions an EHR/referral environment, <TASK_ENV_BASE_URL>, duplicate candidates, patient active lists, referral batches, ServiceRequests, or normalized packet JSON.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_015/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
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

# EHR Quality JSON

Use this skill to turn EHR API evidence into the exact normalized JSON object requested by the task. The evaluator rewards evidence-backed field values, stable IDs, sorted sets, and strict adherence to the provided template.

## Required Workflow

1. Read the prompt and every file under `input/payloads/` before querying the API.
   - Treat `answer_template.json` as the output contract.
   - Preserve the required top-level keys, field names, enum spellings, booleans, nulls, and ordering rules from the template.
   - Do not emit prose, markdown, comments, or procedural notes outside the final JSON object.

2. Resolve the API base URL.
   - Use the prompt value, `TASK_ENV_BASE_URL`, or the staged environment access note.
   - Query only documented endpoints. Prefer direct ID endpoints when the prompt gives an ID.