CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-immunotherapy-response-prediction

Predict patient response to immune checkpoint inhibitors (ICIs) by integrating tumor mutational burden (TMB), microsatellite instability (MSI), PD-L1 expression, HLA status, and immune-related gene expression. Outputs ICI Response Score with drug-specific recommendations and resistance-risk assessment. Use for melanoma/NSCLC/RCC immunotherapy decision support.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./plugin/skills/tooluniverse-immunotherapy-response-prediction/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 dense, actionable workflow with exact tool calls and quantitative scoring, weakened by broken bundle references and some re-taught background biology. The core defect is that four linked files the workflow repeatedly depends on do not exist in the skill directory.

Suggestions

Ship the four referenced bundle files (SCORING_TABLES.md, INPUT_REFERENCE.md, REPORT_TEMPLATE.md, TOOLS_REFERENCE.md) or inline their essential content — the cancer-specific thresholds, ORR baselines, and verified tool parameters the workflow depends on are currently unreachable.

Trim the 'Reasoning Before Searching' section to the scoring-relevant caveats (e.g., RCC responding despite low TMB) and remove the duplicate resistance-gene listing and the trailing URL list to save tokens.

Add parameters for tools currently called without them (iedb_search_epitopes, civic_search_evidence_items, and the Phase 6 gene-expression queries) so every tool invocation is fully specified.

DimensionReasoningScore

Conciseness

The 'Reasoning Before Searching' section re-teaches well-known oncology biology ('Caused by defective DNA mismatch repair (MMR)', 'The direct target of pembrolizumab'), resistance genes are listed twice (KEY PRINCIPLES #6 and Phase 7), and the trailing database URL list adds little — the document could be tightened despite being mostly dense and actionable.

3 / 5

Actionability

Highly concrete guidance: exact tool calls with parameters (e.g., "fda_pharmacogenomic_biomarkers(drug_name='pembrolizumab')", "MyGene_query_genes: use query (NOT q)"), explicit point values (STK11 -10, POLE +10), and a fully specified score formula with floor and cap. Minor gaps: several tools (iedb_search_epitopes, civic_search_evidence_items, Phase 6 expression queries) are invoked without parameters, and the promised parameter reference file does not exist.

4 / 5

Workflow Clarity

Eleven clearly sequenced phases with explicit checkpoints ('LOOK UP DON'T GUESS', 'BEFORE calling ANY tool, verify parameters', flag unknowns instead of defaulting to moderate) and confidence tiers tied to biomarker completeness. No error-recovery or feedback loops for failed or empty tool calls, keeping it below a 5; no destructive or batch operations apply the cap.

4 / 5

Progressive Disclosure

The body itself is well organized with one-level, clearly signaled references, but all four referenced files (INPUT_REFERENCE.md, SCORING_TABLES.md, REPORT_TEMPLATE.md, TOOLS_REFERENCE.md) are missing from the bundle, so the cancer-specific thresholds, ORR baselines, report template, and tool-parameter tables the workflow depends on are unreachable.

3 / 5

Total

14

/

20

Passed

Description

83%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: third-person voice, concrete and specific about inputs, outputs, and scope, with an explicit 'Use for' clause. The main gaps are missing drug-name triggers and plain-language synonyms that would broaden natural-language matching.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Predict patient response to immune checkpoint inhibitors (ICIs) by integrating tumor mutational burden (TMB), microsatellite instability (MSI), PD-L1 expression, HLA status' and 'Outputs ICI Response Score with drug-specific recommendations and resistance-risk assessment' — covering inputs, outputs, and downstream recommendations comprehensively.

5 / 5

Completeness

Both 'what' (multi-biomarker integration producing an ICI Response Score) and 'when' ('Use for melanoma/NSCLC/RCC immunotherapy decision support') are explicit, but the 'when' clause names contexts rather than concrete trigger phrases a user would actually say.

4 / 5

Trigger Term Quality

Natural domain terms like 'immunotherapy', 'PD-L1', 'TMB', 'melanoma', and 'NSCLC' are present, but common user phrasings such as specific drug names (pembrolizumab, nivolumab) or plain-language synonyms ('lung cancer', 'kidney cancer') are missing.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear clinical niche (ICI response prediction) with named biomarkers, a named output score, and specific cancer types, so overlap with other skills is minimal.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 7 missing

Warning

Total

15

/

16

Passed

Repository

mims-harvard/ToolUniverse

Path

plugin/skills/tooluniverse-immunotherapy-response-prediction/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.