TO

tooluniverse-binder-discovery

A systematic workflow for protein target druggability assessment and small-molecule binder identification.

Install

mkdir -p .claude/skills/tooluniverse-binder-discovery && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3540" && unzip -o skill.zip -d .claude/skills/tooluniverse-binder-discovery && rm skill.zip

Installs to .claude/skills/tooluniverse-binder-discovery

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Discover novel small-molecule binders for protein targets using structure-based and ligand-based screening. Covers druggability assessment, known-ligand mining (ChEMBL, BindingDB), similarity expansion, ADMET filtering, and synthesis feasibility. Use for hit identification, virtual screening, target-to-compounds workflows, and lead-finding before commit-to-medchem.
367 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Advanced

Key capabilities

  • Perform structure-based protein binding site analysis
  • Mine compound libraries from ChEMBL or BindingDB
  • Apply ADMET filtering to prioritize binders
  • Assess chemical synthesis feasibility
  • Generate prioritized ligand reports

How it works

Uses a series of targeted tool queries across binding pocket definition, ligand screening, and druggability assessments.

Inputs & outputs

You give it
Protein target structure
You get back
Prioritized small molecule candidate report

When to use tooluniverse-binder-discovery

  • Screening compounds for a specific protein target
  • Filtering candidates by ADMET profiles
  • Assessing druggability of a novel target
  • Mining ligand data from chemical databases

About this skill

Small Molecule Binder Discovery Strategy

Systematic discovery of novel small molecule binders using 60+ ToolUniverse tools across druggability assessment, known ligand mining, similarity expansion, ADMET filtering, and synthesis feasibility.

LOOK UP DON'T GUESS - Always retrieve actual data from tools before drawing conclusions. Do not assume druggability, binding sites, or compound properties based on target class alone.

KEY PRINCIPLES:

  1. Report-first approach - Create report file FIRST, then populate progressively
  2. Target validation FIRST - Confirm druggability before compound searching
  3. Multi-strategy approach - Combine structure-based and ligand-based methods
  4. ADMET-aware filtering - Eliminate poor compounds early
  5. Evidence grading - Grade candidates by supporting evidence
  6. Actionable output - Provide prioritized candidates with rationale
  7. English-first queries - Always use English terms in tool calls. Respond in the user's language

Binding Site Reasoning (Start Here)

Before any tool call, reason about the target's structural biology:

Is the binding site a well-defined pocket (small molecule accessible) or a flat protein-protein interface (needs peptide/macrocycle)? This determines your screening strategy.

  • Enzymes with active sites (proteases, kinases, ATPases): deep, well-defined pockets. Classic small molecule territory. Prioritize co-crystal structure search and known inhibitor scaffold analysis.
  • GPCRs and ion channels: transmembrane pockets. Structure often available; start with GPCRdb and GtoPdb for known pharmacology.
  • Nuclear receptors: deep hydrophobic pockets. Excellent small molecule tractability; ligand-based methods are well-powered.
  • Protein-protein interfaces: flat, large contact surface. Small molecules rarely compete effectively unless there is a "hot spot" cavity. Check whether any allosteric pockets exist before committing to small molecule strategy. Warn the user if no pocket is found.
  • Intrinsically disordered regions: essentially no small molecule approach. Redirect to peptide or degrader strategies.
  • Scaffolding / adaptor proteins: assess co-crystal structures for unexpected pockets before declaring undruggable.

Use this reasoning to select phases and warn the user about challenges before executing a full workflow.


Critical Workflow Requirements

1. Report-First Approach (MANDATORY)

DO NOT show search process or tool outputs to the user. Instead:

  1. Create the report file FIRST - Before any data collection:

    • File name: [TARGET]_binder_discovery_report.md
    • Initialize with all section headers from the template (see REPORT_TEMPLATE.md)
    • Add placeholder text: [Researching...] in each section
  2. Progressively update the report - As you gather data, update each section immediately.

  3. Output separate data files:

    • [TARGET]_candidate_compounds.csv - Prioritized compounds with SMILES, scores
    • [TARGET]_bibliography.json - Literature references (optional)

2. Citation Requirements (MANDATORY)

Every piece of information MUST include its source:

Example: *Source: ChEMBL via ChEMBL_get_target_activities (CHEMBL203)*


