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, and label change tracking. Use for post-market safety surveillance, AE signal investigation, drug-AE association strength scoring, and pharmacovigilance reports.

Quality

85%

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

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.

Highly actionable content with concrete tool calls, formulas, and parameter corrections, plus a well-sequenced multi-phase workflow. It is held back by verbose explanatory reasoning strategies covering concepts Claude already knows, a duplicate heading, and four referenced bundle files that do not exist.

Suggestions

Provide the missing referenced files (SIGNAL_DETECTION.md, REPORT_TEMPLATES.md, CHECKLIST.md, TOOLS_REFERENCE.md) or remove the links — broken references defeat progressive disclosure.

Condense or externalize the seven 'Reasoning Strategy' sections, which explain general pharmacology concepts Claude already knows; keep only the domain-specific 'How to apply this' framing.

Fix the duplicate 'Reasoning Strategy 5' heading (lines 80 and 88) — the second instance should be 'Reasoning Strategy 6' and subsequent numbering shifted.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but padded: seven 'Reasoning Strategy' sections explain general pharmacology concepts Claude already knows (Naranjo algorithm, on/off-target, timeline diagnostics), and the 'Reasoning Strategy 5' heading is duplicated (lines 80 and 88).	3 / 5
Actionability	Fully executable guidance — exact tool calls with corrected parameters (e.g. 'FAERS_count_reactions_by_drug_event(drug_name=..., limit=50)'), the PRR formula '(A/B)/(C/D)', signal thresholds, the signal score formula, severity weights, evidence tiers, and fallback chains.	5 / 5
Workflow Clarity	Clear Phase 0–7 sequencing with MANDATORY report-first and citation requirements plus mechanistic cross-checks; this is analysis/reporting (not destructive/batch) so no hard cap applies, but explicit validate-then-proceed feedback loops are thin.	4 / 5
Progressive Disclosure	References are well-signaled one-level-deep links (SIGNAL_DETECTION.md, REPORT_TEMPLATES.md, CHECKLIST.md, TOOLS_REFERENCE.md), but none of these files exist in the bundle — all links are broken — and the long reasoning strategies are inlined rather than split out.	3 / 5
	Total	15 / 20 Passed

Description

100%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, specific description that concretely names the analysis capabilities, includes natural trigger terms with synonyms, and explicitly covers both what the skill does and when to use it. Written in third person with a distinct pharmacovigilance niche.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'FAERS spontaneous-report mining', 'FDA black-box warnings', 'signal detection (PRR, ROR, IC)', 'risk factors by demographic/comorbidity', 'label change tracking' — with comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what ('Drug safety and adverse event analysis — ...') and when ('Use for post-market safety surveillance, AE signal investigation, drug-AE association strength scoring, and pharmacovigilance reports').	5 / 5
Trigger Term Quality	Comprehensive natural terms including synonyms — 'drug safety', 'adverse event'/'AE', 'safety surveillance', 'AE signal investigation', 'pharmacovigilance reports' — that users would naturally say.	5 / 5
Distinctiveness Conflict Risk	Clear pharmacovigilance niche anchored on FAERS-specific triggers; third-person voice; minimal overlap risk with other skills.	5 / 5
	Total	20 / 20 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: 4 missing	Warning

	Total	15 / 16 Passed

Repository: mims-harvard/ToolUniverse
Path: plugin/skills/tooluniverse-pharmacovigilance/SKILL.md
Commit: 1b02920

Reviewed: 1 day 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.