Skip to main content
ClaudeWave
Skill1.4k repo starsupdated today

tooluniverse-enzyme-kinetics

This Claude Code skill analyzes substrate-velocity data to extract Michaelis-Menten kinetic parameters (Km, Vmax, kcat, catalytic efficiency) through nonlinear regression and classifies enzyme inhibition mechanisms (competitive, uncompetitive, non-competitive) with inhibition constants (Ki). Use it when you have experimental measurements of initial reaction rates at multiple substrate concentrations and need to quantify enzyme kinetics or determine how a small molecule inhibits your enzyme, not for retrieving published constants from databases.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/mims-harvard/ToolUniverse /tmp/tooluniverse-enzyme-kinetics && cp -r /tmp/tooluniverse-enzyme-kinetics/plugin/skills/tooluniverse-enzyme-kinetics ~/.claude/skills/tooluniverse-enzyme-kinetics
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# Enzyme Kinetics (Michaelis-Menten)

Turn **substrate concentration vs initial velocity** data into Km, Vmax, kcat, and catalytic efficiency — and classify an inhibitor's mechanism.

The Michaelis-Menten model: `v = Vmax·[S] / (Km + [S])`.

## When to use this

- You measured initial reaction rates at several substrate concentrations.
- You need Km (substrate affinity), Vmax, kcat (turnover number), or kcat/Km.
- You have ±inhibitor velocity data and want to classify the inhibition mode + Ki.

