CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-clinical-data-integration

End-to-end drug safety review integrating FDA labels, FAERS adverse event reports, PRR/ROR disproportionality, pharmacogenomic biomarkers, clinical trial data, and published literature. Use for regulatory drug safety reviews, comprehensive pharmacovigilance reports, label-vs-real-world AE comparison, and clinical decision support for drug safety.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

A highly actionable, well-sequenced workflow skill whose tool-specific details (parameter quirks, output shapes, thresholds, fallbacks) are excellent. Its weaknesses are inlined reference material instead of progressive disclosure into separate files, and re-explanation of standard pharmacovigilance concepts Claude already knows.

Suggestions

Move the FAERS signal interpretation table, signal-credibility checklist, and evidence-grading tiers into a references/ file (e.g., FAERS-INTERPRETATION.md) linked one level deep from the relevant phase, keeping SKILL.md as an overview.

Trim or compress sections that re-teach known concepts — the channeling/notoriety/protopathic bias list and the standard PRR thresholds — down to the tool-specific deltas (which parameters differ, which values the tools return).

Consider offloading the Limitations and Edge Cases sections to a reference file and replacing them with a short pointer, reducing the always-loaded token footprint without losing fallback guidance.

DimensionReasoningScore

Conciseness

Mostly efficient — tool parameter quirks, output shapes, and thresholds are novel and earn their tokens — but several sections re-teach concepts Claude already knows: the 'Signal ≠ Causation' bias list (channeling/notoriety/protopathic), the PRR threshold table reflecting standard Evans criteria, and the ICD-10 vs SNOMED data-harmonization paragraph, matching the 'mostly efficient but includes some unnecessary explanation' anchor.

3 / 5

Actionability

Fully concrete, execution-ready guidance: exact tool names, parameter quirks flagged explicitly ('medicinalproduct', NOT 'drug_name'; 'setid', NOT 'set_id'; 'limit=1000'), output schemas, expected error shapes ('NOT_FOUND... is normal'), and specific signal criteria (PRR >= 2.0, lower CI > 1.0, N >= 3), covering the common cases per the instruction-skill scoring note.

5 / 5

Workflow Clarity

Phases 0-6 are clearly sequenced, each with objective, tools, and numbered workflow, and include explicit checkpoints and error recovery: a 5-point signal-credibility checklist, T1-T4 evidence grading, edge-case fallbacks (new drug, OTC, combination products), and interpretation guidance for ambiguous results (MedDRA term-level mismatch, NOT_FOUND responses).

5 / 5

Progressive Disclosure

The section structure is good, but there are no bundle files at all — all ~290 lines are inlined in SKILL.md, including content that naturally belongs in one-level-deep references (the FAERS interpretation guide, edge cases, and limitations), matching the 'some structure but content that should be separate is inline' anchor.

3 / 5

Total

16

/

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 with an explicit what-plus-when structure, concrete named data sources, and natural trigger phrases in third person. Its only weaknesses are limited action-verb variety, a missing common synonym ('side effects'), and minor overlap risk with the sibling pharmacovigilance skill.

DimensionReasoningScore

Specificity

Enumerates six concrete data components ('FDA labels, FAERS adverse event reports, PRR/ROR disproportionality, pharmacogenomic biomarkers, clinical trial data, and published literature') with comprehensive domain coverage, but the action verbs are limited to 'review' and 'integrating', placing it between the 4 and 5 anchors.

4 / 5

Completeness

Explicitly answers both questions: the 'what' is 'End-to-end drug safety review integrating FDA labels, FAERS adverse event reports, PRR/ROR disproportionality...' and the 'when' is 'Use for regulatory drug safety reviews, comprehensive pharmacovigilance reports, label-vs-real-world AE comparison, and clinical decision support for drug safety' — matching the top anchor exactly.

5 / 5

Trigger Term Quality

Good natural-term coverage — 'drug safety review', 'pharmacovigilance reports', 'adverse event', 'label-vs-real-world AE comparison', 'clinical decision support' — with the pharmacovigilance synonym present, but common user phrasings such as 'side effects' are missing, so it does not fully reach the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The regulatory-grade multi-source integration niche is clear and mostly distinct, but 'comprehensive pharmacovigilance reports' overlaps with the sibling tooluniverse-pharmacovigilance skill, and the description does not itself disambiguate (disambiguation lives only in the body), giving minor overlap risk with a closely related skill.

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

plugin/skills/tooluniverse-clinical-data-integration/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.