BB tooluniverse-precision-medicine-stratification
Comprehensive patient stratification for precision medicine by integrating genomic, clinical, and therapeutic data. Given a disease/condition, genomic data (germline variants, somatic mutations, expression), and optional clinical parameters, performs multi-phase analysis across 9 phases covering disease disambiguation, genetic risk assessment, disease-specific molecular stratification, pharmacogenomic profiling, comorbidity/DDI risk, pathway analysis, clinical evidence and guideline mapping, clinical trial matching, and integrated outcome prediction. Generates a quantitative Precision Medicine Risk Score (0-100) with risk tier assignment (Low/Intermediate/High/Very High), treatment algorithm (1st/2nd/3rd line), pharmacogenomic guidance, clinical trial matches, and monitoring plan. Use when clinicians ask about patient risk stratification, treatment selection, prognosis prediction, or personalized therapeutic strategy across cancer, metabolic, cardiovascular, neurological, or rare diseases.
Comprehensive patient stratification for precision medicine by integrating genomic, clinical, and therapeutic data.
As a process B 75/100 · Nearly there — weak spots: execution cost, running it twice, progress reporting
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 11854 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 75/100
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Execution cost. Instruction body is 11854 tokens: crowds the task out of the window
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 68 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- low 17 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Description length 1004: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 72 headings
- +3Step-by-step instructions: 68 items
- +3Output format is stated explicitly
- +4Has examples (31 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.