clinpgx

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

Quality

64%

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

57%

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

The content is well-organized into a clear single-purpose overview, but the workflow lacks executable detail and validation/verification checkpoints for batch API operations, holding actionability and workflow clarity at 2.

Suggestions

Add at least one concrete executable example — a real ClinPgx API endpoint path with a `requests.get(...)` snippet — so guidance is copy-paste ready.

Insert validation/verification checkpoints into the workflow (e.g., handle HTTP errors and rate-limit responses, verify non-empty API responses before assembling data) to support batch queries.

Trim the role preamble and the Example Queries section, whose trigger phrasing duplicates the Integration section, to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with no concept-teaching filler, but the role preamble ("You are ClinPgx, a specialised ClawBio agent...") and the Example Queries section duplicate trigger terms already covered by the Integration section, so it could be tightened rather than earning the 'every token earns its place' anchor.	2 / 3
Actionability	It gives concrete-ish parameters (2 req/sec rate limit, 24h caching, exact output filenames) but no executable code, no real API endpoint paths, and no request examples, leaving key implementation details missing despite the base URL being stated.	2 / 3
Workflow Clarity	A clear 5-step sequence is present (parse, query, assemble, generate, attribute), but there are no validation/verification checkpoints and no error-recovery loop for batch queries or API failures, which caps workflow clarity at 2 per the batch-operation guidance.	2 / 3
Progressive Disclosure	There are no bundle files and the body is organized into clear, single-purpose sections with no nested references or monolithic wall of text, meeting the simple-skill allowance for a well-organized single-purpose skill.	3 / 3
	Total	9 / 12 Passed

Description

72%

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 to a distinct pharmacogenomics niche with strong natural trigger terms, but it omits explicit "when to use" guidance, capping completeness at 2.

Suggestions

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

Broaden specificity beyond data outputs by naming concrete actions the skill performs (e.g., 'look up genes, search drugs, fetch CPIC guidelines and FDA labels').

Dimension	Reasoning	Score
Specificity	Quotes "Query the ClinPgx API for pharmacogenomic gene-drug data, clinical annotations, CPIC guidelines, and FDA drug labels" — it names a concrete action and the data domain, but lists data outputs rather than multiple distinct actions, matching the 'names domain and some actions' anchor rather than the 'lists multiple specific concrete actions' anchor.	2 / 3
Completeness	It clearly answers what the skill does but has no "Use when..." clause or explicit trigger guidance, so per the judging guidelines completeness is capped at 2 (what present, when missing).	2 / 3
Trigger Term Quality	Natural domain terms a user would say are well covered — "ClinPgx", "CPIC guidelines", "FDA drug labels", "clinical annotations", "gene-drug" — matching the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	The pharmacogenomics niche (ClinPgx, CPIC, FDA drug labels) is highly specific with distinct triggers, unlikely to conflict with other skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 12 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: f6c7851

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