Workflow Overview

Phases in order:

  • Phase 0: Tool verification (check parameter names with get_tool_info)
  • Phase 1: Target validation — resolve IDs, assess druggability, identify binding sites, predict structure if needed
  • Phase 2: Known ligand mining — ChEMBL, BindingDB, GtoPdb, PubChem BioAssay, chemical probes; SAR analysis
  • Phase 3: Structure analysis — PDB co-crystals, EMDB (membrane targets), binding pocket characterization
  • Phase 3.5: Docking validation — dock reference inhibitor to validate pocket geometry
  • Phase 4: Compound expansion — similarity/substructure search (seeds: 3-5 diverse actives) + de novo generation
  • Phase 5: ADMET filtering — physicochemical, bioavailability, toxicity, CYP, structural alerts
  • Phase 6: Candidate docking and prioritization — score and rank top 20
  • Phase 6.5: Literature evidence — PubMed, EuropePMC, OpenAlex
  • Phase 7: Report synthesis and delivery

Phase 0: Tool Verification

CRITICAL: Verify tool parameters before calling unfamiliar tools.

tool_info = tu.tools.get_tool_info(tool_name="ChEMBL_get_target_activities")

Common parameter corrections (verify with get_tool_info if uncertain):

  • OpenTargets_*: ensemblId (camelCase); ADMETAI_*: smiles must be a list
  • NvidiaNIM_alphafold2 (requires NVIDIA_API_KEY env var; free key at build.nvidia.com): sequence not seq; NvidiaNIM_genmol (requires NVIDIA_API_KEY env var; free key at build.nvidia.com): SMILES must contain [*{min-max}]
  • NvidiaNIM_boltz2 (requires NVIDIA_API_KEY env var; free key at build.nvidia.com): polymers=[{"molecule_type": "protein", "sequence": "..."}]

Phase 1: Target Validation

1.1 Identifier Resolution

Resolve all IDs upfront and store for downstream queries:

1. UniProt_search(query=target_name, organism="human") -> UniProt accession
2. MyGene_query_genes(q=gene_symbol, species="human") -> Ensembl gene ID
3. ChEMBL_search_targets(query=target_name, organism="Homo sapiens") -> ChEMBL target ID
4. GtoPdb_search_targets(query=target_name) -> GtoPdb ID (if GPCR/channel/enzyme)

1.2 Druggability Assessment

Use multi-source triangulation:

  • OpenTargets_get_target_tractability_by_ensemblID(ensemblId) - tractability bucket
  • DGIdb_get_gene_druggability(genes=[gene_symbol]) - druggability categories
  • OpenTargets_get_target_classes_by_ensemblID(ensemblId) - target class
  • For GPCRs: GPCRdb_get_protein + GPCRdb_get_ligands + GPCRdb_get_structures
  • For antibody landscape: TheraSAbDab_search_by_target(target=target_name)

Decision Point: If no tractability data and binding site reasoning suggests PPI or disordered region, explicitly warn the user before proceeding.

1.3 Binding Site Analysis

  • ChEMBL_search_binding_sites(target_chembl_id)
  • get_binding_affinity_by_pdb_id(pdb_id) for co-crystallized ligands
  • InterPro_get_protein_domains(accession) for domain architecture

1.4 Structure Prediction (NVIDIA NIM)

Requires NVIDIA_API_KEY. Two options:

  • AlphaFold2: NvidiaNIM_alphafold2(sequence, algorithm="mmseqs2") - high accuracy, 5-15 min
  • ESMFold: ESMFold_predict_structure(sequence) - fast (~30s), max 1024 AA

pLDDT guidance: >=90 very high confidence, 70-90 confident, <70 use with caution. Low pLDDT in the putative binding region undermines docking reliability.


Phase 2: Known Ligand Mining

Priority order for bioactivity data:

  1. ChEMBL_get_target_activities - curated, SAR-ready
  2. BindingDB_get_ligands_by_uniprot - direct Ki/Kd with literature links
  3. GtoPdb_search_ligands - pharmacology focus (GPCRs, channels)
  4. PubChem_search_assays_by_target_gene - HTS screens, novel scaffolds
  5. OpenTargets_get_chemical_probes_by_target_ensemblID - validated probes

