BB tooluniverse-multiomic-disease-characterization
Comprehensive multi-omics disease characterization integrating genomics, transcriptomics, proteomics, pathway, and therapeutic layers for systems-level understanding. Produces a detailed multi-omics report with quantitative confidence scoring (0-100), cross-layer gene concordance analysis, biomarker candidates, therapeutic opportunities, and mechanistic hypotheses. Uses 80+ ToolUniverse tools across 8 analysis layers. Use when users ask about disease mechanisms, multi-omics analysis, systems biology of disease, biomarker discovery, or therapeutic target identification from a disease perspective.
Comprehensive multi-omics disease characterization integrating genomics, transcriptomics, proteomics, pathway, and therapeutic layers for systems-level…
As a process B 72/100 · Nearly there — weak spots: execution cost, 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 10087 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 72/100
- 0Progress reporting. Says nothing while it works
- 40Execution cost. Instruction body is 10087 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 60Steps. 312 steps, 5 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- low 18 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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 602: enough signal without eating the budget
- +4Structure: 71 headings
- +3Step-by-step instructions: 312 items
- +3Output format is stated explicitly
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.