tooluniverse-infectious-disease

Rapid pathogen characterization and drug repurposing for outbreaks. Combines pathogen genomics (NCBI, BVBRC), host immune response (IEDB), drug-target databases (ChEMBL, DGIdb), and literature surveillance (PubMed/EuropePMC). Use for emerging-pathogen profiling, antiviral candidate identification, and outbreak intelligence reporting.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugin/skills/tooluniverse-infectious-disease/SKILL.md

Quality

Content

55%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-structured outbreak-response workflow with clear sequencing and validation, but it is held back by missing referenced bundle files (progressive disclosure) and procedure-level rather than executable phase guidance (actionability).

Suggestions

Create the referenced bundle files (TOOLS_REFERENCE.md, phase_details.md, report_template.md, CHECKLIST.md, EXAMPLES.md) or remove the dangling References table so navigation is not broken.

Inline at least one concrete, executable code snippet per phase in SKILL.md rather than deferring all examples to phase_details.md, to lift actionability.

Collapse the duplicated completeness checklist into the workflow overview to remove repetition and tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Largely efficient and avoids explaining concepts Claude already knows, but the workflow overview ASCII tree plus per-phase summaries plus a duplicate completeness checklist introduce repetition that could be tightened.	2 / 3
Actionability	Names concrete tools and parameters (e.g. 'ChEMBL_search_targets', 'pref_name__contains') and a scoring rubric, but most phases give procedure-level direction rather than executable copy-paste code; actual examples are deferred to phase_details.md.	2 / 3
Workflow Clarity	Clear sequenced phases (0 through 6) with explicit validation checkpoints — tool-verification parameter corrections, pLDDT > 70 gating before docking, and a completeness checklist with feedback loops for the batch/report operations.	3 / 3
Progressive Disclosure	The body references five bundle files (TOOLS_REFERENCE.md, phase_details.md, report_template.md, CHECKLIST.md, EXAMPLES.md) in a References table, but none of these files exist in references/, scripts/, or assets/, so the signaled navigation points to missing content.	1 / 3
	Total	8 / 12 Passed

Description

85%

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, specific description with an explicit 'Use for' trigger clause and concrete data sources per capability. Trigger-term naturalness is slightly technical but the overall what/when coverage and niche distinctiveness are excellent.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('pathogen characterization', 'drug repurposing', 'outbreak intelligence reporting') and names specific data sources per capability, matching the level-3 anchor of multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (combines pathogen genomics, host immune response, drug-target databases, literature surveillance) and when ('Use for emerging-pathogen profiling, antiviral candidate identification, and outbreak intelligence reporting'), matching the level-3 anchor with an explicit 'Use for...' clause.	3 / 3
Trigger Term Quality	Includes natural phrases like 'drug repurposing' and 'emerging-pathogen profiling', but the trigger framing leans technical ('antiviral candidate identification', 'outbreak intelligence reporting') and misses common lay variations a user might actually say.	2 / 3
Distinctiveness Conflict Risk	A clear niche (infectious-disease outbreak intelligence with named bioinformatics databases) with distinct triggers unlikely to overlap with other skills, matching the level-3 clear-niche anchor.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 5 missing	Warning

	Total	15 / 16 Passed

Repository: mims-harvard/ToolUniverse
Path: plugin/skills/tooluniverse-infectious-disease/SKILL.md
Commit: 089eb8e

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

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.