For *published* kinetic constants (someone else's Km/kcat), use the BRENDA tools instead — this skill is for analyzing **your own measured** data.

## Step 1 — Prepare the data

| Issue | What to do |
|---|---|
| **Initial velocities, not endpoints** | `v` must be the *initial* rate (linear phase, <10% substrate consumed). Endpoint or plateaued rates give a wrong Km/Vmax. |
| **Substrate range must span Km** | Include `[S]` both well below and well above Km (ideally ~0.2×Km to ~5×Km). Points only above Km can't define Km; only below can't define Vmax. |
| **Units — be consistent** | One `[S]` unit (mM, µM) → Km comes back in that unit. One velocity unit. Keep them fixed. |
| **For kcat you need [E]** | kcat = Vmax / [E]total. The tool's "catalytic_efficiency" is Vmax/Km on the velocity scale; to get true kcat (per-second turnover) and kcat/Km, divide Vmax by the molar enzyme concentration yourself. |
| **≥5–7 points** | Few points → unstable fit. Spread them across the range, not clustered. |

## Step 2 — Fit Michaelis-Menten

```bash
tu run EnzymeKinetics_calculate '{"operation":"michaelis_menten",
  "substrate_concs":[0.1,0.25,0.5,1,2,5,10],
  "velocities":[8.5,18,32,52,72,90,98]}'
```

Returns a `nonlinear_fit` block (`Vmax`, `Km`, `R2`, `SSE`) **— use these as the answer**, a `lineweaver_burk` block (for reference only), `catalytic_efficiency` (Vmax/Km), and `predicted_velocities` + `residuals`.

> **Prefer the nonlinear fit, not Lineweaver-Burk.** The double-reciprocal (Lineweaver-Burk) linearization distorts error (it over-weights low-`[S]` points) and is only for visualization/sanity — never report its Km/Vmax as the final values. The tool gives both; cite `nonlinear_fit`.

`scripts/fit_michaelis_menten.py` does the same nonlinear fit from a CSV and converts Vmax→kcat→kcat/Km when you supply the enzyme concentration.

## Step 3 — Interpret

| Parameter | Meaning | Notes |
|---|---|---|
| **Km** | Substrate concentration at ½Vmax — *apparent affinity* (lower Km = tighter binding / higher affinity). | In the same units as `[S]`. Must lie inside your tested range to be trustworthy. |
| **Vmax** | Maximum velocity at saturating substrate. | Depends on [E]; not an intrinsic enzyme property. |
| **kcat** | Turnover number = Vmax/[E] (per second). | Requires the molar enzyme concentration; intrinsic to the enzyme. |
| **kcat/Km** | Catalytic efficiency / specificity constant. | The best single metric to compare enzymes or substrates; near ~10⁸–10⁹ M⁻¹s⁻¹ is diffusion-limited ("catalytically perfect"). |
| **R² / SSE** | Fit quality. | R²≥0.98 good; check `residuals` for systematic curvature (a pattern, not random scatter, means MM is the wrong model). |

## Step 4 — Inhibition mechanism

Provide velocities ±inhibitor to classify the mode:

```bash
tu run EnzymeKinetics_calculate '{"operation":"inhibition",
  "substrate_concs":[...],
  "velocities_no_inhibitor":[...],
  "velocities_with_inhibitor":[...],
  "inhibitor_conc":5, "inhibition_type":"competitive"}'
```

| Mechanism | Effect on apparent Km | Effect on Vmax | Signature |
|---|---|---|---|
| **Competitive** | ↑ (increases) | unchanged | inhibitor competes at the active site; beatable by more substrate |
| **Uncompetitive** | ↓ (decreases) | ↓ | inhibitor binds only the ES complex |
| **Non-competitive (mixed)** | ~unchanged (pure) / changes (mixed) | ↓ | binds enzyme and ES; not relieved by substrate |

Ki is the inhibition constant (lower = more potent inhibitor). Decide the mechanism from how Km and Vmax shift, not from a single Lineweaver-Burk eyeball.

## Step 5 — Gotchas (state these)

- **Substrate inhibition** (velocity rises then *falls* at high `[S]`) breaks MM — the fit will show systematic residuals; flag it instead of forcing one Km.
- **Km outside the tested range** → unreliable; widen `[S]`.
- **kcat without [E]** is impossible — don't report a turnover number if you only fit velocities.
- **Lineweaver-Burk for final numbers** is the classic error — it's for a quick plot, not the reported Km/Vmax.

## Honest limitations

- MM assumes a single substrate, initial-rate, steady-state, one active site. Allosteric (sigmoidal) enzymes need the Hill equation; multi-substrate enzymes need their own formalism.
- Parameters are only as good as the substrate range and the initial-rate measurement.

## Related skills
- `tooluniverse-dose-response` — IC50/EC50 (the Hill/4PL sibling for concentration-response).
- `tooluniverse-statistical-modeling` — general nonlinear regression and model comparison.
- BRENDA tools — look up *published* enzyme kinetic constants.
setup-tooluniverseSkill

Install and configure ToolUniverse for any use case — MCP server (chat-based), CLI (command line with 9 subcommands), or Python SDK (Coding API with 3 calling patterns). Covers uv/uvx setup, MCP configuration for 12+ AI clients (Cursor, Claude Desktop, Windsurf, VS Code, Codex, Gemini CLI, Trae, Cline, etc.), full CLI reference (tu list/grep/find/info/run/test/status/build/serve), Coding API quickstart, agentic tools, code executor, API key walkthrough, skill installation, and upgrading. Use when user asks how to set up ToolUniverse, which access mode to use (MCP vs CLI vs SDK), configuring MCP servers, using the CLI, troubleshooting installation, upgrading, or mentions installing ToolUniverse or setting up scientific tools. Also triggers for "how do I use ToolUniverse", "what's the best way to access tools", "command line", "tu command", "coding API", "tu build".

tooluniverse-acmg-variant-classificationSkill

Systematic ACMG/AMP germline variant classification with all 28 criteria (PVS1, PS1-4, PM1-6, PP1-5, BA1, BS1-4, BP1-7) for clinical significance. Produces 5-tier verdict (Pathogenic / Likely Pathogenic / VUS / Likely Benign / Benign) with cited evidence per criterion. Use for variant interpretation, VUS resolution, and pathogenicity assessment. Combines ClinVar, gnomAD, computational predictors, and gene-mechanism context.

tooluniverse-admet-predictionSkill

Comprehensive ADMET (Absorption, Distribution, Metabolism, Excretion, Toxicity) profiling for drug candidates. Integrates ADMET-AI predictions, SwissADME drug-likeness, PubChemTox experimental toxicity, ChEMBL clinical data, Lipinski rule-of-five, and CYP interaction data. Use for drug-likeness assessment, BBB penetration, bioavailability, hepatotoxicity prediction, ADME/PK profiling, or screening compound libraries before lab testing.

tooluniverse-adverse-event-detectionSkill

Detect and analyze adverse drug event signals using FDA FAERS reports, drug labels, and disproportionality statistics (PRR, ROR, IC). Generates quantitative safety signal scores (0-100) with evidence grading. Use for post-market surveillance, pharmacovigilance, drug safety assessment, regulatory submissions, and detecting rare AE signals not visible in clinical trials.

tooluniverse-adverse-outcome-pathwaySkill

Map environmental and industrial chemicals to adverse outcome pathways (AOPs) — molecular initiating event to organ-level toxicity. Uses AOPWiki, GHS classification, IARC carcinogen status, and LD50 data. Use for environmental/industrial chemical risk assessment, regulatory-grade hazard characterization, and AOP stressor mapping. Distinct from drug-safety analysis (use tooluniverse-pharmacovigilance for drugs).

tooluniverse-aging-senescenceSkill

Aging biology, cellular senescence, and longevity research. Covers senescence markers (p16/CDKN2A, SASP, SA-beta-gal), aging hallmarks, senolytic drug discovery (dasatinib+quercetin, fisetin, navitoclax), epigenetic clocks, telomere biology, and longevity GWAS. Use for senescence-pathway analysis, age-related disease genetics, senolytic-target discovery, and centenarian-genetics queries. Distinguishes correlative vs causal evidence (knockout, intervention).

tooluniverse-antibody-engineeringSkill

Therapeutic antibody engineering and optimization, lead-to-clinical-candidate. Covers sequence humanization (germline alignment, framework retention), affinity maturation, developability (aggregation, stability, PTMs), structure modeling (AlphaFold/PDB CDR analysis), immunogenicity prediction, and manufacturing feasibility. Use for biologic-drug optimization, mAb design review, biosimilar engineering, and clinical-precedent comparison.

tooluniverse-binder-discoverySkill

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.