Key steps:

  1. Filter to IC50/Ki/Kd < 10 uM; retrieve molecule details for top actives
  2. Identify chemical probes and approved drugs
  3. Analyze SAR: common scaffolds, key modifications
  4. Check off-target selectivity: BindingDB_get_targets_by_compound

Phase 3: Structure Analysis

Tools:

  • PDB_search_similar_structures(query=uniprot, type="sequence") - find PDB entries
  • get_protein_metadata_by_pdb_id(pdb_id) - resolution, method
  • get_binding_affinity_by_pdb_id(pdb_id) - co-crystal ligand affinities
  • get_ligand_smiles_by_chem_comp_id(chem_comp_id) - ligand SMILES from PDB
  • EMDB_search_structures(query) - cryo-EM structures (prefer for GPCRs, ion channels)
  • alphafold_get_prediction(qualifier) - AlphaFold DB fallback

Phase 3.5: Docking Validation (NVIDIA NIM)

If PDB + SDF available: use get_diffdock_info(protein=PDB, ligand=SDF, num_poses=10). If only sequence + SMILES: use NvidiaNIM_boltz2(polymers=[...], ligands=[...]).

Dock a known reference inhibitor first to validate the binding pocket geometry before running candidates.


Phase 4: Compound Expansion

4.1-4.3 Search-Based Expansion

Use 3-5 diverse actives as seeds, similarity threshold 70-85%:

  • ChEMBL_search_similar_molecules(molecule=SMILES, similarity=70)
  • PubChem_search_compounds_by_similarity(smiles, threshold=0.7)
  • ChEMBL_search_substructure(smiles=core_scaffold)
  • STITCH_get_chemical_protein_interactions(identifier=gene, species=9606)

4.4 De Novo Generation (NVIDIA NIM)

GenMol - scaffold hopping with masked regions:

NvidiaNIM_genmol(smiles="...core...[*{3-8}]...tail...[*{1-3}]...", num_molecules=100, temperature=2.0, scoring="QED")

MolMIM - controlled analog generation:

NvidiaNIM_molmim(smi=reference_smiles, num_molecules=50, algorithm="CMA-ES")

Phase 5: ADMET Filtering

Apply sequentially (all tools accept smiles=[list]):

  1. Physicochemical: ADMETAI_predict_physicochemical_properties - Lipinski violations <= 1, QED > 0.3, MW 200-600
  2. Bioavailability: ADMETAI_predict_bioavailability - oral bioavailability > 0.3
  3. Toxicity: ADMETAI_predict_toxicity - AMES < 0.5, hERG < 0.5, DILI < 0.5
  4. CYP: ADMETAI_predict_CYP_interactions - flag CYP3A4 inhibitors
  5. Alerts: ChEMBL_search_compound_structural_alerts - no PAINS

Include a filter funnel summary in the report showing pass/fail counts at each stage.


Phase 6: Candidate Docking & Prioritization

Composite score: docking confidence (40%) + ADMET score (30%) + similarity to known active (20%) + novelty (10%, not in ChEMBL + novel scaffold bonus).

Evidence tiers for candidates:

  • T1 (3 stars): Experimental IC50/Ki < 100 nM
  • T2 (2 stars): Docking within 5% of reference OR IC50 100-1000 nM
  • T3 (1 star): >80% similarity to T1 compound
  • T4 (0 stars): 70-80% similarity, scaffold match only
  • T5 (no stars): Generated mo

Content truncated.

When not to use it

  • When working with non-protein targets
  • For non-small molecule drug discovery projects

Prerequisites

Access to chemical databasesToolUniverse API credentials

Limitations

  • Highly dependent on available structural data
  • Computationally intensive for large ligand screens

How it compares

It forces a systematic, evidence-based approach to drug discovery rather than relying on generative speculation.

Compared to similar skills

tooluniverse-binder-discovery side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
tooluniverse-binder-discovery (this skill)12moCautionAdvanced
torchdrug37moReviewAdvanced
string-database27moReviewIntermediate
transformer-lens-interpretability27moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

More by mims-harvard

View all by mims-harvard

tooluniverse-drug-research

mims-harvard

