Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Predict peptide-MHC class I and II binding affinity using MHCflurry and NetMHCpan neural network models. Identify potential T-cell epitopes from protein sequences. Use when predicting MHC binding for vaccine design or neoantigen identification.
.claude/skills/bio-immunoinformatics-mhc-binding-prediction/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-02 | ✗→✓ | ▲ Improved | — | — |
| case-01 | ✗→✓ | ▲ Improved | — | — |
| case-07 | ✗→✓ | ▲ Improved | — | — |
| case-19 | ✓→✓ | = Same ✓ | — | — |
| case-10 | ✓→✓ | = Same ✓ | — | — |
Reference examples tested with: MHCflurry 2.1+, pandas 2.2+
Before using code patterns, verify installed versions match. If versions differ:
pip show <package> then help(module.function) to check signatures<tool> --version then <tool> --help to confirm flagsIf code throws ImportError, AttributeError, or TypeError, introspect the installed package and adapt the example to match the actual API rather than retrying.
"Predict which peptides bind to MHC" → Predict peptide-MHC class I and II binding affinity using neural network models to identify potential T-cell epitopes from protein sequences.
mhcflurry.Class1PresentationPredictor().predict() for MHC-InetMHCpan for alternative MHC-I/II predictionsGoal: Install MHCflurry and download pre-trained prediction models.
Approach: Install via pip and fetch model weights for class I pan-allele or specific allele predictions.
bash# Install MHCflurry pip install mhcflurry # Download prediction models mhcflurry-downloads fetch # Download models for specific alleles mhcflurry-downloads fetch models_class1_pan
Goal: Predict peptide-MHC binding affinity and presentation scores for a set of peptides.
Approach: Load the Class1PresentationPredictor and call predict() with peptide-allele pairs to obtain IC50, percentile rank, and presentation scores.
pythonfrom mhcflurry import Class1PresentationPredictor # Load predictor (includes binding and processing scores) predictor = Class1PresentationPredictor.load() # Predict for single allele result = predictor.predict( peptides=['SIINFEKL', 'GILGFVFTL', 'NLVPMVATV'], alleles=['HLA-A*02:01', 'HLA-A*02:01', 'HLA-A*02:01'] ) # Result columns: # - mhcflurry_affinity: Predicted IC50 (nM) # - mhcflurry_affinity_percentile: Percentile rank # - mhcflurry_presentation_score: Combined binding + processing print(result)
Goal: Classify peptide-MHC binding strength from predicted IC50 values.
Approach: Apply standard affinity thresholds (strong <50nM, moderate <500nM, weak <5000nM) to categorize binding.
pythondef interpret_binding(ic50_nm): '''Interpret MHC binding affinity IC50 thresholds (commonly used): - <50 nM: Strong binder (high confidence epitope) - 50-500 nM: Moderate binder (potential epitope) - 500-5000 nM: Weak binder (unlikely epitope) - >5000 nM: Non-binder Percentile rank (recommended): - <0.5%: Strong binder - 0.5-2%: Moderate binder - >2%: Weak/non-binder ''' if ic50_nm < 50: return 'strong' elif ic50_nm < 500: return 'moderate' elif ic50_nm < 5000: return 'weak' else: return 'non-binder'
Goal: Predict binding for all peptide-allele combinations in a batch.
Approach: Iterate over peptide-allele pairs, call MHCflurry for each combination, and concatenate results into a single DataFrame.
pythonfrom mhcflurry import Class1PresentationPredictor import pandas as pd def predict_binding_batch(peptides, alleles): '''Predict binding for multiple peptides and alleles Args: peptides: List of peptide sequences alleles: List of HLA alleles (4-digit format) Returns: DataFrame with predictions for all combinations ''' predictor = Class1PresentationPredictor.load() # Create all combinations results = [] for peptide in peptides: for allele in alleles: pred = predictor.predict( peptides=[peptide], alleles=[allele] ) pred['peptide'] = peptide pred['allele'] = allele results.append(pred) return pd.concat(results, ignore_index=True) # Example usage peptides = ['SIINFEKL', 'GILGFVFTL', 'NLVPMVATV', 'YMLDLQPETT'] alleles = ['HLA-A*02:01', 'HLA-A*03:01', 'HLA-B*07:02'] predictions = predict_binding_batch(peptides, alleles) print(predictions[['peptide', 'allele', 'mhcflurry_affinity', 'mhcflurry_affinity_percentile']])
Goal: Identify all potential MHC-I epitopes within a protein by scanning overlapping peptide windows.
Approach: Generate all k-mers (8-11aa) from the protein, predict binding for each against target alleles, and retain those below the 2% percentile rank cutoff.
pythondef scan_protein_for_epitopes(protein_seq, alleles, peptide_lengths=[8, 9, 10, 11]): '''Scan protein for potential MHC epitopes MHC-I typically binds 8-11mer peptides Most common: 9-mers Returns all peptides with predicted binding ''' from mhcflurry import Class1PresentationPredictor predictor = Class1PresentationPredictor.load() epitopes = [] for length in peptide_lengths: for i in range(len(protein_seq) - length + 1): peptide = protein_seq[i:i + length] for allele in alleles: pred = predictor.predict(peptides=[peptide], alleles=[allele]) if pred['mhcflurry_affinity_percentile'].values[0] < 2.0: epitopes.append({ 'peptide': peptide, 'position': i + 1, 'length': length, 'allele': allele, 'affinity_nM': pred['mhcflurry_affinity'].values[0], 'percentile': pred['mhcflurry_affinity_percentile'].values[0] }) return pd.DataFrame(epitopes)
Goal: Predict MHC class II binding for longer peptides (13-25aa) relevant to CD4+ T-cell responses.
Approach: Query the IEDB NetMHCIIpan API since MHCflurry focuses on class I; submit peptide-allele pairs and parse results.
pythondef predict_mhc_ii(peptides, alleles): '''Predict MHC class II binding MHC-II binds longer peptides (13-25 aa) Binding core is ~9aa but flanking regions matter Note: MHCflurry focuses on class I For class II, use NetMHCIIpan or IEDB tools ''' # NetMHCIIpan via IEDB API import requests url = 'http://tools-cluster-interface.iedb.org/tools_api/mhcii/' results = [] for peptide in peptides: for allele in alleles: params = { 'method': 'netmhciipan_ba', 'sequence_text': peptide, 'allele': allele, 'length': '15' } response = requests.post(url, data=params) # Parse response... return results
Goal: Define population-representative HLA allele sets for broad epitope coverage analysis.
Approach: Use curated lists of the most frequent HLA-A and HLA-B alleles covering ~85% of the Caucasian population.
python# Most common HLA-A alleles (cover ~85% of population) COMMON_HLA_A = [ 'HLA-A*02:01', # ~30% Caucasian 'HLA-A*01:01', # ~15% 'HLA-A*03:01', # ~13% 'HLA-A*24:02', # ~10% 'HLA-A*11:01', # ~8% ] # Most common HLA-B alleles COMMON_HLA_B = [ 'HLA-B*07:02', 'HLA-B*08:01', 'HLA-B*44:02', 'HLA-B*15:01', 'HLA-B*35:01', ] def get_patient_alleles(hla_typing_result): '''Parse HLA typing result Patients have 2 alleles per locus (one from each parent) Format: HLA-A*02:01, HLA-A*24:02 ''' # Typically 6 alleles: 2 HLA-A, 2 HLA-B, 2 HLA-C return hla_typing_result.split(',')
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-03 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-06 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-09 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-14 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-15 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-21 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-19 | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-13 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-04 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-12 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-18 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-22 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-02 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-10 | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-16 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-08 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-01 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-07 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-05 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-11 | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-20 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-17 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +14 percentage points is the difference between those two pass rates over the 22 comparable cases.
The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.
Other measured skills in the registry, with their headline benchmark lift.