clinpgx-database

Access ClinPGx pharmacogenomics data (successor to PharmGKB). Query gene-drug interactions, CPIC guidelines, allele functions, for precision medicine and genotype-guided dosing decisions.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/clinpgx-database/SKILL.md

Quality

Content

65%

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

A highly actionable, executable API skill body with real bundle references, but it is verbose and keeps a large API reference inline rather than delegating it to the bundled reference file, and workflows lack explicit validation checkpoints. Tightening the body and pushing detail to the reference would lift conciseness and progressive disclosure.

Suggestions

Move the per-endpoint parameter and response details into references/api_reference.md and keep SKILL.md as a concise overview with one example per capability plus a pointer to the reference.

Add explicit validation checkpoints inside each workflow (e.g., check response status_code and handle 429/empty results before proceeding to the next step) rather than relying on a separate helper.

Trim the Overview paragraph and consolidate the nine near-identical capability code blocks to reduce repetition.

Dimension	Reasoning	Score
Conciseness	Mostly efficient specialized API content Claude would not already know, but the lengthy Overview and heavily repeated endpoint-pattern blocks across nine sections could be tightened, fitting the "mostly efficient but could be tightened" anchor.	2 / 3
Actionability	Provides fully executable requests.get examples with real URLs and params plus ready-to-use helper functions and a bundled script, matching the copy-paste-ready anchor.	3 / 3
Workflow Clarity	Five clearly sequenced numbered workflows exist and a retry/backoff feedback loop is provided in helpers, but individual workflow steps lack explicit per-step validation checkpoints, fitting the "steps listed but validation gaps" anchor.	2 / 3
Progressive Disclosure	Two real bundle files are clearly signaled and one level deep, but the SKILL.md body itself is a large monolithic inline API reference duplicating content that should live in references/api_reference.md, matching the "content that should be separate is inline" anchor.	2 / 3
	Total	9 / 12 Passed

Description

82%

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, specific description with good natural trigger terms and a clear niche, but it lacks an explicit "Use when..." clause so the invocation trigger is only implied. Adding a trigger clause would raise completeness to full marks.

Suggestions

Append an explicit trigger clause, e.g. "Use when querying pharmacogenomic gene-drug interactions, CPIC guidelines, or allele functions for precision medicine dosing."

Keep the concrete action list but ensure the "when" guidance mirrors the natural phrasing users would say when they need this skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Query gene-drug interactions, CPIC guidelines, allele functions") rather than vague domain mention, matching the multiple-specific-actions anchor.	3 / 3
Completeness	Clearly states what the skill does but omits any "Use when..." trigger clause, so the "when" guidance is only implied, capping completeness per the missing-trigger guideline.	2 / 3
Trigger Term Quality	Uses natural domain terms a user would actually say ("pharmacogenomics," "gene-drug interactions," "CPIC guidelines," "allele functions," "genotype-guided dosing") with broad coverage.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear pharmacogenomics-database niche with distinct triggers (ClinPGx, CPIC, allele functions) unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (636 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/clinpgx-database/SKILL.md
Commit: f627ab5

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

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.