clinpgx-database

Access ClinPGx pharmacogenomics data (successor to PharmGKB) when you need to query gene-drug interactions, CPIC guidelines, allele functions, and drug-label PGx content for precision medicine and genotype-guided dosing.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/clinpgx-database/SKILL.md

Quality

Content

63%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.

The content is highly actionable with strong executable examples, but it suffers from heavy duplication of sections and generic boilerplate that inflate the token budget. Over-inlining of API patterns that already live in the reference file weakens progressive disclosure.

Suggestions

Remove the duplicated 'When to Use', 'Key Features', 'Dependencies', 'Example Usage', and 'Implementation Details' sections — keep only the detailed numbered versions and delete the generic stubs near the top.

Replace the inline endpoint/rate-limiting/evidence-levels material in section 5 with a one-line pointer to references/api_reference.md to avoid duplicating the reference file.

Trim the generic boilerplate blocks (Deterministic Output Rules, Failure Handling, Completion Checklist, Validation and Safety Rules) to skill-specific essentials only.

Dimension	Reasoning	Score
Conciseness	The body noticeably duplicates itself — 'When to Use', 'Key Features', 'Dependencies', 'Example Usage', and 'Implementation Details' each appear twice — plus generic boilerplate (Deterministic Output Rules, Failure Handling, Completion Checklist) that adds tokens without skill-specific value.	2 / 5
Actionability	Provides a fully executable, copy-paste-ready Python example plus concrete endpoint patterns and bash commands covering the common query cases.	5 / 5
Workflow Clarity	A clear numbered run plan and Recommended Workflow with a validation pass and completion checklist are present, though the API-query nature means validation checkpoints are lighter than for destructive operations.	4 / 5
Progressive Disclosure	Real bundle files (references/api_reference.md, scripts/query_clinpgx.py) are signaled, but the body inlines a full endpoint list and rate-limiting/evidence guidance that largely duplicates the api_reference.md file rather than deferring to it.	3 / 5
	Total	14 / 20 Passed

Description

92%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.

The description is specific, well-scoped, and clearly conveys both capability and trigger conditions in concise third-person voice. Minor room to add common synonyms/file extensions for broader trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('query gene-drug interactions, CPIC guidelines, allele functions, and drug-label PGx content') covering the core querying surface comprehensively.	5 / 5
Completeness	Explicitly answers both what ('Access ClinPGx pharmacogenomics data...') and when ('when you need to query...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong domain keywords (ClinPGx, PharmGKB, CPIC, gene-drug interactions, pharmacogenomics) but missing some natural synonyms users might say (e.g., 'pharmacogenetics', 'drug-gene', file extensions).	4 / 5
Distinctiveness Conflict Risk	Clear niche tied to ClinPGx as PharmGKB successor with CPIC/allele-specific triggers, minimal overlap risk with unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: aipoch/medical-research-skills
Path: scientific-skills/Evidence Insight/clinpgx-database/SKILL.md
Commit: 63c61d3

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