Source profileQuality 90/100Review permissions

K-Dense-AI/scientific-agent-skills/skills/torchdrug/SKILL.md

torchdrug

Build and troubleshoot TorchDrug 0.2.1 workflows for molecular graphs, property prediction, self-supervised pretraining, molecule generation, retrosynthesis, protein representation learning, and knowledge graph reasoning. Use when code imports torchdrug or needs its datasets, models, tasks, or Engine.

Source repository stars
31,966
Declared platforms
0
Static risk flags
2
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Use TorchDrug as a modular PyTorch graph-learning stack:

Best for

  • Use when code imports torchdrug or needs its datasets, models, tasks, or Engine.

Not for

  • Installation or import failure
  • Feature dimension mismatch

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/K-Dense-AI/scientific-agent-skills --skill "skills/torchdrug"
Safe inspection promptEditorial

Inspect the Agent Skill "torchdrug" from https://github.com/K-Dense-AI/scientific-agent-skills/blob/e7ac42510774624f327003c95b6650e2883bc01d/skills/torchdrug/SKILL.md at commit e7ac42510774624f327003c95b6650e2883bc01d. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Canonical property-prediction workflow

    Use the documented ClinTox → GIN → PropertyPrediction → Engine pattern:

    Use the documented ClinTox → GIN → PropertyPrediction → Engine pattern:Add gpus=[0] only when a supported CUDA device is available. Omit gpus for CPU execution.For binary classification, task.predict(batch) returns logits; apply torch.sigmoid when probabilities are needed. In 0.2.1, normalized regression predictions are returned on the original target scale, which is a breakin…
  2. 02

    Choose the official workflow

    Dataset: datasets.ClinTox, BBBP, Tox21, QM9, or another documented

    Dataset: datasets.ClinTox, BBBP, Tox21, QM9, or another documentedModel: start with models.GIN; use edgeinputdim when the selected featureTask: tasks.PropertyPrediction.
  3. 03

    Start with the version guard

    Before generating or debugging code, inspect the environment:

    Python 3.7 through 3.10PyTorch 1.8 through 2.0Linux, Windows, or macOS
  4. 04

    Installation

    Prefer a dedicated Python 3.10 environment and pin the TorchDrug release:

    Prefer a dedicated Python 3.10 environment and pin the TorchDrug release:Install torch-scatter and torch-cluster wheels matched to the exact PyTorch and CUDA pair, following the official installation page. For a CPU-only PyTorch 2.0 environment, one reproducible wheel combination is:Do not copy a CUDA wheel URL between environments. Match the PyTorch version, CUDA build, Python ABI, and platform. On Apple Silicon, the official docs require building torch-scatter and torch-cluster from source; pin r…
  5. 05

    Molecular property prediction

    Dataset: datasets.ClinTox, BBBP, Tox21, QM9, or another documented

    Dataset: datasets.ClinTox, BBBP, Tox21, QM9, or another documentedModel: start with models.GIN; use edgeinputdim when the selected featureTask: tasks.PropertyPrediction.

Permission review

Static risk signals and limitations

Runs scripts

medium · line 19

The documentation asks the agent to run terminal commands or scripts.

python --version

Runs scripts

medium · line 20

The documentation asks the agent to run terminal commands or scripts.

python -c "import torch; print(torch.__version__)"

Network access

medium · line 51

The documentation includes network, browsing, or remote request actions.

-find-links "https://data.pyg.org/whl/torch-2.0.0+cpu.html"

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score90/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars31,966SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
K-Dense-AI/scientific-agent-skills
Skill path
skills/torchdrug/SKILL.md
Commit
e7ac42510774624f327003c95b6650e2883bc01d
License
MIT
Collected
2026-07-28
Default branch
main
View the original SKILL.md

TorchDrug

Use TorchDrug as a modular PyTorch graph-learning stack:

  1. load a datasets.* dataset,
  2. choose a models.* representation model,
  3. wrap it in a tasks.* objective,
  4. train and evaluate it with core.Engine.

The current official documentation and latest release are both 0.2.1. Treat newer Python or PyTorch combinations as unverified rather than silently assuming compatibility.

