CtrlK
BlogDocsLog inGet started
Tessl Logo

tooluniverse-admet-prediction

Comprehensive ADMET (Absorption, Distribution, Metabolism, Excretion, Toxicity) profiling for drug candidates. Integrates ADMET-AI predictions, SwissADME drug-likeness, PubChemTox experimental toxicity, ChEMBL clinical data, Lipinski rule-of-five, and CYP interaction data. Use for drug-likeness assessment, BBB penetration, bioavailability, hepatotoxicity prediction, ADME/PK profiling, or screening compound libraries before lab testing.

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

Passed

No findings from the security scan

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.

The body is highly actionable with a well-sequenced, validated workflow and genuinely non-obvious operational detail, but it is a long monolithic file with some inline explanation and reference-style tables that could be split out. Splitting the ideal-range and toxicity-endpoint tables into a reference file and trimming the 'why it matters' prose would lift the two 2-scored dimensions.

Suggestions

Move the ideal-range table (Phase 2) and the 7-endpoint toxicity reference list (Phase 4) into a references/ file, keeping SKILL.md as an overview with one-level-deep links, to improve progressive_disclosure.

Trim the inline 'Why X matters' annotations (e.g. the CYP paragraph) to the non-obvious operational facts, tightening conciseness without losing tool-specific guidance.

Consider a short 'Quick start / single-compound run' summary near the top so the 5-phase detail can be treated as the advanced path.

DimensionReasoningScore

Conciseness

Most content earns its place (exact tool signatures, SOAP/list quirks, fallback paths, console-noise caveats Claude would not know), but inline 'Why X matters' mini-essays and the 8-row ideal-range table explain ADMET significance that could be tightened. Not 3 because some explanatory prose could be trimmed; not 1 because it avoids basic-concept padding.

2 / 3

Actionability

Provides copy-paste-ready tool calls with exact signatures (e.g. 'ADMETAI_predict_BBB_penetrance(smiles=["<SMILES>"])'), list-wrapping reminders, expected output fields, and concrete fallbacks. Not 2 because the guidance is fully executable rather than pseudocode.

3 / 3

Workflow Clarity

A 5-phase sequenced workflow with an ASCII flow diagram, per-phase goals/steps, fallbacks, and a MANDATORY completeness checklist acting as an explicit validation checkpoint before reporting. Not 2 because validation and failure-handling steps are explicit, not merely implied.

3 / 3

Progressive Disclosure

Single monolithic ~310-line file with no bundle directories or external references, and large inline reference-style tables (8-row ideal-range table, 7 toxicity endpoints) that arguably belong in a separate reference file. Not 3 because the simple-skill carve-out does not apply to this long, multi-task skill; not 1 because sections are clearly organized rather than a wall of nested references.

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.

The description is specific, uses third person, and explicitly answers both what the skill does and when to use it with strong natural trigger terms. It occupies a clear niche with low conflict risk.

DimensionReasoningScore

Specificity

Names concrete actions and integrations ('Integrates ADMET-AI predictions, SwissADME drug-likeness, PubChemTox experimental toxicity, ChEMBL clinical data, Lipinski rule-of-five, and CYP interaction data'), matching the multi-specific-action anchor; not the level below, which only names a domain and some actions.

3 / 3

Completeness

Explicitly states what ('Comprehensive ADMET ... profiling for drug candidates') and when ('Use for ... before lab testing'), satisfying both halves; not 2 because the 'Use for' trigger clause is present and explicit.

3 / 3

Trigger Term Quality

The 'Use for ... BBB penetration, bioavailability, hepatotoxicity prediction, ADME/PK profiling, or screening compound libraries' clause covers natural terms users would say; not 2 because common variations are well represented rather than partial.

3 / 3

Distinctiveness Conflict Risk

Clear ADMET/drug-likeness niche with distinct triggers unlikely to fire for unrelated skills; not 2 because the domain and triggers are specific enough to avoid overlap with general cheminformatics skills.

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.