Menu

Individual skill

self_attempt_03

Not available

experiments/claude_code_deepseek_v4_pro_max/reports/skills/task_group_015/self/self_attempt_03/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
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.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

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.

Declared tags are partial or unavailable.

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-Governance Skill

## When to use

Invoke this skill when the task involves preparing a normalized JSON packet from an EHR (Electronic Health Record) quality-governance API. The task prompt will reference `<TASK_ENV_BASE_URL>`, an `input/payloads/answer_template.json`, and one or more case objects (patient IDs, duplicate candidate IDs, referral IDs, provider IDs, batch IDs, or service request IDs).

## Pre-flight — read these files first

1. **`environment_access.md`** — Resolves `<TASK_ENV_BASE_URL>` to the actual `base_url`. Lists every `allowed_endpoints` the API exposes. Treat this as the authoritative endpoint catalog; do not call endpoints not listed here.

2. **`input/payloads/answer_template.json`** — The exact JSON shape to return. It defines required top-level keys, field types, enum allowed values, set semantics, and ordering rules. Every field you emit must conform to the constraints in this template.

3. **The task prompt** (`prompt.txt` or equivalent) — Identifies the task type and provides the specific case-object identifiers. Read it to understand which endpoints are relevant and what domain the task falls into.

4. **Any supplementary payloads** in `input/payloads/` beyond `answer_template.json` — Some tasks include additional request objects (e.g., `merge_packet_request.json`) that carry structured parameters. Read all payload files present; do not assume only the answer template exists.