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.

1.70x

Quality

66%

Does it follow best practices?

Impact

99%

1.70x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./scientific-skills/clinpgx-database/SKILL.md

Quality

Discovery

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.

This is a strong, domain-specific description with excellent trigger term coverage for pharmacogenomics users. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The technical specificity is appropriate for the specialized audience.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about drug-gene interactions, pharmacogenomic testing, medication dosing based on genetics, or references PharmGKB/ClinPGx data.'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Query gene-drug interactions, CPIC guidelines, allele functions' and specifies use cases 'precision medicine and genotype-guided dosing decisions'.	3 / 3
Completeness	Clearly describes WHAT it does (access ClinPGx data, query interactions/guidelines/alleles) but lacks an explicit 'Use when...' clause. The when is only implied through the domain context.	2 / 3
Trigger Term Quality	Excellent coverage of domain-specific terms users would naturally use: 'ClinPGx', 'pharmacogenomics', 'PharmGKB', 'gene-drug interactions', 'CPIC guidelines', 'allele functions', 'precision medicine', 'genotype-guided dosing'.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche in pharmacogenomics with specific database name (ClinPGx), domain terminology (CPIC, allele functions), and clear medical/pharmaceutical focus that wouldn't overlap with general data or document skills.	3 / 3
	Total	11 / 12 Passed

Implementation

50%

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

This skill provides highly actionable, executable code examples for querying the ClinPGx API, which is its primary strength. However, it suffers from significant verbosity, explaining concepts Claude already understands (pharmacogenomics basics, what evidence levels mean, what CYP enzymes are) and including redundant sections like 'When to Use This Skill'. The document would benefit from aggressive trimming and better content distribution across reference files.

Suggestions

Remove the 'When to Use This Skill' section entirely and trim the Overview to 2-3 sentences - Claude understands pharmacogenomics concepts

Move detailed workflow examples to a separate WORKFLOWS.md file, keeping only one quick-start example in the main skill

Consolidate the extensive API endpoint documentation into the referenced api_reference.md rather than duplicating inline

Add validation steps within workflows (e.g., 'Verify response.status_code == 200 before proceeding') to improve error recovery

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive explanations Claude already knows (what pharmacogenomics is, what CYP450 enzymes do, what evidence levels mean). The 'When to Use This Skill' section is redundant, and many sections contain unnecessary context padding that could be condensed significantly.	1 / 3
Actionability	Provides fully executable Python code examples throughout, with specific API endpoints, parameters, and copy-paste ready implementations. Code examples are complete and demonstrate real use cases with proper imports and response handling.	3 / 3
Workflow Clarity	Multiple workflows are clearly sequenced with numbered steps, but validation checkpoints are largely missing. For example, workflows don't verify API responses succeeded before proceeding, and there's no error recovery guidance within the workflow steps themselves (error handling is separate).	2 / 3
Progressive Disclosure	References external files (scripts/query_clinpgx.py, references/api_reference.md) appropriately, but the main document is a monolithic wall of text with extensive inline content that could be split into separate reference files. The API endpoint details and all workflow examples could be in separate documents.	2 / 3
	Total	8 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

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

	Total	9 / 11 Passed

Repository: K-Dense-AI/claude-scientific-skills
Commit: 71add64

Reviewed: 7 days 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.