clinpgx

Query the ClinPGx API for pharmacogenomic gene-drug data, clinical annotations, CPIC guidelines, and FDA drug labels

Quality

61%

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 ./skills/clinpgx/SKILL.md

Quality

Content

53%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 body is concise and well-structured, but it lacks executable API examples and validation checkpoints for its batch API operations, limiting actionability and workflow clarity.

Suggestions

Add concrete, copy-pasteable API call examples (e.g., a `requests.get` snippet against api.clinpgx.org showing endpoint, params, and response handling).

Insert validation checkpoints into the workflow (e.g., verify HTTP status, retry on 429, confirm CSV fields before writing) so batch operations have explicit feedback loops.

Specify the actual API endpoints/paths used for gene lookup, drug lookup, and clinical annotations so the guidance is directly executable.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence without over-explaining concepts, with only minor spots that could be tightened.	4 / 5
Actionability	The workflow is described in prose ('Hit the ClinPGx REST API with rate limiting', 'Generate report') with no executable code, API call examples, or concrete commands, leaving the specific steps to execute largely missing.	2 / 5
Workflow Clarity	A numbered sequence is present, but batch API operations (rate-limited queries, CSV generation) lack explicit validation checkpoints, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections in a single appropriately-sized file with no bundle files needed; minor organization gaps only.	4 / 5
	Total	13 / 20 Passed

Description

70%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 and well-targeted to a distinct niche, but it omits an explicit 'when to use' trigger clause, which caps completeness. Adding a 'Use when...' clause would raise the score.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when the user asks about pharmacogenomic gene-drug interactions, CPIC guidelines, or FDA drug labels').

Include a few natural synonyms a user might say ('PGx', 'drug-gene interactions', 'PharmGKB') to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete actions ('Query the ClinPGx API for pharmacogenomic gene-drug data, clinical annotations, CPIC guidelines, and FDA drug labels'), with only minor coverage gaps.	4 / 5
Completeness	It clearly answers 'what' the skill does but has no 'Use when...' or equivalent trigger guidance, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	It includes strong natural domain keywords (ClinPGx, pharmacogenomic, gene-drug, CPIC, FDA drug labels), though it omits common synonyms or extensions a user might say.	4 / 5
Distinctiveness Conflict Risk	The ClinPGx pharmacogenomics niche has distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: ClawBio/ClawBio
Path: skills/clinpgx/SKILL.md
Commit: 00f070d

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