CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-precision-medicine-stratification

Patient stratification for precision medicine — integrate genomic, clinical, and therapeutic data to split patients into responder/non-responder groups, risk tiers, or treatment-decision groups. Use for stratification-by-biomarker, treatment-selection logic, and personalized therapeutic strategy reports per patient subgroup.

Quality

84%

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 well-structured, information-dense skill body with a clear 9-phase workflow, concrete tool-parameter guidance, and good routing logic. The main defect is progressive disclosure: the body is built around five reference files that are absent from the bundle, and some reference-bound content (tool parameter notes) is duplicated inline.

Suggestions

Ship the five referenced files (TOOLS_REFERENCE.md, SCORING_REFERENCE.md, REPORT_TEMPLATE.md, EXAMPLES.md, QUICK_START.md) in the skill's references/ directory so the body's navigation actually resolves.

Move the 'Critical Tool Parameter Notes' section fully into TOOLS_REFERENCE.md and keep only a one-line pointer inline, instead of duplicating it in both places.

Add an explicit validation checkpoint in Phase 9 (e.g., 'verify report against REPORT_TEMPLATE.md completeness requirements before delivering') to close the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is dense and token-efficient — tables for disease classification and risk tiers, terse per-phase tool lists, and it assumes Claude's domain knowledge rather than explaining basics. Minor trimming opportunities exist ('Reasoning Before Searching' prose and the 7-item 'KEY PRINCIPLES' list partially restate later content). Not 5: a few sections could be tightened without losing clarity.

4 / 5

Actionability

Highly concrete for an instruction-only skill: exact tool names with parameter gotchas ('param is `query` (NOT `q`)', "REQUIRES `species='homo_sapiens'`", '`limit=1000`', 'STRING (space-separated), not array') and specific Enrichr library names. Not 5: no example tool-call invocations or output snippets inline, and key scoring details are deferred to reference files.

4 / 5

Workflow Clarity

Nine phases are clearly sequenced, with explicit disease-type routing and a pre-routing checkpoint ('Route to the correct Phase 3 path BEFORE running Phase 2 tools') plus graceful degradation ('gnomAD: May return "Service overloaded" - skip gracefully'). Not 5: validation checkpoints are mostly implicit — report completeness verification is only deferred to REPORT_TEMPLATE.md rather than stated as an explicit step.

4 / 5

Progressive Disclosure

Sections are well organized with clearly signaled, one-level-deep references ('Reference files (same directory)'), but none of the five referenced files (TOOLS_REFERENCE.md, SCORING_REFERENCE.md, REPORT_TEMPLATE.md, EXAMPLES.md, QUICK_START.md) exist in the bundle, so the navigation is broken. Additionally, the inlined 'Critical Tool Parameter Notes' section duplicates content the body itself says belongs in TOOLS_REFERENCE.md. Not 4: broken reference targets and inline content that should live in the reference files keep this at 'some structure but could be better organized'.

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: third-person, concise, concrete about what the skill does, with an explicit 'Use for' trigger clause. Its only weaknesses are slightly incomplete natural-synonym coverage and unaddressed overlap with sibling precision-medicine skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'integrate genomic, clinical, and therapeutic data', 'split patients into responder/non-responder groups, risk tiers, or treatment-decision groups', and produce 'personalized therapeutic strategy reports per patient subgroup' — with comprehensive coverage of the skill's capabilities. Not 4: coverage goes beyond minor gaps; each named action is specific rather than generic.

5 / 5

Completeness

Clearly answers both: the 'what' (integrate multi-modal data, split patients into defined group types, produce subgroup reports) and an explicit 'Use for stratification-by-biomarker, treatment-selection logic, and personalized therapeutic strategy reports per patient subgroup' trigger clause. Both are present with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage: 'patient stratification', 'stratification-by-biomarker', 'treatment-selection logic', 'risk tiers', 'personalized therapeutic strategy'. A few natural phrases users would say are missing (e.g., 'prognosis', 'risk prediction', 'who responds to treatment'). Not 5: the synonym coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear niche (biomarker-driven patient stratification) with mostly distinct triggers, but 'responder/non-responder groups' overlaps the sibling immunotherapy-response-prediction skill and no exclusion boundary is stated in the description. Not 5: minor overlap risk with closely related skills in the same family.

4 / 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

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