CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-precision-oncology

Cancer treatment recommendations from molecular profile (mutations + cancer type + biomarkers) — FDA-approved + investigational therapies, resistance mechanisms, matching clinical trials, prognosis. Uses CIViC, ClinVar, OpenTargets, ClinicalTrials.gov. Use for tumor-board treatment recommendations, evidence-tiered actionability assessment, and FDA-precedent-driven therapy selection.

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

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 domain-rich, actionably written skill body with concrete tool parameters, mandatory verification checkpoints, and a phased workflow. Its two real weaknesses are inconsistent phase numbering between the overview and the detailed sections, and a References section pointing at files that are absent from the bundle (while the bundle's one script is orphaned).

Suggestions

Reconcile phase numbering: the Workflow Overview lists "Phase 5.5: Literature" and "Phase 6: Report Synthesis", but the Key Tools sections label "Phase 5.5: Safety & Pharmacogenomics" and "Phase 6: Literature" — renumber so overview and details match, and add a Phase 6 Report Synthesis section covering the report-first principle and output format.

Fix the reference bundle: TOOLS_REFERENCE.md, API_USAGE_PATTERNS.md, TREATMENT_ALGORITHMS.md, REPORT_TEMPLATE.md, EXAMPLES.md, and CHECKLIST.md are linked in the References section but do not exist in the bundle — either ship them in references/ or trim the list to files that exist; likewise reference or remove the orphaned scripts/gdsc_drug_response.py.

Move the cancer-type biomarker-to-drug mappings and resistance-mutation catalogs into TREATMENT_ALGORITHMS.md, keeping only the evidence-hierarchy logic and a few exemplar mappings inline to slim the overview and reduce stale-approval risk in SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense and specialized — biomarker-to-drug mappings, resistance frequencies ("C797S (10-25%), MET amp (15-20%)"), and parameter gotchas — knowledge Claude cannot reliably recall, so it earns its tokens rather than padding. Not 5 because the cancer-type drug-mapping blocks and resistance catalogs largely duplicate what TREATMENT_ALGORITHMS.md is supposed to hold, and could be trimmed from the overview.

4 / 5

Actionability

Highly concrete tool guidance: exact parameters with corrections ("`variant_id` (numeric, e.g., 4170)", "param: `condition`, NOT `disease`", "`ensemblId`, camelCase"), a runnable command ("python3 skills/tooluniverse-drug-drug-interaction/scripts/pharmacology_ref.py --type cyp_substrate --drug drugname"), and example query values ("molecular_profile='EGFR C797S'"). Not 5 because there is no complete end-to-end example tool call in the body — worked examples are delegated to EXAMPLES.md.

4 / 5

Workflow Clarity

A clear phase sequence (0→6) with per-phase tool assignments and an explicit hard checkpoint ("Phase 5.5: Safety & Pharmacogenomics (MANDATORY — do NOT skip)" / "You MUST call FAERS... before finalizing the report") plus a Phase 0 tool-verification table. Held below 5 by a numbering inconsistency: the Workflow Overview defines "Phase 5.5: Literature → Phase 6: Report Synthesis" while the detail sections label "Phase 5.5: Safety & Pharmacogenomics" and "Phase 6: Literature", and no detailed Report Synthesis section exists.

4 / 5

Progressive Disclosure

The References section is well-signaled and one level deep (TOOLS_REFERENCE.md, TREATMENT_ALGORITHMS.md, EXAMPLES.md, etc.), but none of those six files exist in the provided bundle — there is no references/ directory — so the navigation paths dangle. Additionally, the one bundle file present (scripts/gdsc_drug_response.py) is never referenced by the body. Structure matches the 4 anchor, but unverifiable/broken references push it to 3.

3 / 5

Total

15

/

20

Passed

Description

88%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: it states concrete capabilities in third person, names its data sources, and includes an explicit "Use for..." trigger clause tied to tumor-board use cases. The only weakness is moderately jargon-laden trigger phrasing ("evidence-tiered actionability", "FDA-precedent-driven") that some users would not naturally say.

DimensionReasoningScore

Specificity

Lists multiple concrete, comprehensive actions: "FDA-approved + investigational therapies, resistance mechanisms, matching clinical trials, prognosis" from "mutations + cancer type + biomarkers". Every capability is a specific deliverable, not abstract language, matching the comprehensive-coverage anchor exactly; the level below (4) would require minor gaps in coverage, which are not present.

5 / 5

Completeness

Explicitly answers both: the "what" ("Cancer treatment recommendations from molecular profile... resistance mechanisms, matching clinical trials, prognosis") and an explicit "when" clause ("Use for tumor-board treatment recommendations, evidence-tiered actionability assessment, and FDA-precedent-driven therapy selection") with concrete trigger scenarios. Matches the 5 anchor; a 4 would require the 'when' to be less explicit than the literal "Use for" phrasing present here.

5 / 5

Trigger Term Quality

Good natural-term coverage: "tumor-board treatment recommendations", "therapy selection", "clinical trials", "resistance", "prognosis" — phrases a clinician or researcher would actually say. Falls short of 5 because phrases like "evidence-tiered actionability assessment" and "FDA-precedent-driven" are skill jargon rather than user language, and common variations ("what drug for [mutation]", "targeted therapy options") are absent.

4 / 5

Distinctiveness Conflict Risk

A clear precision-oncology niche anchored by named databases ("Uses CIViC, ClinVar, OpenTargets, ClinicalTrials.gov") makes mistaken triggering unlikely. Not 5 because "cancer treatment recommendations" and "clinical trials" are broad enough to overlap with general drug-interaction or literature-search skills; the database citation is what keeps it mostly distinct rather than minimally at risk.

4 / 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: 6 missing

Warning

Total

15

/

16

Passed

Repository

mims-harvard/ToolUniverse

Path

plugin/skills/tooluniverse-precision-oncology/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.