CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-clinical-guidelines

Search and retrieve clinical practice guidelines from 12+ authoritative sources — NICE, WHO, NCCN, AHA, ADA, SIGN, USPSTF, IDSA, NIH consensus, ESMO/ESC/EASL European societies, and US specialty associations. Use for evidence-graded treatment recommendations, dosing protocols, screening guidance, and authoritative-source-prioritized clinical guidance (NICE/WHO ranked above society guidelines).

Quality

82%

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

The canonical home for this skill is tooluniverse-clinical-guidelines in mims-harvard/ToolUniverse

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.

The ToolUniverse-specific core is excellent — precise parameter quirks, return formats, gotchas, and fallback loops that could only come from live verification. However, the skill is bloated by generic clinical-reasoning material Claude already knows, and a ~300-line monolith with no reference files wastes the progressive-disclosure structure the format supports.

Suggestions

Move the "Clinical MCQ Reasoning Framework" and "Diagnostic Test Selection Reasoning" sections into separate reference files (e.g., references/mcq-reasoning.md, references/diagnostic-reasoning.md) and keep only a one-line pointer plus the trigger conditions in SKILL.md, cutting the body by roughly a third.

Delete or compress explanations of concepts Claude already knows — SnNOut/SpPIn, sensitivity vs specificity basics, pre-test probability, likelihood ratios, Brown-Séquard anatomy, Holliday-Segar fluids — retaining only the tool-specific application of those concepts.

Add one or two worked example sequences showing the parallel Step-1 searches with actual parameter values (e.g., NICE_Clinical_Guidelines_Search(query='heart failure guideline', limit=10) alongside TRIP and EuropePMC calls) to make the opening workflow as executable as the CPIC section already is.

DimensionReasoningScore

Conciseness

The tool-workflow sections are dense and earn their tokens, but roughly a third of the body restates clinical knowledge Claude already has — SnNOut/SpPIn mnemonics, pre-test probability, likelihood ratios, Brown-Séquard lesion anatomy, Holliday-Segar fluids, TLICS scoring — plus a ~65-line "Clinical MCQ Reasoning Framework" only tangentially related to guideline retrieval. This fits "mostly efficient but includes some unnecessary explanation or could be tightened"; not 2 because the padding is terse reference bullets rather than padded prose and the tool-specific material is genuinely non-obvious.

3 / 5

Actionability

Guidance is copy-paste ready throughout: exact tool names with required parameters ("`SIGN_search_guidelines` — `query` (NOT `q`)"), literal example calls ("CPIC_get_gene_info(genesymbol='CYP2D6')"), PostgREST syntax ("genesymbol='eq.CYP2D6'"), return-shape parsing ("r.get('data', [])"), per-failure fallbacks, and a synthesis template. As an instruction-only skill, the specific examples cover the common cases, matching the anchor-5 description; not 4 because there are no real gaps in executability of the guidance given.

5 / 5

Workflow Clarity

The search strategy is clearly sequenced (start narrow with parallel calls → minimum 3 sources → full-text retrieval) with explicit error-recovery feedback loops ("NICE returns empty -> try TRIP or EuropePMC", "TRIP returns 403/gated PDFs -> note limited access, try alternative sources") and verification habits (check publication date, check returned `status` field). Not 5 because the checkpoints are scattered across separate sections rather than woven into one workflow, and some verification is implicit; not 3 because explicit fallback loops and checklists are present.

4 / 5

Progressive Disclosure

There are no bundle files at all — the entire ~305-line skill is inline. Section headers and tables give it real structure, but the tool catalog, the diagnostic-test selection reasoning, and the MCQ reasoning framework each clearly belong in separate reference files, matching the anchor-3 pattern of "content that should be separate is inline". Not 2 because the in-page organization and navigation via headers is good; not 4 because at this length the lack of any file split is a real structural gap, not a minor one.

3 / 5

Total

15

/

20

Passed

Description

83%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, concrete about both capability and sources, with an explicit "Use for" trigger clause covering the main use cases. The only weaknesses are minor — slightly thin action verbs relative to what the skill actually does and a few missing natural synonyms.

DimensionReasoningScore

Specificity

"Search and retrieve clinical practice guidelines from 12+ authoritative sources" names two concrete actions and enumerates the sources exhaustively (NICE, WHO, NCCN, AHA, ADA, SIGN, USPSTF, IDSA, ESMO/ESC/EASL), matching the "several specific actions; minor gaps" anchor. Not 5 because the action verbs stop at search/retrieve while the skill body also covers full-text retrieval and synthesis, which the description omits.

4 / 5

Completeness

Explicitly answers both questions: the "what" is "Search and retrieve clinical practice guidelines from 12+ authoritative sources" and the "when" is a concrete "Use for" clause listing evidence-graded treatment recommendations, dosing protocols, and screening guidance. This matches the anchor-5 example structure (what + "Use when..." with concrete trigger phrases) exactly.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — "clinical practice guidelines", "treatment recommendations", "dosing protocols", "screening guidance" — plus a dozen recognizable org names, giving good keyword coverage. Not 5 because common variations like "standard of care", "best practice", or "screening guidelines" are absent; not 3 since coverage clearly exceeds "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

The clinical-guideline niche with named bodies (NICE/WHO ranked above society guidelines) is clearly distinguishable, fitting "mostly distinct; minor overlap risk". Not 5 because triggers like "dosing protocols" and "treatment recommendations" could also plausibly fire a drug-information or general clinical-decision skill; not 3 since the org-specific framing keeps overlap minor.

4 / 5

Total

17

/

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

plugins/tooluniverse/skills/tooluniverse-clinical-guidelines/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.