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.

Install with Tessl CLI

npx tessl i github:K-Dense-AI/claude-scientific-skills --skill clinpgx-database

What are skills?

Overall
score

69%

Review — 67%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 13 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

83%

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 professionals. It clearly articulates specific capabilities and uses appropriate technical terminology. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill.

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'. Uses proper third person voice.	3 / 3
Completeness	Clearly answers 'what' (access ClinPGx data, query interactions/guidelines/alleles) and implies 'when' through domain context, but lacks an explicit 'Use when...' clause with trigger guidance. The rubric caps completeness at 2 for missing explicit trigger guidance.	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'. These are the exact terms professionals in this field would search for.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche in pharmacogenomics with specific database name (ClinPGx), predecessor reference (PharmGKB), and specialized terminology (CPIC guidelines, allele functions). Very unlikely to conflict with other 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 accessing the ClinPGx API, which is its primary strength. However, it suffers from severe verbosity - explaining pharmacogenomics concepts, phenotype categories, and evidence levels that Claude already knows. The document would benefit significantly from aggressive trimming and better content organization across multiple files.

Suggestions

Remove explanatory content Claude already knows: phenotype category definitions, what evidence levels mean, what pharmacogenomics is, and the extensive 'When to Use This Skill' section

Move detailed workflow examples (Workflows 1-5) to a separate WORKFLOWS.md file, keeping only one representative example in the main skill

Integrate validation and error handling directly into workflow steps rather than as a separate section - e.g., 'Query gene-drug pair → Validate response status → Handle 429 with backoff'

Consolidate the 'Common Use Cases' section with the workflows or remove it entirely as it's redundant with the workflow examples

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive explanations Claude already knows (what pharmacogenomics is, what phenotype categories mean, what evidence levels are). The 'When to Use This Skill' section is redundant, and there's excessive repetition of concepts throughout. Could be reduced by 60-70%.	1 / 3
Actionability	Provides fully executable Python code examples throughout with specific API endpoints, parameters, and response handling. Code is copy-paste ready with proper imports and realistic usage patterns.	3 / 3
Workflow Clarity	Multiple workflows are clearly sequenced with numbered steps, but validation checkpoints are minimal. No explicit error recovery loops within workflows - error handling is separated into its own section rather than integrated into the clinical decision workflows where it matters most.	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 too much inline content. The API reference details, common use cases, and extensive workflow examples could be split into separate files.	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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (638 lines); consider splitting into references/ and linking	Warning
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	13 / 16 Passed

Reviewed: 8 minutes 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.