Start with the version guard

Before generating or debugging code, inspect the environment:

python --version
python -c "import torch; print(torch.__version__)"
python -c "import torchdrug; print(torchdrug.__version__)"

The supported matrix for TorchDrug 0.2.1 is:

  • Python 3.7 through 3.10
  • PyTorch 1.8 through 2.0
  • Linux, Windows, or macOS
  • Apple Silicon: PyTorch 1.13 or later, CPU only; no MPS support

If the project uses Python 3.11+ or PyTorch 2.1+, create a compatible environment or explicitly test a source build. Do not present such combinations as supported.

Installation

Prefer a dedicated Python 3.10 environment and pin the TorchDrug release:

uv venv --python 3.10
source .venv/bin/activate
uv pip install "torch==2.0.0"

Install torch-scatter and torch-cluster wheels matched to the exact PyTorch and CUDA pair, following the official installation page. For a CPU-only PyTorch 2.0 environment, one reproducible wheel combination is:

uv pip install "torch-scatter==2.1.1" "torch-cluster==1.6.1" \
  --find-links "https://data.pyg.org/whl/torch-2.0.0+cpu.html"
uv pip install "torchdrug==0.2.1"

Do not copy a CUDA wheel URL between environments. Match the PyTorch version, CUDA build, Python ABI, and platform. On Apple Silicon, the official docs require building torch-scatter and torch-cluster from source; pin reviewed source revisions and expect CPU execution.

Canonical property-prediction workflow

Use the documented ClinTox → GIN → PropertyPredictionEngine pattern:

import torch
from torchdrug import core, datasets, models, tasks

dataset = datasets.ClinTox("~/molecule-datasets/")
lengths = [int(0.8 * len(dataset)), int(0.1 * len(dataset))]
lengths.append(len(dataset) - sum(lengths))
train_set, valid_set, test_set = torch.utils.data.random_split(dataset, lengths)

model = models.GIN(
    input_dim=dataset.node_feature_dim,
    hidden_dims=[256, 256, 256, 256],
    short_cut=True,
    batch_norm=True,
    concat_hidden=True,
)
task = tasks.PropertyPrediction(
    model,
    task=dataset.tasks,
    criterion="bce",
    metric=("auprc", "auroc"),
)

optimizer = torch.optim.Adam(task.parameters(), lr=1e-3)
solver = core.Engine(
    task,
    train_set,
    valid_set,
    test_set,
    optimizer,
    batch_size=1024,
)
solver.train(num_epoch=100)
solver.evaluate("valid")

Add gpus=[0] only when a supported CUDA device is available. Omit gpus for CPU execution.

For binary classification, task.predict(batch) returns logits; apply torch.sigmoid when probabilities are needed. In 0.2.1, normalized regression predictions are returned on the original target scale, which is a breaking change from older releases.

Choose the official workflow

Molecular property prediction

  • Dataset: datasets.ClinTox, BBBP, Tox21, QM9, or another documented molecule dataset.
  • Model: start with models.GIN; use edge_input_dim when the selected feature configuration supplies edge features.
  • Task: tasks.PropertyPrediction.
  • Read molecular property prediction.

Self-supervised molecular pretraining

  • InfoGraph: models.InfoGraph(gin_model, separate_model=False) wrapped by tasks.Unsupervised.
  • Attribute masking: tasks.AttributeMasking(model, mask_rate=0.15).
  • Recreate the same encoder for fine-tuning, then load the checkpoint with strict=False before training tasks.PropertyPrediction.
  • Read molecular property prediction.

Molecule generation

  • Dataset: datasets.ZINC250k(..., kekulize=True, atom_feature="symbol").
  • GCPN: an models.RGCN encoder wrapped by tasks.GCPNGeneration.
  • GraphAF: node and edge models.GraphAF flows wrapped by tasks.AutoregressiveGeneration.
  • Supported optimization tasks in the tutorial are "qed" and "plogp"; criteria are "nll" and/or "ppo".
  • Read molecular generation.

