CtrlK
BlogDocsLog inGet started
Tessl Logo

tooluniverse-drug-target-validation

Quantitative drug-target validation pipeline. Scores druggability, selectivity, safety profile, ADMET feasibility, and structural tractability with a composite Target Validation Score (0-100) and GO/NO-GO recommendation. Use for go/no-go decisions on a target before commit-to-medchem, target prioritization across a list, and target-deselection rationale.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable and well-sequenced pipeline body with concrete tool calls, parameters, and a validation checkpoint, but it is verbose in places and references four bundle files that are not actually present. Creating the referenced reference files and trimming repeated emphasis would lift the two score-2 dimensions.

Suggestions

Create the referenced SCORING_CRITERIA.md, REPORT_TEMPLATE.md, TOOL_REFERENCE.md, and QUICK_START.md under a references/ directory so the signaled progressive-disclosure structure is real rather than dangling, and move the inline scoring tables and per-phase tool lists into them.

Tighten repeated emphasis blocks — e.g. consolidate 'RUN THE ML MODELS, DON'T SKIP THEM' rationale and the multiple 'IMPORTANT/REQUIRED' callouts — to reduce padding and raise conciseness toward the score-3 lean anchor.

Move the full ADMET-AI endpoint table and Python fallback into TOOL_REFERENCE.md, keeping only the requirement statement and a pointer in SKILL.md, to reduce inline bulk while preserving actionability.

DimensionReasoningScore

Conciseness

Mostly operational tool/parameter lists without over-explaining basic concepts, but ~280 lines are padded with repeated 'IMPORTANT'/'REQUIRED' emphasis and rationale paragraphs ('RUN THE ML MODELS, DON'T SKIP THEM…') that could be tightened; score 3 requires every token to earn its place, which this repeated emphasis does not meet.

2 / 3

Actionability

Provides executable, copy-paste-ready guidance — exact tool names with required parameters ('species="homo_sapiens" REQUIRED', 'target_chembl_id__exact' double underscore, 'operation="median"') and a complete Python ADMET-AI fallback script — matching the score-3 fully-executable anchor.

3 / 3

Workflow Clarity

Clear phased sequence (Phase 0–10) with explicit gates ('Do not proceed to Phase 3 before completing Phase 1'), a Completeness Checklist validation checkpoint, and feedback loops (gate-1 failure → NO-GO/pivot), matching the score-3 anchor with explicit validation and error-recovery paths.

3 / 3

Progressive Disclosure

References to SCORING_CRITERIA.md, REPORT_TEMPLATE.md, TOOL_REFERENCE.md, and QUICK_START.md are signaled one-level-deep, but none of these files exist in the bundle (no references/ dir); additionally substantial scoring tables and tool lists are inline rather than split into those files, fitting the score-2 'content that should be separate is inline' anchor rather than the score-3 well-split structure.

2 / 3

Total

10

/

12

Passed

Description

100%

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 tight, third-person description that states concrete capabilities and an explicit 'Use for' trigger set, covering both what and when with low conflict risk. No meaningful weakness against the description rubric.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Scores druggability, selectivity, safety profile, ADMET feasibility, and structural tractability with a composite Target Validation Score (0-100) and GO/NO-GO recommendation' — matching the score-3 anchor of several specific concrete actions rather than the partial score-2 anchor.

3 / 3

Completeness

Explicitly answers both what (the scoring pipeline) and when via a clear 'Use for go/no-go decisions on a target before commit-to-medchem, target prioritization across a list, and target-deselection rationale' clause, matching the score-3 anchor and exceeding the score-2 'when only implied' case.

3 / 3

Trigger Term Quality

Uses natural pharma terms a user would say — 'go/no-go decisions on a target', 'target prioritization across a list', 'target-deselection rationale' — giving good coverage; not merely jargon, so it clears the score-3 bar over the partial-coverage score-2.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear drug-target-validation niche with distinct triggers unlikely to fire for adjacent skills; the score-2 'could still overlap' anchor does not apply because the scope is narrowly scoped to pre-medchem target validation.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mims-harvard/ToolUniverse
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.