CtrlK
BlogDocsLog inGet started
Tessl Logo

admet-reasoning

Interpretable ADMET analysis with mechanistic reasoning. Maps liabilities to structural causes and biological pathways. Based on CoTox (Park 2025) and DrugR (Liu 2026).

64

Quality

77%

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/chemistry/admet-reasoning/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The content is concise, highly actionable, and well-structured with a real referenced bundle script, but its workflows omit validation/verification steps for batch and report-generation operations.

Suggestions

Add a validation/verification step to the batch workflow, e.g., checking the output CSV/report for expected columns or empty results before declaring success.

Include a brief feedback loop for report generation (e.g., 'Verify report.json contains liabilities, causes, and fixes for each input molecule').

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no basic-concept tutorials, no library explanations — and every section (overview, when-to-use, workflows, script table) earns its place.

3 / 3

Actionability

Provides fully executable commands with real SMILES examples, explicit flags, output paths, and a complete install command — copy-paste ready with concrete outputs documented.

3 / 3

Workflow Clarity

Three named workflows are clearly sequenced with explicit commands, but batch/report operations lack validation or verification checkpoints, capping workflow clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

A clean overview organized into well-defined sections with a single one-level-deep bundle reference (scripts/reason_admet.py) that exists and is clearly signaled — appropriate structure for a skill of this size.

3 / 3

Total

11

/

12

Passed

Description

67%

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 and well-scoped, clearly stating what the skill does and distinguishing it from adjacent skills, but it lacks an explicit 'Use when...' trigger clause and richer natural-language trigger terms.

Suggestions

Add an explicit trigger clause, e.g., 'Use when interpreting ADMET/toxicity predictions, planning lead optimization, or generating toxicity reports for medicinal chemistry teams.'

Broaden trigger terms to include natural variations users would say, such as 'ADMET properties', 'toxicity report', 'drug safety', or 'liability interpretation'.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Maps liabilities to structural causes and biological pathways' — going beyond naming the domain to specify what is done.

3 / 3

Completeness

Clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so the 'when' is only implied — capping completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

Contains relevant domain keywords like 'ADMET analysis' and 'liabilities' but is missing common natural-language variations a user might say (e.g., 'ADMET properties', 'toxicity report', 'drug safety').

2 / 3

Distinctiveness Conflict Risk

The interpretive-reasoning framing carves a clear niche distinct from sibling prediction/optimization skills, with triggers unlikely to fire for the wrong skill.

3 / 3

Total

10

/

12

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.

Validation14 / 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
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.