CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-hla-immunogenomics

HLA gene-family analysis and MHC-peptide binding for transplant compatibility, vaccine epitope coverage, and cancer immunotherapy. Uses IMGT (HLA polymorphism), IEDB (epitope-MHC binding), UniProt (annotation), DGIdb (druggability). Use for HLA typing/imputation review, vaccine HLA coverage, and immunotherapy prediction biomarkers (HLA-LOH, neoantigen presentation).

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is tooluniverse-hla-immunogenomics in mims-harvard/ToolUniverse

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced pipeline skill: exact tool signatures, verified live example calls with real outputs, format gotchas, and explicit fallbacks for failure modes. Its main weaknesses are moderate inline padding of textbook HLA biology and a monolithic structure that inlines reference-grade detail (tool APIs, affinity thresholds, drug associations) instead of splitting it into separate files.

Suggestions

Split per-database tool reference detail (e.g., IMGT/IPD, IEDB, HLA Ligand Atlas/MHC Motif Atlas tool signatures and verified examples) into references/ files, keeping SKILL.md as the workflow overview with clearly signaled one-level-deep links.

Trim content Claude already knows — the background biology in the Reasoning Strategy section and the 'Well-known HLA-drug associations' list — to the one-line reminders needed for lookup orientation (e.g., 'verify HLA-B*57:01/abacavir-type associations via DGIdb/PubMed, do not rely on memory').

Add an explicit cross-source validation checkpoint in Phase 6 (e.g., confirm allele nomenclature against IPD allele_history and reconcile IEDB binding evidence against Ligand Atlas elution data before reporting) to close the workflow validation gap.

DimensionReasoningScore

Conciseness

The bulk is lean operational detail Claude cannot know: exact parameter names and formats ('Input: name (e.g. "A*02:01" -- NOT query, a common mistake)', 'hla_class must be the literal string "HLA-I"'), performance guidance ('can take 60+ seconds or time out'), and verified live example calls. Minor over-explanation remains: the Reasoning Strategy paragraph and the 'Well-known HLA-drug associations' list restate biology (HLA-B27/ankylosing spondylitis, abacavir/HLA-B*57:01) Claude already knows. Not 3 because padding is limited; not 5 because those sections could be trimmed.

4 / 5

Actionability

Fully executable guidance: every tool lists exact inputs and outputs, two sections provide copy-paste-ready verified live examples with real returned values ('IPD_search_hla_alleles({"name": "A*02:01"})' returning accessions 'HLA00005/HLA00006', 'MHCMotifAtlas_get_allele_ligands({"allele": "A0201"})' returning 'ALFTKVLENV'), plus format pitfalls and explicit IC50 thresholds covering common cases.

5 / 5

Workflow Clarity

Phases 0-6 are clearly sequenced, each with an objective, tool inventory, and numbered workflow, plus a fallback section providing error-recovery loops ('If allele not found: Check nomenclature...', 'BVBRC empty results: Try broader organism name') and an early species/resolution checkpoint. Not 5 because there is no explicit cross-source validation step (e.g., confirming an IEDB result against IMGT annotation) in the report-synthesis phase; not 3 because checkpoints and feedback loops are present and concrete. This is a read-only lookup skill, so the destructive/batch validation cap does not apply.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the ~250-line body inlines per-tool API reference detail, IC50 interpretation tables, drug-association lists, and nomenclature primers that, at this length, belong in separate reference files with the SKILL.md acting as an overview. Well-structured with clear headers, so above 2, but the monolithic single-file layout with zero external references fits anchor 3 ('content that should be separate is inline') better than 4.

3 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly and concisely states what the skill does, which databases it uses, and when to use it, with natural domain trigger terms and third-person voice. Minor gaps: it under-represents the ligand-atlas/immunopeptidomics and literature-lookup capabilities documented in the body, and could add a few more common synonyms.

DimensionReasoningScore

Specificity

Lists several specific actions ('HLA gene-family analysis and MHC-peptide binding') with concrete application areas ('transplant compatibility, vaccine epitope coverage, and cancer immunotherapy') and four named data sources with their roles. Not 5 because it covers roughly two core actions and omits capabilities present in the body (immunopeptidomics/ligand atlas, PubMed literature lookup); not 3 because coverage goes well beyond 1-2 generic actions.

4 / 5

Completeness

Explicitly answers both questions: 'what' ('HLA gene-family analysis and MHC-peptide binding for transplant compatibility, vaccine epitope coverage, and cancer immunotherapy... Uses IMGT, IEDB, UniProt, DGIdb') and 'when' ('Use for HLA typing/imputation review, vaccine HLA coverage, and immunotherapy prediction biomarkers (HLA-LOH, neoantigen presentation)') with concrete trigger phrases. Third-person voice throughout, matching the anchor-5 good example structure.

5 / 5

Trigger Term Quality

Includes natural domain phrases users would say: 'HLA typing', 'vaccine HLA coverage', 'immunotherapy', 'HLA-LOH', 'neoantigen presentation', 'transplant compatibility'. A few common variations are missing (e.g., 'antigen presentation', 'epitope', 'graft/organ matching'), keeping it below the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (HLA/immunogenomics) with distinct triggers and named databases (IMGT, IEDB, UniProt, DGIdb) plus specific biomarkers (HLA-LOH, neoantigen presentation). Minimal conflict risk — these terms would not naturally route to a generic gene-lookup or document skill.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mims-harvard/ToolUniverse

Path

plugins/tooluniverse/skills/tooluniverse-hla-immunogenomics/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.