CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 has a genuinely useful core — a complete runnable API example, concrete endpoint patterns, and domain-specific cautions (rate limits, evidence levels, phenoconversion) — but it is buried in duplicated boilerplate section pairs and ~10 generic template sections that carry no domain information. Structural fixes (deduplication, naming the reference file, removing fabricated output claims) would raise most dimensions substantially.

Suggestions

Delete the first set of template sections (lines 13-52: 'When to Use', 'Key Features', 'Dependencies', 'Example Usage', 'Implementation Details') and the generic filler sections ('Deterministic Output Rules', 'Output Contract', 'Failure Handling', 'Completion Checklist', 'Scope Reminder'); keep only the numbered, domain-specific sections 1-5 to roughly halve the token cost.

Replace the vague 'Reference material available in `references/`' with explicit links like 'Full endpoint documentation: See [references/api_reference.md](references/api_reference.md)' so the 756-line reference is clearly signaled and the inline endpoint list can shrink to the few most common patterns.

Rewrite 'Recommended Workflow' with concrete, executable checkpoints (e.g., verify the script runs with `python scripts/query_clinpgx.py --help`, then query a known pair like CYP2C19/clopidogrel and confirm JSON returns before running the user's actual query), and remove the '--help' expected-output block that does not reflect the script's real behavior.

DimensionReasoningScore

Conciseness

The body is noticeably verbose with pervasive template padding: it contains two of each section ('When to Use' vs '1. When to Use', 'Key Features' vs '2. Key Features', 'Dependencies' vs '3. Dependencies', 'Example Usage' vs '4. Example Usage', 'Implementation Details' vs '5. Implementation Details'), where the first of each pair is contentless boilerplate ('Use this skill when the request matches its documented task boundary', 'Structured execution path designed to keep outputs consistent and reviewable'). Roughly ten further generic sections ('Deterministic Output Rules', 'Output Contract', 'Failure Handling', 'Completion Checklist', 'Scope Reminder') add no ClinPGx-specific information, and the dependencies statements contradict each other ('not explicitly version-pinned in this skill package' vs the pinned 'requests >=2.31.0'). It is not a 1 because a substantial core (the runnable Python example, endpoint patterns, rate limiting) genuinely earns its tokens.

2 / 5

Actionability

The Python example is complete and copy-paste runnable with rate limiting and 429 backoff, and the endpoint patterns are concrete with example paths ('GET /gene/{symbol} (e.g., /gene/CYP2D6)', 'GET /variant/{rsid} (e.g., /variant/rs4244285)'). Minor gaps keep it at 4: the run plan tells the user to 'Edit the in-file CONFIG block' without establishing the script has one, the hardcoded 'cd "20260316/scientific-skills/..."' path is questionable, and the 'Quick Validation' section claims a '--help' invocation produces a result-file summary format it almost certainly does not.

4 / 5

Workflow Clarity

Sequences exist ('Example run plan', 'Recommended Workflow': validate request, select execution path, produce output, run final validation) but they are generic and duplicated, with no concrete checkpoint commands — 'run a final validation pass for completeness, consistency, and safety' names no actual check. The only concrete verification is 'python scripts/query_clinpgx.py --help'. It reaches 3 rather than 2 because a real, ordered sequence for API querying is present and the operations are read-only, so no destructive-operation cap applies; it cannot reach 4 because checkpoints are implicit rather than executable steps.

3 / 5

Progressive Disclosure

The bundle does contain references/api_reference.md (756 lines) and scripts/query_clinpgx.py, but the body never names or links the reference file — it only offers vague pointers ('Reference material available in `references/`', '`references/` contains supporting rules, prompts, or checklists') — while inlining a condensed API reference (endpoint list, rate limiting, evidence levels) that overlaps the dedicated reference file. This matches the anchor of references present but not clearly signaled with content that could live in the separate file inline; it is above 2 because real structure and one-level-deep bundle layout exist, but below 4 because the reference is not explicitly signaled or navigable from the body.

3 / 5

Total

12

/

20

Passed

Description

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

A strong, tightly-written description: it names the domain and successor relationship, enumerates four concrete query capabilities, and provides an explicit 'when you need to' trigger with purpose context ('precision medicine and genotype-guided dosing'). The only shortcoming is mild under-coverage of a few supported capabilities and natural synonyms.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'query gene-drug interactions, CPIC guidelines, allele functions, and drug-label PGx content' — anchored in a named data source ('ClinPGx pharmacogenomics data (successor to PharmGKB)'). It sits at 4 rather than 5 because coverage has minor gaps: the packaged skill also supports clinical annotations, pathways, and chemical/drug lookup, none of which are mentioned. The verb phrase is third-person/imperative ('Access...'); 'when you need to' is a trigger clause matching the accepted 'Use when...' pattern, not a second-person capability claim like 'You can use this', so no voice penalty applies.

4 / 5

Completeness

Both halves are explicit: the 'what' is 'Access ClinPGx pharmacogenomics data... query gene-drug interactions, CPIC guidelines, allele functions, and drug-label PGx content', and the 'when' is the concrete trigger clause 'when you need to query... for precision medicine and genotype-guided dosing'. This mirrors the anchor-5 example structure (what + 'Use when...' with concrete trigger phrases), so it is not the 4 where the 'when' is only loosely specified.

5 / 5

Trigger Term Quality

Natural trigger phrases are well covered: 'pharmacogenomics', 'gene-drug interactions', 'CPIC guidelines', 'PGx', 'drug-label', 'genotype-guided dosing', plus the PharmGKB name for legacy users. It falls short of 5 because a few natural variations users would say are missing (e.g., 'medication safety', 'adverse drug reaction', 'star allele', 'genotype'), though none of these alone would misroute the trigger.

4 / 5

Distinctiveness Conflict Risk

The description stakes out a clear niche with named, non-generic triggers (ClinPGx, PharmGKB, CPIC, PGx, genotype-guided dosing) that no general-purpose or adjacent skill would claim. Conflict risk with other skills is minimal; a user mentioning any of these terms would be routed here and nowhere else.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.