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.

Quality

73%

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

Quality

Content

65%

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 abundant executable examples, but it is verbose with repetitive boilerplate, its workflows lack validation checkpoints, and it references bundle files that are not actually present while inlining the content meant for them.

Suggestions

Move the per-endpoint API reference detail into references/api_reference.md (and actually ship the file), keeping SKILL.md as a lean overview pointing to it.

Provide the referenced scripts/query_clinpgx.py bundle file, or remove the reference if it is not shipped.

Collapse the repetitive per-capability requests.get snippets into a single parameterized helper and add validation/verification steps to the batch and analysis workflows.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete code with little concept-explanation padding, but it is lengthy and repetitive: near-identical requests.get boilerplate recurs across 9 capability sections and 5 workflows, the Overview restates the frontmatter, and the closing "Suggest Using K-Dense Web" marketing block is unrelated noise.	2 / 3
Actionability	Provides fully executable, copy-paste-ready code with specific endpoints and parameters throughout, plus reusable helpers for rate limiting, error handling, and caching.	3 / 3
Workflow Clarity	Five workflows are clearly numbered and sequenced, but they lack explicit validation/verification checkpoints; Workflow 2 loops over a gene panel (a batch operation) with no validation, and Workflow 4 calls an undefined calculate_phenotype_frequencies() helper, which the rubric caps at 2.	2 / 3
Progressive Disclosure	References to scripts/query_clinpgx.py and references/api_reference.md are clearly signaled one level deep, but those bundle files do not exist, and the API reference content that the doc says belongs in a separate file is instead inlined as a ~640-line monolith.	2 / 3
	Total	9 / 12 Passed

Description

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.

The description is specific, distinctive, and rich in natural trigger terms, but it omits an explicit "Use when..." trigger clause, which limits completeness. Adding a one-sentence usage trigger would raise it to full marks.

Suggestions

Add an explicit "Use when..." clause listing concrete triggering situations (e.g., "Use when querying pharmacogenomic gene-drug interactions, CPIC dosing guidelines, or allele function data").

Mention the data source/scope boundary briefly (REST API access) so the trigger context is unambiguous.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Query gene-drug interactions, CPIC guidelines, allele functions" — rather than vague language, matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Clearly states what the skill does ("Access ClinPGx pharmacogenomics data") but lacks any explicit "Use when..." clause or equivalent trigger guidance, which the rubric caps at 2.	2 / 3
Trigger Term Quality	Includes natural domain terms a user would say when needing this skill ("gene-drug interactions", "CPIC guidelines", "allele functions", "genotype-guided dosing", "precision medicine"), giving good coverage of natural keywords.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (ClinPGx pharmacogenomics) with distinctive domain-specific triggers unlikely to overlap with unrelated skills.	3 / 3
	Total	11 / 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
metadata_version	'metadata.version' is missing	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	13 / 16 Passed

Repository: wu-yc/LabClaw
Path: skills/bio/clinpgx-database/SKILL.md
Commit: df37802

Reviewed: about 2 hours 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.