Generates comprehensive drug research reports with compound disambiguation, evidence grading, and mandatory completeness sections. Covers identity, chemistry, pharmacology, targets, clinical trials, safety, pharmacogenomics, and ADMET properties. Use when users ask about drugs, medications, therapeutics, or need drug profiling, safety assessment, or clinical development research.

323

tooluniverse-pharmacovigilance

mims-harvard

Analyze drug safety signals from FDA adverse event reports, label warnings, and pharmacogenomic data. Calculates disproportionality measures (PRR, ROR), identifies serious adverse events, assesses pharmacogenomic risk variants. Use when asked about drug safety, adverse events, post-market surveillance, or risk-benefit assessment.

323

tooluniverse-precision-oncology

mims-harvard

Provide actionable treatment recommendations for cancer patients based on molecular profile. Interprets tumor mutations, identifies FDA-approved therapies, finds resistance mechanisms, matches clinical trials. Use when oncologist asks about treatment options for specific mutations (EGFR, KRAS, BRAF, etc.), therapy resistance, or clinical trial eligibility.

321

tooluniverse-expression-data-retrieval

mims-harvard

Retrieves gene expression and omics datasets from ArrayExpress and BioStudies with gene disambiguation, experiment quality assessment, and structured reports. Creates comprehensive dataset profiles with metadata, sample information, and download links. Use when users need expression data, omics datasets, or mention ArrayExpress (E-MTAB, E-GEOD) or BioStudies (S-BSST) accessions.

217

tooluniverse-literature-deep-research

mims-harvard

Conduct comprehensive literature research with target disambiguation, evidence grading, and structured theme extraction. Creates a detailed report with mandatory completeness checklist, biological model synthesis, and testable hypotheses. For biological targets, resolves official IDs (Ensembl/UniProt), synonyms, naming collisions, and gathers expression/pathway context before literature search. Default deliverable is a report file; for single factoid questions, uses a fast verification mode and may include an inline answer. Use when users need thorough literature reviews, target profiles, or to verify specific claims from the literature.

213

tooluniverse-target-research

mims-harvard

Gather comprehensive biological target intelligence from 9 parallel research paths covering protein info, structure, interactions, pathways, expression, variants, drug interactions, and literature. Features collision-aware searches, evidence grading (T1-T4), explicit Open Targets coverage, and mandatory completeness auditing. Use when users ask about drug targets, proteins, genes, or need target validation, druggability assessment, or comprehensive target profiling.

25

You might also like

torchdrug

davila7

Graph-based drug discovery toolkit. Molecular property prediction (ADMET), protein modeling, knowledge graph reasoning, molecular generation, retrosynthesis, GNNs (GIN, GAT, SchNet), 40+ datasets, for PyTorch-based ML on molecules, proteins, and biomedical graphs.

326

string-database

davila7

Query STRING API for protein-protein interactions (59M proteins, 20B interactions). Network analysis, GO/KEGG enrichment, interaction discovery, 5000+ species, for systems biology.

217

transformer-lens-interpretability

davila7

Provides guidance for mechanistic interpretability research using TransformerLens to inspect and manipulate transformer internals via HookPoints and activation caching. Use when reverse-engineering model algorithms, studying attention patterns, or performing activation patching experiments.

215

denario

davila7

Multiagent AI system for scientific research assistance that automates research workflows from data analysis to publication. This skill should be used when generating research ideas from datasets, developing research methodologies, executing computational experiments, performing literature searches, or generating publication-ready papers in LaTeX format. Supports end-to-end research pipelines with customizable agent orchestration.

213

tooluniverse

jimmc414

Use this skill when working with scientific research tools and workflows across bioinformatics, cheminformatics, genomics, structural biology, proteomics, and drug discovery. This skill provides access to 600+ scientific tools including machine learning models, datasets, APIs, and analysis packages. Use when searching for scientific tools, executing computational biology workflows, composing multi-step research pipelines, accessing databases like OpenTargets/PubChem/UniProt/PDB/ChEMBL, performing tool discovery for research tasks, or integrating scientific computational resources into LLM workflows.

36

imaging-data-commons

K-Dense-AI

Query and download public cancer imaging data from NCI Imaging Data Commons using idc-index. Use for accessing large-scale radiology (CT, MR, PET) and pathology datasets for AI training or research. No authentication required. Query by metadata, visualize in browser, check licenses.

12

Search skills

Search the agent skills registry