CtrlK
BlogDocsLog inGet started
Tessl Logo

pharmgkb-skill

Submit compact PharmGKB API requests for genes, variants, clinical annotations, dosing guidelines, and search. Use when a user wants concise PharmGKB summaries

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary lean skill body: it documents only what Claude cannot infer (the script's interface, endpoint paths, request patterns) and provides three fully executable JSON examples plus a runnable shell one-liner. Structure is tight, the single bundle reference is real, and failure and staleness behavior are covered without any padding.

DimensionReasoningScore

Conciseness

The 38-line body contains only operational facts Claude would not know (base_url, max_items heuristics, stdin field list, truncation caveat) with zero explanation of known concepts. Lean throughout; anchor 5 fits and 4 would require over-explanation to trim, which is absent.

5 / 5

Actionability

The 'echo ... | python scripts/rest_request.py' command plus three complete copy-paste-ready JSON payloads (gene, clinicalAnnotation with params, variant) are fully executable and cover the common lookup cases. Anchor 5 fits; 4 would imply gaps or non-runnable examples that are not present.

5 / 5

Workflow Clarity

This is a simple, single-purpose skill (build request JSON, run script, summarize output) and that single action is unambiguous, with failure behavior documented ('Failure returns ok=false with error.code and error.message') and staleness guidance ('Re-run requests in long conversations'). The simple-skill exception applies and no destructive or batch operations exist, so no validation cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines, organized into clear sections, references exactly one bundle file (scripts/rest_request.py, which exists on disk), and explicitly states the package should stay limited to SKILL.md plus that script. Per the simple-skill exception, well-organized sections with no external references warrant anchor 5.

5 / 5

Total

20

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that names concrete actions across the full PharmGKB entity set and includes an explicit 'Use when' clause. Its only weaknesses are a thin trigger surface — no pharmacogenomics/PGx synonyms or genotype-related phrasing — and a when-clause that covers one trigger scenario rather than several concrete ones.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions in third person — 'Submit compact PharmGKB API requests for genes, variants, clinical annotations, dosing guidelines, and search' — covering the domain comprehensively with no vague filler. Anchor 5 fits; 4 would require coverage gaps that are not present.

5 / 5

Completeness

Both 'what' (submit compact API requests for the listed entity types) and 'when' ('Use when a user wants concise PharmGKB summaries') are explicitly stated. The when-clause is single-scoped and could name more concrete triggers, matching anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Natural terms like 'genes', 'variants', 'clinical annotations', 'dosing guidelines', and 'PharmGKB summaries' are present and would be said by users, but common synonyms such as 'pharmacogenomics', 'PGx', or 'drug-gene' variants are missing. Anchor 4 fits; 5 requires the synonym coverage that is absent.

4 / 5

Distinctiveness Conflict Risk

'PharmGKB' is a highly specific niche with named entity types, so triggers are distinct and conflict risk with other skills is minimal. Anchor 5 fits; 4 would require overlap with closely related skills that does not exist here.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.