
tooluniverse-antibody-engineering
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.
- Installs
- 389
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/mims-harvard/tooluniverse --skill tooluniverse-antibody-engineering- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads tooluniverse-antibody-engineering automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Antibody Engineering & Optimization
AI-guided antibody optimization pipeline from preclinical lead to clinical candidate. Covers sequence humanization, structure modeling, affinity optimization, developability assessment, immunogenicity prediction, and manufacturing feasibility.
KEY PRINCIPLES:
- Report-first approach - Create optimization report before analysis
- Evidence-graded humanization - Score based on germline alignment and framework retention
- Developability-focused - Assess aggregation, stability, PTMs, immunogenicity
- Structure-guided - Use AlphaFold/PDB structures for CDR analysis
- Clinical precedent - Reference approved antibodies for validation
- Quantitative scoring - Developability score (0-100) combining multiple factors
- English-first queries - Always use English terms in tool calls, even if user writes in another language. Respond in user's language
LOOK UP, DON'T GUESS
When uncertain about any scientific fact, SEARCH databases first (PubMed, UniProt, ChEMBL, ClinVar, etc.) rather than reasoning from memory. A database-verified answer is always more reliable than a guess.
When to Use
Apply when user asks:
- "Humanize this mouse antibody sequence"
- "Optimize antibody affinity for [target]"
- "Assess developability of this antibody"
- "Predict immunogenicity risk for [sequence]"
- "Engineer bispecific antibody against [targets]"
- "Reduce aggregation in antibody formulation"
- "Design pH-dependent binding antibody"
- "Analyze CDR sequences and suggest mutations"
Critical Workflow Requirements
1. Report-First Approach (MANDATORY)
- Create the report file FIRST:
antibody_optimization_report.md - Progressively update as analysis completes
- Output separate files:
optimized_sequences.fasta- All optimized variantshumanization_comparison.csv- Before/after comparisondevelopability_assessment.csv- Detailed scores
See REPORT_TEMPLATE.md for the full report template with section formats.
2. Documentation Standards (MANDATORY)
Every optimization MUST include per-variant documentation with:
- Original and optimized sequences
- Humanization score (% human framework)
- CDR preservation confirmation
- Metrics table (humanness, aggregation risk, predicted KD, immunogenicity)
- Data source citations
Phase 0: Tool Verification
Required Tools
| Tool | Purpose | Category |
|---|---|---|
IMGT_search_genes | Germline gene identification | Humanization |
IMGT_get_sequence | Human framework sequences | Humanization |
SAbDab_search_structures | Antibody structure precedents | Structure |
TheraSAbDab_search_by_target | Clinical antibody benchmarks | Validation |
ESMFold_predict_structure | Fv structure modeling (VH-linker-VL scFv) | Structure |
alphafold_get_prediction | Retrieve a precomputed AlphaFold DB model by UniProt accession (target antigen) | Structure |
iedb_search_epitopes | Epitope identification | Immunogenicity |
iedb_search_bcell | B-cell epitope prediction | Immunogenicity |
UniProt_get_entry_by_accession | Target antigen information | Target |
STRING_get_interaction_partners | Protein interaction network | Bispecifics |
PubMed_search_articles | Literature precedents | Validation |
CRITICAL: SOAP tools (IMGT, SAbDab, TheraSAbDab) require an operation parameter. See QUICK_START.md for correct usage.
Workflow Overview
Phase 1: Input Analysis & Characterization
├── Sequence annotation (CDRs, framework)
├── Species identification
├── Target antigen identification
├── Clinical precedent search
└── OUTPUT: Input characterization
↓
Phase 2: Humanization Strategy
├── Germline gene alignment (IMGT)
├── Framework selection
├── CDR grafting design
├── Backmutation identification
└── OUTPUT: Humanization plan
↓
Phase 3: Structure Modeling & Analysis
├── AlphaFold prediction
├── CDR conformation analysis
├── Epitope mapping
├── Interface analysis
└── OUTPUT: Structural assessment
↓
Phase 4: Affinity Optimization
├── In silico mutation screening
├── CDR optimization strategies
├── Interface improvement
└── OUTPUT: Affinity variants
↓
Phase 5: Developability Assessment
├── Aggregation propensity
├── PTM site identification
├── Stability prediction
├── Expression prediction
└── OUTPUT: Developability score
↓
Phase 6: Immunogenicity Prediction
├── MHC-II epitope prediction (IEDB)
├── T-cell epitope risk
├── Aggregation-related immunogenicity
└── OUTPUT: Immunogenicity risk score
↓
Phase 7: Manufacturing Feasibility
├── Expression level prediction
├── Purification considerations
├── Formulation stability
└── OUTPUT: Manufacturing assessment
↓
Phase 8: Final Report & Recommendations
├── Ranked variant list
├── Experimental validation plan
├── Next steps
└── OUTPUT: Comprehensive report
Phase 1: Input Analysis & Characterization
Goal: Annotate sequences, identify species/germline, find clinical precedents.
Key steps:
- Annotate CDRs using an antibody-numbering tool and map labels back to sequence indices (IMGT CDR-H1: 27-38, CDR-H2: 56-65, CDR-H3: 105-117). These labels are not literal array offsets, especially with insertions or terminal extensions.
- Identify closest human germline genes via
IMGT_search_genes - Search clinical precedents via
TheraSAbDab_search_by_target - Get target antigen info via
UniProt_get_entry_by_accession
Output: Sequence information table, CDR annotation, target info, clinical precedent list.
See WORKFLOW_DETAILS.md Phase 1 for code examples.
Phase 2: Humanization Strategy
Goal: Select human framework, design CDR grafting, identify backmutations.
Key steps:
- Search IMGT for IGHV/IGKV human germline genes
- Score candidate frameworks by identity, CDR compatibility, and clinical use
- Design CDR grafting onto selected framework
- Identify Vernier zone residues that may need backmutation (positions 2, 27-30, 47-48, 67, 69, 71, 78, 93-94)
- Generate at least 2 variants: full humanization and with key backmutations
- Calculate humanization score (framework humanness, CDR preservation, T-cell epitopes, aggregation risk)
Output: Framework selection rationale, grafting design, backmutation analysis, humanized sequences.
See WORKFLOW_DETAILS.md Phase 2 for code examples.
Phase 3: Structure Modeling & Analysis
Goal: Predict structure, analyze CDR conformations, map epitope.
Key steps:
- Predict Fv structure via
ESMFold_predict_structure(VH-linker-VL scFv;alphafold_get_predictiononly retrieves precomputed models by UniProt accession) - Assess pLDDT scores by region (framework, CDRs, interface)
- Classify CDR canonical structures and calculate RMSD
- Search known epitopes via
iedb_search_epitopes - Compare with clinical antibody structures via
SAbDab_search_structures
Output: Structure quality table, CDR conformation analysis, epitope mapping, structural comparison.
See WORKFLOW_DETAILS.md Phase 3 for code examples.
Phase 4: Affinity Optimization
Goal: Design affinity-improving mutations via computational screening.
Key steps:
- Identify interface residues (distance cutoff 4.5 A)
- Screen all amino acid substitutions at CDR interface positions
- Rank by computed binding-energy change only when the method and calibration support it; state the sign convention and uncertainty. An illustrative cutoff is not a universal binding gate.
- Design combination strategy: single -> double -> triple mutants
- Consider CDR-H3 extension, tyrosine enrichment, salt bridge formation
- Optional: specify stronger acidic binding or neutral binding with acidic release before considering histidine substitutions. Neither direction follows automatically from His pKa. Validate complete bound/free protonation assumptions with controls and matched assays; use Protein Design Campaign and its pH reference.
Output: Ranked mutation hypotheses, combination strategy, computed metrics where supported, and explicit unverified affinity/conditional-binding claims. Do not invent KD ranges or fold improvements.
See WORKFLOW_DETAILS.md Phase 4 for code examples.
Phase 5: Developability Assessment
Goal: Comprehensive developability scoring (0-100) across five dimensions.
Key steps:
- Aggregation, pI, hydrophobic patches (sequence-computable): run
scripts/developability.py --seq <VH/VL>. It returns AGGRESCAN aggregation-prone regions (real per-residue propensity), isoelectric point, and Kyte-Doolittle hydrophobic patches. - PTM liability: Scan for deamidation (NG/NS), isomerization (DG/DS), oxidation (Met/Trp), N-glycosylation (N-X-S/T)
- Stability (Tm) and 4. Expression titer: NOT computable from sequence alone — use external predictors (sequence→Tm/titer ML tools; report only if actually run). Do not fabricate Tm/titer numbers.
- Solubility: external solubility predictor (e.g. NetSolP)
Scoring: Weighted average (aggregation 0.30, PTM 0.25, stability 0.20, expression 0.15, solubility 0.10). Tiers: T1 (>75), T2 (60-75), T3 (<60).
Output: Component scores, overall score, tier classification, mitigation recommendations.
See WORKFLOW_DETAILS.md Phase 5 and CHECKLISTS.md for scoring details.
Phase 6: Immunogenicity Prediction
Goal: Predict immunogenicity risk and design deimmunization strategy.
Key steps:
- Scan 9-mer peptides against IEDB for MHC-II binding epitopes
- Count non-human residues in framework regions
- Assess aggregation-related immunogenicity
- Calculate total risk score (0-100, lower is better): Low <30, Medium 30-60, High >60
- Propose deimmunization mutations (remove T-cell epitopes while preserving CDRs)
- Compare with clinical precedent ADA rates
Output: T-cell epitope list, risk score breakdown, deimmunization strategy, clinical comparison.
See WORKFLOW_DETAILS.md Phase 6 for code examples.
Phase 7: Manufacturing Feasibility
Goal: Assess expression, purification, formulation, and CMC feasibility.
Key steps:
- Assess codon optimization for CHO, identify rare codons --
CodonUsage_get_optimal_codons(taxid=<Cricetulus griseus NCBI taxid>)gives the CHO-preferred codon per amino acid to compare against; resolve the taxid first if not already known rather than assuming one.CodonUsage_get_table(same taxid) additionally gives per-codon usage frequency, needed to flag which codons in the actual sequence are rare in CHO specifically -- human codon-usage tables (e.g. from tooluniverse-sequence-analysis) are the wrong reference here, rare-in-human is not the same set as rare-in-CHO - Design signal peptide
- Plan 3-step purification: Protein A capture -> cation exchange polishing -> viral nanofiltration
- Recommend formulation (buffer, pH, stabilizer, tonicity)
- Define analytical characterization panel (SEC-MALS, CEX, CE-SDS, SPR, DSF)
- Estimate CMC timeline and costs (typically 18-24 months, $1.65-2.65M to IND)
Output: Expression assessment, purification strategy, formulation recommendation, CMC timeline.
See MANUFACTURING.md for detailed manufacturing content and WORKFLOW_DETAILS.md Phase 7 for code.
Phase 8: Final Report & Recommendations
Goal: Compile all findings into a ranked recommendation with validation plan.
Key outputs:
- Top candidate with key metrics (humanness, affinity, developability, immunogenicity, stability, expression)
- Key improvements table comparing original vs. optimized
- Experimental validation plan: In vitro (3-4 months) -> Lead optimization (2-3 months) -> Preclinical (6-12 months)
- Backup variants with profiles and recommendations
- IP considerations: FTO analysis, CDR novelty, patentability
- Next steps: Immediate (month 1-3), short-term (4-6), long-term (7-24)
See REPORT_TEMPLATE.md for the full report template.
Tool Reference
IMGT Tools
IMGT_search_genes: Search germline genes (IGHV, IGKV, etc.)IMGT_get_sequence: Get germline sequencesIMGT_get_gene_info: Database information
Antibody Databases
SAbDab_search_structures: Search antibody structuresSAbDab_get_structure: Get structure detailsTheraSAbDab_search_therapeutics: Search by nameTheraSAbDab_search_by_target: Search by target antigen
Immunogenicity
iedb_search_epitopes: Search epitopesiedb_search_bcell: B-cell epitopesiedb_search_mhc: MHC-II epitopesiedb_get_epitope_references: Citations
Structure & Target
ESMFold_predict_structure: Fv structure prediction from a sequencealphafold_get_prediction: Retrieve a precomputed AlphaFold DB model by UniProt accessionUniProt_get_entry_by_accession: Target infoRCSBData_get_entry: Experimental structures
Reagent Verification (Antibody Registry)
AntibodyRegistry_search: Find validated commercial antibodies for a target (by target gene/protein name, antibody name, or vendor keyword). Returns each hit's RRID, target (with UniProt/Entrez id), clonality, host organism, applications, vendor/catalog number, and defining citation. Useful during Phase 1 (target/precedent research) to see what antibody reagents already exist against a target antigen before designing a new one, or during Phase 8 (validation planning) to identify a benchmark reagent.AntibodyRegistry_get_by_rrid: Resolve a specific RRID (e.g.AB_2298772, accepts the bare numeric id orRRID:AB_...form too) cited in a methods section to its full record — verify which exact antibody a paper used rather than assuming from the name alone. Live-verified: both tools return real records (e.g.AntibodyRegistry_search(query="GFAP")-> a real GFAP rabbit mAb with UniProt target P14136).SciCrunch_resolve_rrid: General RRID resolver for everything that ISN'T an antibody — cell lines (CVCL_prefix), model organisms, software/tools (SCR_prefix), and plasmids. Use it when a clinical-precedent or validation paper's methods section also cites the cell line or software used alongside an antibody. It will still resolve anAB_RRID, but only returns generic fields (name, description, categories, proper_citation) — no target/clonality/host — so preferAntibodyRegistry_get_by_rridfor antibody RRIDs specifically. Live-verified:SciCrunch_resolve_rrid(rrid="CVCL_0045")returns the real HEK293 cell-line record (12 synonyms,proper_citation: "NCBI_Iran Cat# C497, RRID:CVCL_0045"); on the sameAB_2298772antibody RRID above it returns onlyname/description/categorieswith no target info, confirming the richer-antibody-fields distinction.
Systems Biology (for Bispecifics)
STRING_get_interaction_partners: Protein interactionsSTRING_get_enrichment: Pathway analysis
Reference Files
| File | Contents |
|---|---|
QUICK_START.md | Getting started guide, SOAP tool parameters, Python SDK and MCP usage |
WORKFLOW_DETAILS.md | Code examples for all 8 phases |
REPORT_TEMPLATE.md | Full report template with section formats and example tables |
MANUFACTURING.md | Detailed manufacturing content (expression, purification, formulation, CMC) |
EXAMPLES.md | Complete clinical scenario examples (humanization, affinity, bispecific) |
CHECKLISTS.md | Evidence grading, completeness checklists, scoring details, special considerations |
FAQ
What does the tooluniverse-antibody-engineering skill do?
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.
How do I install tooluniverse-antibody-engineering?
Run npx skills add https://github.com/mims-harvard/tooluniverse --skill tooluniverse-antibody-engineering in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/tooluniverse-antibody-engineering/ (personal) or .claude/skills/tooluniverse-antibody-engineering/ (project).
Which AI agents can use tooluniverse-antibody-engineering?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is tooluniverse-antibody-engineering safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains tooluniverse-antibody-engineering?
It is published by mims-harvard in mims-harvard/tooluniverse. It has 389 recorded installs.
More from mims-harvard/tooluniverse
tooluniverse-sequence-retrieval
mims-harvard/tooluniverse
Retrieve DNA/RNA/protein sequences from NCBI and ENA with disambiguation. Quality hierarchy: RefSeq (NM/NP) RefSeq predicted (XM/XP) GenBank submissions. Use for fetching specific sequences by accession, gene-symbol-to-sequence lookup, transcript-isoform retrieval, and curated-vs-raw-submission preference.
tooluniverse-literature-deep-research
mims-harvard/tooluniverse
Deep literature review — PubMed, EuropePMC, bioRxiv preprints, citation networks, evidence synthesis. Disambiguates queries, runs collision-aware searches, grades evidence T1-T4, and produces structured reports. Use for systematic literature review, meta-analysis evidence collection, and detailed answer-with-citations workflows.
tooluniverse-image-analysis
mims-harvard/tooluniverse
Microscopy and quantitative imaging analysis — colony morphometry, fluorescence intensity quantification, cell-count statistics, dose-response curves, and ANOVA/Dunnett on image-derived measurements. Uses pandas/numpy/scipy/scikit-image. Use for analyzing tabular outputs from CellProfiler/ImageJ, image-derived measurement statistics, and image-based assay quantification.
tooluniverse-clinical-guidelines
mims-harvard/tooluniverse
Search and retrieve clinical practice guidelines from 12+ authoritative sources — NICE, WHO, NCCN, AHA, ADA, SIGN, USPSTF, IDSA, NIH consensus, ESMO/ESC/EASL European societies, and US specialty associations. Use for evidence-graded treatment recommendations, dosing protocols, screening guidance, and authoritative-source-prioritized clinical guidance (NICE/WHO ranked above society guidelines).
tooluniverse
mims-harvard/tooluniverse
ToolUniverse plugin router. STEP 1 BEFORE ANY ANALYSIS: if the data folder contains executed.ipynb, run tu run readexecutednotebook '{"datafolder":" ","search":" "}' to extract its cell outputs and apply EVERY filter/sample-exclusion the notebook used — even when the question says 'Using DESeq2/Run X/Compute Y' (this describes the METHOD the notebook used, not a request to rerun). The notebook's cell outputs are the only published authoritative answers; reimplementing or reading stale pre-computed CSVs in the data folder produces different numbers because of outlier-sample removal, library version, and filter steps you don't see by skimming. STEP 2 routing — pick a sub-skill name from this exact list (never invent): tooluniverse-rnaseq-deseq2 (RNA/miRNA-seq DE, correlation, PCA, clustering, dispersion), tooluniverse-gene-enrichment (GO/KEGG/Reactome/GSEA/pathway enrichment), tooluniverse-statistical-modeling (regression, ANOVA, ordinal/logistic, chi-square, correl
tooluniverse-drug-research
mims-harvard/tooluniverse
Comprehensive drug profiling — mechanism, primary/secondary targets, drug interactions, clinical-trial status, adverse events (FAERS), pharmacogenomics, and approval history. Use for full drug investigation reports, 'tell me about drug X' queries, and assembling drug profiles for clinicians, researchers, or regulatory work.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.