CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-immunology

Immunology research workflows: antibody-antigen interactions, T/B cell repertoire, MHC/HLA binding prediction, autoimmune disease genetics, vaccine epitope mapping. Uses IEDB, IMGT, SAbDab, UniProt. Use for adaptive immunity questions, immune response analysis, antibody/TCR/BCR characterization, immunogenicity prediction, and immune-pathway-to-disease mapping.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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

SKILL.md
Quality
Evals
Security

Quality

Content

71%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-organized tool reference whose tool tables and parameter gotchas are its core strength. Its weaknesses are the ~80 lines of inlined API reference that belong in a separate file, textbook immunology restated in the reasoning frameworks, and a dangling numbered reference in the single-cell workflow.

Suggestions

Move the Tool Reference tables and Parameter Gotchas into a references/ file (e.g. references/tool_reference.md), keeping SKILL.md as an overview with clear one-level-deep pointers to it.

Trim the Reasoning Frameworks to the decision guidance only (which arm of immunity → which databases/tools) and drop textbook restatements like innate-vs-adaptive timing and the full complement cascade description that Claude already knows.

Remove the dangling "(1)" and "(2)" markers in the single-cell dual receptor workflow, which reference numbered options that do not exist in this document.

DimensionReasoningScore

Conciseness

The tool tables, gotchas, and workflows are dense and high-value, but the Reasoning Frameworks sections restate textbook immunology Claude already knows ("Innate is fast (hours) and antigen-nonspecific; adaptive is slow (days)", the full three-pathway complement cascade description, isotype switching mechanics). Mostly efficient with several passages that could be tightened to just the decision guidance.

3 / 5

Actionability

Exact tool names with exact parameters ("stId", "targetName", "gene_names" as list), concrete example values ("H00080", "Q9NZQ7", "9606", "STAT4 IRF5"), and a wrong/correct gotcha table give copy-paste-ready guidance for every tool. For a tool-dispatch skill, this is fully executable instruction.

5 / 5

Workflow Clarity

Four workflows are clearly sequenced as tool chains (e.g. "Orphanet_search_diseases → Orphanet_get_genes + Orphanet_get_phenotypes → gwas_search_associations → …"), and partial checkpoints exist (evidence grading tiers, "validate with orthogonal methods" on TIMER2). No explicit validate-and-retry loops, so anchor 4 rather than 5; the workflows are read-only lookups, so the destructive-operation cap does not apply.

4 / 5

Progressive Disclosure

The body is well-sectioned with clear headers and tables, but the full Tool Reference and Parameter Gotchas (~80 lines) are inlined in SKILL.md where a separate reference file belongs, and no bundle files exist to offload them. Anchor 3: some structure, but content that should be separate is inline and there are no references to signal.

3 / 5

Total

15

/

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: concrete domain coverage, named databases, and an explicit multi-phrase "Use for" trigger clause in third-person voice. The only weakness is that capabilities are stated as noun-phrase domains rather than explicit action verbs.

DimensionReasoningScore

Specificity

Lists five concrete workflow areas ("MHC/HLA binding prediction", "vaccine epitope mapping", "autoimmune disease genetics") plus named databases ("Uses IEDB, IMGT, SAbDab, UniProt"), but the workflows are noun phrases without action verbs, so coverage is comprehensive with a minor gap rather than fully verb-driven like the anchor-5 example.

4 / 5

Completeness

Explicitly answers both "what" (five named workflow categories plus the databases used) and "when" ("Use for" followed by five concrete trigger phrases), matching the anchor-5 example. Third-person voice is maintained throughout; no first/second person to penalize.

5 / 5

Trigger Term Quality

"Use for adaptive immunity questions, immune response analysis, antibody/TCR/BCR characterization, immunogenicity prediction" are phrases a user would naturally say, but common variations like "immune system", "infection", or "allergy" are missing — good coverage, not comprehensive.

4 / 5

Distinctiveness Conflict Risk

"Immunology research workflows" combined with domain-specific databases (IEDB, IMGT, SAbDab) carves a clear niche with distinct trigger phrases and minimal overlap risk with adjacent biomedical skills.

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-immunology/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.