agentleFS
PharMolixPharMolix/OpenBioMed/skills/admet-prediction/SKILL.md

admet-prediction

Skill1.1k starsChanged 8 months agoMITView on GitHub

Predict comprehensive ADMET (Absorption, Distribution, Metabolism, Excretion, Toxicity) properties for drug candidate molecules using GraphMVP ensemble models. Use this skill when: (1) Predicting blood-brain barrier penetration, (2) Assessing side effect profiles, (3) Estimating Caco-2 permeability, half-life, or LD50 toxicity, (4) Evaluating drug-likeness and safety of molecules.

4 other projects use a version of this.

Trending

Quiet this year.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the PharMolix/OpenBioMed repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about PharMolix/OpenBioMed

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create molecule from SMILES string.

    line 32
  2. Very specific:

    Solution: Ensure checkpoints exist in ./checkpoints/server/:

    line 123
  3. Distinctive:

    Solution: Use CPU instead:

    line 132

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ADMET Prediction

Predict comprehensive ADMET properties for drug candidate molecules using GraphMVP ensemble models.

When to Use

  • User asks to predict ADMET properties for a molecule
  • User provides a drug candidate and wants safety assessment
  • User needs blood-brain barrier penetration prediction
  • User wants to evaluate toxicity (LD50) or side effects (SIDER)
  • User requests pharmacokinetic properties (half-life, Caco-2)

Workflow

Step 1: Load Molecule

Create molecule from SMILES string.

from open_biomed.data import Molecule
molecule = Molecule.from_smiles("CC(=O)OC1=CC=CC=C1C(=O)O")  # Aspirin

Step 2: Build ADMET Pipeline

Initialize ensemble pipeline with all GraphMVP checkpoints.

from open_biomed.core.pipeline import InferencePipeline, EnsemblePipeline

pipelines = {
    "BBBP": InferencePipeline(
        task="molecule_property_prediction", model="graphmvp",
        model_ckpt="./checkpoints/server/graphmvp-BBBP.ckpt",
        additional_config="./configs/dataset/bbbp.yaml", device="cuda:0"),
    "SIDER": InferencePipeline(
        task="molecule_property_prediction", model="graphmvp",
        model_ckpt="./checkpoints/server/graphmvp-SIDER.ckpt",
        additional_config="./configs/dataset/sider.yaml", device="cuda:0"),
    # See examples/basic_example.py for full pipeline setup
}
pipeline = EnsemblePipeline(pipelines)

Step 3: Run Predictions

Execute predictions for each ADMET property.

# BBB penetration
bbb_result = pipeline.run(molecule=molecule, task="BBBP")

# Side effects (27 categories)
sider_result = pipeline.run(molecule=molecule, task="SIDER")

# Regression properties
caco2_result = pipeline.run(molecule=molecule, task="caco2_wang")
half_life_result = pipeline.run(molecule=molecule, task="half_life_obach")
ld50_result = pipeline.run(molecule=molecule, task="ld50_zhu")

Expected Outputs

TaskOutput TypeDescription
BBBPfloat [0-1]Probability of BBB penetration
SIDERlist[27 floats]Side effect probabilities per category
caco2_wangfloatLog permeability (cm/s)
half_life_obachfloatLog half-life (hours)
ld50_zhufloatLog LD50 (mg/kg)

Interpretation Guide

BBB Penetration

ValueInterpretation
> 0.5Likely crosses BBB
< 0.5Unlikely to cross BBB

Caco-2 Permeability

Value (log cm/s)Interpretation
> -5High absorption
-6 to -5Moderate absorption
< -6Low absorption

LD50 Toxicity

Value (log mg/kg)Toxicity Level
< 1Highly toxic (<10 mg/kg)
1-2Moderately toxic (10-100 mg/kg)
2-3Slightly toxic (100-1000 mg/kg)
> 3Low toxicity (>1000 mg/kg)

SIDER Side Effects

Values range 0-1. Categories with > 0.7 indicate high risk of that side effect.

Error Handling

Checkpoint Not Found

Symptom: FileNotFoundError: graphmvp-*.ckpt

Solution: Ensure checkpoints exist in ./checkpoints/server/:

ls checkpoints/server/graphmvp-*.ckpt

CUDA Out of Memory

Symptom: RuntimeError: CUDA out of memory

Solution: Use CPU instead:

# Change device from "cuda:0" to "cpu"
device="cpu"

Invalid SMILES

Symptom: Molecule fails to parse

Solution: Validate SMILES format or use molecule name lookup via PubChem.

Example

Input: aspirin (CC(=O)OC1=CC=CC=C1C(=O)O)

Output:
  BBB Penetration: 0.19 (does NOT cross BBB)
  Caco-2: -4.68 (moderate absorption)
  Half-life: -7.06 (short half-life)
  LD50: 2.06 (moderate toxicity ~115 mg/kg)

  Top Side Effects:
    Skin disorders: 0.80
    Nervous system: 0.78
    Gastrointestinal: 0.78

See Also

  • examples/basic_example.py - Full runnable example with all properties
  • references/sider_categories.md - Complete SIDER category list
  • references/interpretation.md - Detailed interpretation guidelines

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.