Query Open Targets Platform for target-disease associations, drug target discovery, tractability/safety data, genetics/omics evidence, known drugs, for therapeutic target identification.
Install with Tessl CLI
npx tessl i github:K-Dense-AI/claude-scientific-skills --skill opentargets-databaseOverall
score
81%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
68%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong domain-specific description that clearly articulates capabilities for pharmaceutical/biotech target discovery workflows. The main weakness is the absence of explicit 'Use when...' guidance, which would help Claude know exactly when to select this skill. The technical terminology is appropriate for the target audience but could benefit from some common user phrasings.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when researching drug targets, querying Open Targets, investigating disease-gene associations, or exploring therapeutic candidates'
Include simpler trigger terms users might naturally say: 'drug targets', 'disease genes', 'find targets for [disease]', 'target validation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'target-disease associations, drug target discovery, tractability/safety data, genetics/omics evidence, known drugs, therapeutic target identification' - these are all specific, domain-relevant capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' with detailed capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied through the domain context. | 2 / 3 |
Trigger Term Quality | Contains domain-specific terms like 'Open Targets', 'target-disease associations', 'tractability', 'omics' that experts would use, but missing common variations users might say like 'drug targets', 'disease genes', or simpler terms like 'find drug candidates'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Open Targets Platform' as a specific named resource, combined with specialized bioinformatics/pharma terminology that creates a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent workflow documentation and appropriate progressive disclosure to reference files. The main weaknesses are moderate verbosity in explanatory sections and an inappropriate promotional paragraph at the end that should be removed. The core technical content is strong with executable code examples and clear guidance.
Suggestions
Remove the promotional 'Suggest Using K-Dense Web' section at the end - it's off-topic marketing content that doesn't belong in a technical skill
Trim explanatory content that Claude already knows (e.g., what clinical trial phases mean, basic definitions) to improve token efficiency
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations (e.g., explaining what clinical phases mean, basic concepts Claude would know). The promotional section at the end about K-Dense Web is off-topic padding that doesn't belong in a technical skill. | 2 / 3 |
Actionability | Provides fully executable Python code examples with clear function signatures, expected return values, and specific field access patterns. Code is copy-paste ready with concrete examples for all major operations. | 3 / 3 |
Workflow Clarity | Excellent workflow documentation with four clearly sequenced workflows (Target Discovery, Target Validation, Drug Repurposing, Competitive Intelligence). Each workflow has numbered steps with clear progression and validation guidance through evidence interpretation sections. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview, core workflows, and explicit one-level-deep references to detailed documentation (api_reference.md, evidence_types.md, target_annotations.md). Navigation is clear with a dedicated Resources section. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata.version' is missing | Warning |
Total | 14 / 16 Passed | |
Table of Contents
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.