Retrosynthesis

  • Create two synchronized datasets.USPTO50k views: reaction mode for center identification and as_synthon=True for synthon completion.
  • Train tasks.CenterIdentification and tasks.SynthonCompletion separately.
  • Combine the trained tasks with tasks.Retrosynthesis; do not pass raw models directly to the end-to-end task.
  • Read retrosynthesis.

Knowledge graph reasoning

  • Embedding workflow: datasets.FB15k237models.RotatEtasks.KnowledgeGraphCompletion.
  • Neural reasoning workflow: models.NeuralLP with fact_ratio=0.75.
  • Read knowledge graph reasoning.

Protein modeling

  • Build proteins with data.Protein.from_sequence, from_pdb, or from_molecule.
  • Sequence encoders include models.ESM, ProteinCNN, ProteinResNet, ProteinLSTM, and ProteinBERT; structure encoders include models.GearNet.
  • Use documented graph-construction layers rather than a nonexistent protein.residue_graph() convenience method.
  • Read protein modeling.

Rules for reliable TorchDrug code

  1. Follow the 0.2.1 API. The official docs are not a rolling latest-version site.
  2. Prefer documented feature names. Use atom_feature, bond_feature, residue_feature, and mol_feature; node_feature, edge_feature, and graph_feature are deprecated aliases in relevant dataset constructors.
  3. Let Engine preprocess tasks. If composing pre-trained tasks without constructing their solvers, call each task's preprocess() manually.
  4. Keep paired splits synchronized. For retrosynthesis, reset the same random seed before splitting reaction and synthon datasets.
  5. Use TorchDrug collation. Use data.graph_collate or core.Engine; generic PyTorch collation does not know how to pack TorchDrug graphs.
  6. Separate model, task, and engine arguments. A common source of invented code is passing task options to a model or passing raw models where a composed task is required.
  7. Validate generated chemistry. Treat model outputs as candidates, not as experimentally valid or synthesizable compounds.

Troubleshooting

Installation or import failure

Check Python, PyTorch, torch-scatter, and torch-cluster as one compatibility set. Most failures are binary-wheel mismatches, unsupported Python versions, or attempts to use MPS.

Feature dimension mismatch

Build model dimensions from the loaded dataset:

  • dataset.node_feature_dim
  • dataset.edge_feature_dim
  • dataset.num_bond_type
  • dataset.num_entity and dataset.num_relation for knowledge graphs

Do not hard-code dimensions copied from a different feature configuration.

Device mismatch

Pass gpus=[0] to core.Engine for supported CUDA execution. For manual prediction, collate first and move the entire nested batch with utils.cuda.

Checkpoint mismatch

Recreate the same model and feature configuration. For pretraining-to-fine-tuning transfer, load the checkpoint's "model" state with strict=False; for a complete solver, use solver.save() and solver.load().

Reference index

Upstream sources

Alternatives

Compare before choosing

Computed 9831,966

K-Dense-AI/scientific-agent-skills

dask

Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.

Computed 9831,966

K-Dense-AI/scientific-agent-skills

medchem

Medicinal chemistry filters for compound triage. Apply drug-likeness rules (Lipinski, Veber, CNS), structural alert catalogs (PAINS, NIBR, ChEMBL), complexity metrics, and the medchem query language for library filtering.

Computed 9831,966

K-Dense-AI/scientific-agent-skills

neurokit2

Use NeuroKit2 to build or audit reproducible research workflows for physiological time-series preprocessing, event/interval analysis, multimodal alignment, variability, and complexity. Trigger when code imports neurokit2 or needs its current APIs, schemas, and method-aware validation—not for diagnosis or device validation.

Computed 9637,126

github/awesome-copilot

flowstudio-power-automate-mcp

Foundation skill for Power Automate via FlowStudio MCP — auth setup, the reusable MCP helper (Python + Node.js), tool discovery via `list_skills` / `tool_search`, and oversized-response handling. Load this skill first when connecting an agent to Power Automate. For specialized workflows, load `flowstudio-power-automate-build`, `flowstudio-power-automate-debug`, `flowstudio-power-automate-monitoring` (Pro+), or `flowstudio-power-automate-governance` (Pro+) — each contains the workflow narrative,