CtrlK
BlogDocsLog inGet started
Tessl Logo

diffdock

Predict small-molecule binding poses with DiffDock-L (Corso et al. 2023/2024, github.com/gcorso/DiffDock) — blind diffusion docking that places a ligand into a protein pocket without a predefined search box and ranks the samples with a learned confidence model. Reach for this skill to dock a SMILES or SDF against a PDB, to generate ranked 3D poses for a small fragment library, or to get a starting pose for downstream rescoring. DiffDock predicts geometry, not affinity.

76

Quality

95%

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

93%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 tight, expert-level reference: executable commands, exact CSV/output contracts, and a rare set of operational gotchas (silent precompute, YAML-overrides-CLI, prefix-matched flag) that Claude could not discover without burning runs. The only gap is a missing post-run verification step for batch runs, which leaves workflow clarity just short of the top anchor.

Suggestions

Add a short post-run verification step for batch runs, e.g. 'after a batch, check every complex_name has a rank1.sdf under --out_dir before comparing ligands — rows with a bad ligand_description fail silently.'

State how to obtain $DIFFDOCK_REPO (clone github.com/gcorso/DiffDock) and where default_inference_args.yaml lives, so the first command is runnable without inference.

DimensionReasoningScore

Conciseness

The ~70-line body is lean and every non-obvious fact earns its place — the YAML-overwrites-CLI gotcha ("replaces every key it finds, so passing --samples_per_complex 40... is silently ignored"), the silent ~11-minute SO(3) precompute with its 32 GB RAM requirement, and the --ligand prefix-matching trap. No concepts Claude already knows are re-explained. Matches the 'every token earns its place' anchor.

5 / 5

Actionability

The main invocation is copy-paste ready with real flags (python3 -m inference --config default_inference_args.yaml --protein_path target.pdb --ligand_description "COc1ccc(C#N)cc1"), the batch path specifies the exact four CSV columns, the output convention (rank{N}_confidence{score}.sdf) is documented, and the error table gives concrete fixes (sed the setrlimit constant to min(64000, rlimit[1])). Matches the fully-executable top anchor.

5 / 5

Workflow Clarity

The single-complex path is unambiguous and the "Errors worth recognizing" table provides explicit error-to-fix recovery loops, but there is no post-run verification checkpoint for the batch/fragment-library path (e.g., confirm each complex produced a rank1.sdf before comparing ligands). This sits between 'most checkpoints present' (4) and 'explicit validation steps with feedback loops' (5).

4 / 5

Progressive Disclosure

The body keeps the single-complex path inline and correctly splits batch docking and the ESMFold sequence-only path into references/workflows.md (a real file, one level deep, clearly signaled in context: "that path and a larger-library screening recipe are in references/workflows.md"). Structure is well organized with earned section headings; matches the top anchor.

5 / 5

Total

19

/

20

Passed

Description

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

An exemplary description: concrete capabilities, explicit use-when triggers with file formats, a clear scope boundary (geometry, not affinity), and a distinct niche anchored to a named tool. Third-person voice with no padding or over-claims.

DimensionReasoningScore

Specificity

The description lists multiple concrete, distinct actions — "Predict small-molecule binding poses", "places a ligand into a protein pocket without a predefined search box", "ranks the samples with a learned confidence model", "dock a SMILES or SDF against a PDB", "generate ranked 3D poses for a small fragment library", "get a starting pose for downstream rescoring" — covering the tool's use modes comprehensively, which matches the top anchor rather than the 'minor gaps' level below.

5 / 5

Completeness

It explicitly answers both what ("blind diffusion docking that places a ligand into a protein pocket... and ranks the samples with a learned confidence model") and when ("Reach for this skill to dock a SMILES or SDF against a PDB, to generate ranked 3D poses for a small fragment library, or to get a starting pose for downstream rescoring"), with concrete trigger phrases plus a scope boundary ("predicts geometry, not affinity").

5 / 5

Trigger Term Quality

Natural trigger terms a docking user would actually say are covered including formats and synonyms: "dock", "SMILES", "SDF", "PDB", "binding poses", "fragment library", "rescoring". This matches the comprehensive-coverage anchor; score 4 would require missing natural terms, and none are obviously absent for this niche.

5 / 5

Distinctiveness Conflict Risk

It names the specific tool (DiffDock-L, Corso et al., github.com/gcorso/DiffDock) and its distinct niche (blind docking without a predefined search box, SMILES/SDF against a PDB), giving minimal overlap risk with sibling modeling skills. Not 4: the niche and triggers are clearly distinct rather than having minor overlap.

5 / 5

Total

20

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
UnicomAI/wanwu
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.