CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

opentargets-database

Query Open Targets Platform for target-disease associations, drug target discovery, tractability/safety data, genetics/omics evidence, known drugs, for therapeutic target identification.

64

Quality

80%

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 ./backend/cli/skills/databases/opentargets-database/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-structured skill body: concrete executable examples, a clear core workflow with common recipes, and proper progressive disclosure into real reference files. The main improvement opportunity is removing the triple-repeated caveats about score interpretation and under-studied diseases, and merging the Limitations section with the Best Practices content it duplicates.

Suggestions

State the "scores are relative rankings, not confidence" and "under-studied diseases score lower" caveats once (in Evidence Interpretation or Limitations) and delete the other two repetitions.

Merge the Limitations section into Best Practices — items 2–4 of Limitations restate Score interpretation and Evidence quality guidance almost verbatim.

Fold the schema-drift error-recovery guidance into the workflow steps (e.g. as a "If a query fails" checkpoint) so validation is explicit where it will be executed.

DimensionReasoningScore

Conciseness

The body is mostly dense, non-generic material (API calls, field names, scoring interpretation), but the same caveats are repeated near-verbatim three times — "NOT confidence scores but relative ranking metrics" (line 220), "Scores rank relative, not absolute confidence" (line 271), and "Scores are relative, not absolute" (line 372); the "under-studied diseases score lower" point and the "no authentication" point are likewise each repeated three times, and the Limitations section largely restates Best Practices. This is more than 'minor instances' of padding, so it sits at anchor 3 rather than 4.

3 / 5

Actionability

Every workflow step ships a copy-paste-ready Python call to the bundled script with real arguments (e.g. `get_target_disease_evidence(ensembl_id="ENSG00000157764", efo_id="EFO_0000249")`), the returned fields are enumerated, and the raw GraphQL endpoint is given for custom queries. This fully matches anchor 5: fully executable examples covering the common cases.

5 / 5

Workflow Clarity

The 7-step core workflow and the four numbered Common Workflows give a clear, well-sequenced process, and there is an error-recovery loop ("re-check the live schema when a query fails... inspect the current schema rather than returning an empty result"). It is not 5 because validation checkpoints are stated in a separate versioning section rather than embedded as explicit validate-and-retry steps inside the workflows.

4 / 5

Progressive Disclosure

The SKILL.md is a well-organized overview with clearly signaled, one-level-deep references — `references/api_reference.md`, `references/evidence_types.md`, and `references/target_annotations.md` all exist as real files, contain the bulk detail (79–401 lines), and do not nest further references; `scripts/query_opentargets.py` is likewise real and documented. Content is appropriately split and easy to navigate, matching anchor 5.

5 / 5

Total

17

/

20

Passed

Description

75%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, specific description that clearly conveys what the skill does across all its capability areas. Its main weakness is the complete absence of an explicit 'Use when...' trigger clause, which both caps completeness and leaves some natural trigger synonyms uncovered.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user mentions Open Targets, drug target identification/prioritization, target tractability or safety, or target-disease evidence."

Add natural trigger synonyms users would actually say, such as "target prioritization", "drug repurposing", and "gene targets".

Keep the capability list as-is — it is specific and non-generic; only the 'when' guidance is missing.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — "target-disease associations, drug target discovery, tractability/safety data, genetics/omics evidence, known drugs" — giving comprehensive, specific coverage of the skill's actions rather than vague language. This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage'; it is not score 4 because no capability area is noticeably missing.

5 / 5

Completeness

The 'what' is clearly and concretely answered, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not score 4 because the 'when' is entirely absent, not merely implicit.

3 / 5

Trigger Term Quality

Good keyword coverage including natural terms users would say: "Open Targets", "drug target discovery", "tractability", "known drugs", "therapeutic target identification". It falls short of anchor 5 because common variations users might say — e.g. "gene targets", "target prioritization", "drug repurposing" — are missing.

4 / 5

Distinctiveness Conflict Risk

"Query Open Targets Platform" names a specific, well-known resource, creating a clear niche with distinct triggers and minimal conflict risk with other skills. Periphery terms like "genetics/omics evidence" overlap slightly with general bioinformatics skills, but the platform anchor keeps it distinct.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

synthetic-sciences/openscience

Path

backend/cli/skills/databases/opentargets-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.