CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

diffdock-molecular-docking

Diffusion-based molecular docking to predict 3D ligand–protein binding poses (blind docking) with confidence scoring; use when you need pose prediction for drug discovery or virtual screening.

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 ./scientific-skills/Evidence Insight/diffdock-molecular-docking/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 content is highly actionable — executable commands with real arguments matching the bundled scripts, plus clearly named outputs — and the single-docking workflow is well sequenced with an environment check up front. Weaknesses are a triple-referenced nonexistent file (references/workflows_examples.md) breaking navigation for the batch/advanced use case, redundant capability restatements across three sections, and a no-information Dependencies list.

Suggestions

Fix the broken reference: either add references/workflows_examples.md or remove/redirect the three citations to it (When to Use, Key Features, Implementation Details), since the promised batch/advanced docking documentation currently leads nowhere.

Tighten the body: replace the Dependencies list where every entry says "(version not specified)" with a one-line pointer to scripts/setup_check.py for dependency verification, and merge the duplicated diffusion-sampling/confidence-ranking descriptions in "Key Features" and "Implementation Details" into one place.

Add post-inference validation and error-recovery guidance: instruct the user to confirm confidence_scores.txt lists the expected ranked poses, briefly say what to do when setup_check.py reports missing packages, and point to references/confidence_and_limitations.md for interpreting low-confidence results.

DimensionReasoningScore

Conciseness

The body is mostly efficient and teaches nothing Claude already knows, but it could be tightened: the Dependencies section repeats "(version not specified)" five times with no actionable content, and the diffusion-sampling/confidence-ranking capability is restated three times across "When to Use", "Key Features", and "Implementation Details" (e.g., "Diffusion generative sampling" vs "Uses a diffusion-based generative model to sample multiple candidate ligand poses" vs "Confidence model scoring" vs "A separate confidence model assigns a score to each sampled pose"). This matches the anchor-3 'mostly efficient but includes some unnecessary explanation or could be tightened' better than anchor 4's 'minor instances'.

3 / 5

Actionability

Fully executable, copy-paste-ready commands with real example values ("python scripts/setup_check.py"; "python scripts/inference_runner.py --protein ./data/protein.pdb --ligand 'CC(=O)Oc1ccccc1C(=O)O' --out_dir ./results"), documented arguments that match the actual wrapper script, and concrete named outputs (rank1.sdf..., confidence_scores.txt). The common single-docking case is covered end to end, matching anchor 5.

5 / 5

Workflow Clarity

Clear numbered sequence (1: verify environment via setup_check.py, 2: run inference, 3: inspect ranked SDF poses and confidence report) with an explicit environment-validation checkpoint up front, matching anchor 4. Not a 5: there is no post-inference verification (e.g., checking confidence_scores.txt was written or how to react to low-confidence poses) and no error-recovery guidance if the environment check fails.

4 / 5

Progressive Disclosure

Section structure is good and two referenced files (references/parameters_reference.md, references/confidence_and_limitations.md) exist and are one level deep, but "references/workflows_examples.md" is cited three times (When to Use, Key Features, Implementation Details) and does not exist in the bundle — the promised batch/advanced workflow documentation is a dead path. Scored against the actual bundle structure, navigation fails for one of the skill's advertised capabilities, which outweighs anchor 4's 'minor organization gaps'.

3 / 5

Total

15

/

20

Passed

Description

82%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: it clearly and concretely states what the skill does and gives an explicit, well-targeted use-when clause with natural domain trigger terms and a distinct niche. The only flaw is the second-person "you need" in the trigger clause, which per rubric guidelines costs one point on specificity; anchor-5 trigger coverage is also narrowly missed by the absence of file-extension/synonym terms.

DimensionReasoningScore

Specificity

"Diffusion-based molecular docking to predict 3D ligand–protein binding poses (blind docking) with confidence scoring" names the domain plus several concrete capabilities (docking, 3D pose prediction, blind docking, confidence scoring), which would anchor at 4. However, the trigger clause "use when you need pose prediction" is second person ("you need"), and the rubric explicitly penalizes second-person voice by reducing the specificity score by 1, bringing it to 3.

3 / 5

Completeness

Both parts are explicitly answered: the "what" is concrete ("Diffusion-based molecular docking to predict 3D ligand–protein binding poses (blind docking) with confidence scoring") and the "when" is an explicit trigger clause with concrete phrases ("use when you need pose prediction for drug discovery or virtual screening"), matching the anchor-5 pattern of clear what + explicit when with concrete triggers.

5 / 5

Trigger Term Quality

Strong natural domain keywords: "molecular docking", "blind docking", "pose prediction", "drug discovery", "virtual screening", "binding poses" — exactly the phrases a computational-chemistry user would say. Not a 5 because common variations and file formats are missing (e.g., "protein structure", "binding site", ".pdb", ".sdf", "SMILES", "protein–ligand docking").

4 / 5

Distinctiveness Conflict Risk

Clear niche (diffusion-based blind docking with confidence scoring) with distinct, domain-specific triggers; it would not plausibly fire for unrelated skills, and "diffusion-based" distinguishes it from classical docking tools. Overlap risk with other docking/screening skills is minimal.

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

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/diffdock-molecular-docking/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.