CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-pharmacovigilance

Drug safety and adverse event analysis — FAERS spontaneous-report mining, FDA black-box warnings, signal detection (PRR, ROR, IC), risk factors by demographic/comorbidity, label change tracking, and SIDER curated label-derived side-effect frequencies. Use for post-market safety surveillance, AE signal investigation, drug-AE association strength scoring, "what side effects does drug X have" questions, and pharmacovigilance reports.

Quality

83%

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-pharmacovigilance in mims-harvard/ToolUniverse

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 body delivers excellent tool-specific, non-obvious guidance (exact parameters, MedDRA spellings, formulas, thresholds, fallbacks, data-quality gotchas) in a clear phase sequence, but it is padded with textbook clinical-reasoning exposition and defers critical detail to four referenced files that are not present in the bundle, breaking both actionability and navigation at the mandatory report/checklist steps.

Suggestions

Ship the referenced bundle files (SIGNAL_DETECTION.md, REPORT_TEMPLATES.md, CHECKLIST.md, TOOLS_REFERENCE.md) alongside SKILL.md, or inline their essential content — the mandatory Report-First step and completeness checklist currently point to files that do not exist.

Compress the Clinical Reasoning Framework to the tool-specific 'How to apply this' guidance and move the textbook exposition (Naranjo questions, Type A/B definitions, on-target/off-target basics) into a reference file, cutting roughly 100 lines.

Fix the duplicate 'Reasoning Strategy 5' numbering (Rechallenge and Disproportionality Reasoning are both labeled 5) so the strategy sequence stays navigable.

DimensionReasoningScore

Conciseness

The body is mostly efficient — the tool-parameter table, MedDRA spelling table, PRR formula, and SIDER frequency semantics are exactly the non-obvious knowledge Claude lacks — but the ~100-line 'Clinical Reasoning Framework' restates textbook concepts Claude already knows (Naranjo algorithm, Type A/B classification, on-target/off-target basics, dechallenge/rechallenge definitions) before each 'How to apply this' section. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is not level 4 because the concept exposition is substantial rather than minor, and not level 2 because the tool-specific content genuinely earns its place.

3 / 5

Actionability

Guidance is largely executable: exact tool calls with parameter names ('FAERS_count_reactions_by_drug_event(drug_name=..., limit=50)'), a defined PRR formula with cell meanings, signal thresholds (PRR > 2.0, case count >= 3), a signal-score formula with severity weights, fallback chains, and a SIDER data-quality gotcha with a live example. It falls short of level 5 because the mandatory Report-First step requires report 'section headers' and the PRR calculation details that live in REPORT_TEMPLATES.md and SIGNAL_DETECTION.md — files not present in the skill directory — leaving key details missing.

4 / 5

Workflow Clarity

The Phase 0-7 sequence is clearly laid out with numbered steps per phase, explicit signal thresholds as checkpoints, and a built-in feedback loop ('A signal not predicted mechanistically warrants additional scrutiny'). It is not level 5 because the phase-by-phase verification checklist is deferred to a missing CHECKLIST.md file and there is a duplicate 'Reasoning Strategy 5' heading (Rechallenge and Disproportionality both numbered 5), leaving minor validation and organization gaps.

4 / 5

Progressive Disclosure

References are clearly signaled and one level deep ('See [SIGNAL_DETECTION.md](SIGNAL_DETECTION.md)', '[REPORT_TEMPLATES.md](REPORT_TEMPLATES.md)', '[CHECKLIST.md](CHECKLIST.md)', '[TOOLS_REFERENCE.md](TOOLS_REFERENCE.md)'), but none of these files exist in the skill directory — there is no references/ directory and no sibling files — so the disclosure structure is broken at exactly the points where the most important detail (report structure, checklist, formulas) is deferred. The body is also ~350 lines when the clinical-reasoning exposition belongs in a reference file; this fits 'some structure but could be better organized' rather than level 4, whose 'minor organization gaps' does not cover missing referenced files.

3 / 5

Total

14

/

20

Passed

Description

96%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: comprehensive, specific capability list paired with an explicit 'Use for...' clause covering concrete trigger scenarios, including a natural user-question phrasing. The only weakness is mild overlap risk with general drug-information skills on the generic 'side effects' query.

DimensionReasoningScore

Specificity

The description enumerates six concrete capabilities with named methods — 'FAERS spontaneous-report mining, signal detection (PRR, ROR, IC), risk factors by demographic/comorbidity, label change tracking, and SIDER curated label-derived side-effect frequencies' — matching the comprehensive-coverage anchor; there are no minor gaps in capability coverage, so it is not the level-4 anchor.

5 / 5

Completeness

It explicitly answers both questions: 'what' is the concrete capability list, and 'when' is the explicit 'Use for post-market safety surveillance, AE signal investigation, drug-AE association strength scoring... and pharmacovigilance reports' clause with concrete trigger phrases. Both what and when are present and explicit, matching the level-5 anchor; the level-4 anchor ('when' could be more specific) does not apply.

5 / 5

Trigger Term Quality

Natural user terms are comprehensively covered with synonyms: 'drug safety', 'adverse event', 'side effects', 'safety surveillance', 'pharmacovigilance', plus a literal user-question trigger ('"what side effects does drug X have" questions'). Because both lay phrasing and domain jargon synonyms are present, it fits the level-5 anchor rather than the 'a few natural terms missing' level-4 anchor.

5 / 5

Distinctiveness Conflict Risk

The pharmacovigilance niche is distinct with specialized triggers (FAERS, PRR, signal detection), but the quoted '"what side effects does drug X have" questions' is a general drug-lookup question that a sibling drug-information skill could also claim — minor overlap risk with closely related skills, matching the level-4 anchor rather than the 'minimal conflict risk' level-5 anchor.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 4 missing

Warning

Total

15

/

16

Passed

Repository

mims-harvard/ToolUniverse

Path

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