CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

open-targets-db

Query the Open Targets Platform to retrieve targets, diseases, or evidence records when you need target-disease association data and evidence-based scores for therapeutic discovery.

Quality

69%

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/open-targets-db/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 core sections (When to Use, Example Usage, Implementation Details, Reference pointer) are well-constructed with executable commands and a real one-level-deep bundle, but the body is dragged down by generic template boilerplate and documentation that misrepresents the script's actual interface (evidence type and fields flag unsupported, search type missing). Trimming the filler and aligning the docs with the script would lift most dimensions.

Suggestions

Remove the generic template sections (When Not to Use, Required Inputs, Deterministic Output Rules, Output Contract, Validation and Safety Rules, Failure Handling, Completion Checklist, Scope Reminder) — they restate practices Claude already knows and roughly double the token cost without skill-specific value.

Align documented usage with the actual script: either implement `--type evidence` and `--fields` or drop them from the docs, and document the supported `search` query type that the script actually provides.

Replace the fabricated "Quick Validation" expected output (which `--help` does not produce) with the real help text, and rewrite Recommended Workflow as the concrete query steps (choose entity type → run script → parse JSON output) instead of template language.

DimensionReasoningScore

Conciseness

Roughly half the body is generic template filler — "Deterministic Output Rules", "Output Contract", "Validation and Safety Rules", "Completion Checklist", "Scope Reminder", "Required Inputs" — that restates practices Claude already knows ("Keep the output safe, reproducible, and within the documented scope"). Several padded sections with no skill-specific content put this noticeably below the midpoint; the core sections (When to Use, Example Usage, Implementation Details) are efficient, keeping it above a 1.

2 / 5

Actionability

The target-query bash commands are copy-paste ready and inputs/outputs are concretely specified, but key details are wrong or missing: the documented `--type evidence` is not supported by the script (choices are target/disease/search), the `--fields` option is unimplemented and hedged with "if supported by your script/API wrapper", and the script's actual `search` type is undocumented. This mismatch makes the guidance incomplete despite being executable in part.

3 / 5

Workflow Clarity

The "Recommended Workflow" is a generic four-step template ("Select the documented execution path", "Produce the expected output using the documented file format, schema, or narrative structure") not tied to the actual query process, and "Quick Validation" shows an expected output ("Result file: open_targets_db_result.md") that `--help` does not produce. A concrete sequence exists via the example commands, but checkpoints and the real workflow are implicit or fabricated.

3 / 5

Progressive Disclosure

The bundle structure is genuinely two-tier: SKILL.md serves as overview with a clearly signaled, one-level-deep reference ("See `references/api_reference.md` for API details, available fields, and entity schemas") and the referenced file exists with appropriate API detail. Minor gaps only: the single reference is fine, but the boilerplate sections clutter navigation and some API detail (unsupported fields list) leaks into the body.

4 / 5

Total

12

/

20

Passed

Description

78%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 description that names a specific platform, concrete actions, and an explicit use-when condition with minimal conflict risk. It could reach top marks by enumerating more trigger scenarios and natural synonyms (drug target, gene-disease association, Ensembl/EFO identifiers).

DimensionReasoningScore

Specificity

Lists several concrete actions — "retrieve targets, diseases, or evidence records" plus "target-disease association data and evidence-based scores" — anchored to a named platform. Not 5 because coverage has minor gaps (no mention of comparing associations across entities or field-level retrieval); not 3 because it goes beyond 1-2 actions.

4 / 5

Completeness

Clearly answers "what" (query the Open Targets Platform to retrieve targets, diseases, or evidence records) and includes an explicit "when" clause ("when you need target-disease association data and evidence-based scores for therapeutic discovery"). Not 5 because the "when" is a single condition rather than multiple concrete trigger phrases users would naturally say.

4 / 5

Trigger Term Quality

Includes strong natural domain terms: "Open Targets Platform", "target-disease association data", "evidence-based scores", "therapeutic discovery". A few natural variations are missing (e.g., "drug targets", "gene-disease", "Ensembl", "GWAS"), keeping it below the comprehensive-synonym level of 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Open Targets Platform queries for therapeutic target discovery) with distinct trigger terms; minimal risk of conflicting with other skills since the platform name and domain vocabulary are highly specific.

5 / 5

Total

17

/

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/open-targets-db/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.