Conciseness

The ~35-line body is entirely operational — operating rules, input forms, output fields, and one executable command — with no explanation of what Genebass, Ensembl, or PheWAS is. Every line adds guidance Claude could not infer, matching the anchor for lean, efficient content where every token earns its place.

Actionability

The execution section gives a copy-paste ready command (`echo '{...}' | python scripts/genebass_gene_burden.py`), both input forms are shown with concrete examples, the output fields are enumerated, and the supported burden sets are listed with alias handling noted. This matches the anchor for fully executable, copy-paste ready guidance covering the common cases.

Workflow Clarity

This is a simple single-purpose skill (one gene, one read-only script call) and the single action is unambiguous: pipe JSON to the script and read its `ok`/`error` output, with success and failure shapes both documented. Per the rubric's simple-skill exception this scores at the top; no validation checkpoint is needed for a read-only fetch.

Progressive Disclosure

The body is under 50 lines, well-organized into clearly labeled sections, and needs no external references — the References section explicitly scopes the bundle to this file and the script. The one referenced bundle path (`scripts/genebass_gene_burden.py`) is a real file whose stdin/burden-set/error interface matches what the body documents, matching the under-50-lines guideline for a top score.

Specificity

"Submit compact Genebass gene burden requests for one Ensembl gene ID and one burden set" names the domain with specific parameters (Ensembl gene ID, burden set) but relies on a single action verb ("submit requests"). This matches the anchor for naming the domain with 1-2 concrete actions that are not comprehensive, rather than listing several specific actions (4).

Completeness

Both "what" ("Submit compact Genebass gene burden requests for one Ensembl gene ID and one burden set") and "when" ("Use when a user wants concise Genebass PheWAS summaries") are explicitly stated in third person. The single trigger clause could be more specific with additional concrete trigger phrases, so it does not reach the clearly-explicit multi-trigger example of the top anchor.

Trigger Term Quality

Natural domain terms users would say are present: "Genebass", "gene burden", "Ensembl gene ID", "PheWAS". A few natural variations are missing (e.g., "burden test", "LoF/pLoF", "phenotype associations"), so it falls short of the comprehensive synonym coverage of the top anchor.

Distinctiveness Conflict Risk

"Genebass gene burden" is a clear niche with distinct triggers (Genebass, PheWAS, Ensembl gene ID, burden set); no other common skill would fire on these terms. This matches the anchor for a clear niche with minimal conflict risk.