BB tooluniverse-literature-deep-research
Conduct comprehensive literature research with target disambiguation, evidence grading, and structured theme extraction. Creates a detailed report with mandatory completeness checklist, biological model synthesis, and testable hypotheses. For biological targets, resolves official IDs (Ensembl/UniProt), synonyms, naming collisions, and gathers expression/pathway context before literature search. Default deliverable is a report file; for single factoid questions, uses a fast verification mode and may include an inline answer. Use when users need thorough literature reviews, target profiles, or to verify specific claims from the literature.
Conduct comprehensive literature research with target disambiguation, evidence grading, and structured theme extraction.
As a process B 67/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, execution cost
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 ≈ 8022 tokens (recommended < 5000); move details to references/ - note
edit-residuethe text marks something as outdated (lines 314): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 67/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Execution cost. Instruction body is 8022 tokens: crowds the task out of the window
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 134 steps
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 12 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
- +4Description does not say when NOT to use the skill (false activations)
- -220 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 645: enough signal without eating the budget
- +4Structure: 57 headings
- +3Step-by-step instructions: 134 items
- +3Output format is stated explicitly
- +4Has examples (30 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.