CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

faers-pharmacovigilance-disproportionality-research-planner

Generates complete FAERS-style pharmacovigilance disproportionality research designs from a user-provided drug class, comparator strategy, adverse-event domain, and patient-group stratification. Always use this skill whenever a user wants to design, plan, or build a spontaneous-report safety signal study using FAERS or a similar pharmacovigilance database, especially when the article logic includes product selection, indication-group stratification, MedDRA-based adverse-event extraction, serious-case filtering, suspect-drug and concomitant-exclusion logic, reporting odds ratio analysis, comparator-drug benchmarking, cross-drug comparison, and cautious signal interpretation without causal overclaiming. Covers five study patterns (single-drug disproportionality workflow, multi-drug class comparison workflow, indication-stratified workflow, comparator-controlled signal screening workflow...

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./awesome-med-research-skills/Protocol Design/faers-pharmacovigilance-disproportionality-research-planner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

66%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 well-engineered instruction skill: crisp input validation, a genuinely sequenced workflow with a mandatory pre-output consistency check and feedback loop, and a clean one-level-deep reference bundle. Its main weakness is token efficiency — the Hard Rules section and parts of Step 7 duplicate earlier content almost verbatim — plus the fifth study pattern is never enumerated in the body either.

Suggestions

Cut the redundant 'Hard Rules' recap: rules 1–23 largely restate Steps 3–7 and Sections C.5/G/I/J/D verbatim; keep only genuinely new rules (note the numbering also skips 10 after rule 9) and drop the rest to save ~20 lines of repeated tokens.

Move the detailed A–J output-section specifications and the Step 5 dependency rules into a reference file (e.g., references/output-sections.md), keeping a one-line summary of required sections in the body, to match the disclosure pattern already used for patterns/configs/methods.

Add the concrete ROR computation definition (2×2 contingency table, ROR formula with 95% CI) either inline or explicitly in references/method-library.md, so the analysis steps are directly executable rather than delegated by name.

DimensionReasoningScore

Conciseness

The body is written twice: the 23-item 'Hard Rules' section restates Steps 3–7 nearly verbatim (e.g., rules 11–13 repeat Step 4.5's citation rules, rules 15/17 repeat Section G, rule 22 repeats the Section D disclaimer), and Section B/J requirements restate earlier step content. It does not explain concepts Claude already knows, but it contains several padded, purely redundant sections, matching the 2 anchor ('noticeably verbose; several unnecessary... padded sections') better than 3, where redundancy would be incidental rather than structural.

2 / 5

Actionability

For an instruction-only skill the guidance is concrete: an exact out-of-scope redirect script, a pattern-selection table, per-config field requirements, explicit forbidden-claim lists, exact endpoint formulas ('FAERS query + MedDRA PT extraction + comparator + ROR'), and quantified retrieval minimums ('2–4 drug/adverse-event-domain background references'). It falls short of 5 because key analysis mechanics (the ROR/CI computation itself, actual FAERS query construction) are delegated by name without inline anchors, and directives like 'Explain the logic of each decision' remain abstract.

4 / 5

Workflow Clarity

Seven explicitly ordered steps with genuine validation checkpoints and a feedback loop: Step 5 is a mandatory pre-output dependency consistency check with 'If any dependency inconsistency is found, revise the plan before outputting' (validate → fix → re-check), plus checklists (Hard Rules, the six-element Section J review, forbidden-claim gate). This matches the 5 anchor's 'explicit validation steps; feedback loops for error recovery; checklists'.

5 / 5

Progressive Disclosure

The body links 8 reference files, all of which exist, are one level deep, and never reference each other — clearly signaled with '→ Detailed pattern logic: [references/study-patterns.md]' style pointers. However, substantial detail (the full A–J output-section specifications and the Hard Rules recap) is inlined in SKILL.md where this bundle's own pattern would put it in a reference, so organization is good but not optimally split — the 4 anchor.

4 / 5

Total

15

/

20

Passed

Description

87%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 highly effective description: concrete capability list, explicit 'use when' trigger guidance, and a clearly staked-out pharmacovigilance niche. The one real defect is that the text ends truncated mid-enumeration ('comparator-controlled signal screening workflow...'), never naming the fifth study pattern — this reads as a copy/paste error and should be completed or trimmed.

DimensionReasoningScore

Specificity

The description lists many concrete actions — 'product selection, indication-group stratification, MedDRA-based adverse-event extraction, serious-case filtering, suspect-drug and concomitant-exclusion logic, reporting odds ratio analysis, comparator-drug benchmarking, cross-drug comparison' — which is near-comprehensive coverage of the workflow. It falls just short of a 5 because the final study-pattern enumeration is cut off mid-sentence ('comparator-controlled signal screening workflow...'), leaving a gap, and the sheer length adds padding rather than new specificity.

4 / 5

Completeness

Both questions are explicitly answered: 'what' via 'Generates complete FAERS-style pharmacovigilance disproportionality research designs from a user-provided drug class, comparator strategy, adverse-event domain, and patient-group stratification', and 'when' via the explicit 'Always use this skill whenever a user wants to design, plan, or build a spontaneous-report safety signal study using FAERS or a similar pharmacovigilance database, especially when...' clause with concrete trigger conditions. This matches the 5 anchor; the mid-sentence truncation occurs after both are fully answered, so it does not drop the score.

5 / 5

Trigger Term Quality

Strong natural keywords a target user would say: 'FAERS', 'pharmacovigilance', 'safety signal study', 'disproportionality', 'drug class', 'adverse-event domain', 'reporting odds ratio', 'MedDRA', plus 'design, plan, or build'. A few common variations are missing (e.g., 'signal detection', 'spontaneous reporting system', named alternative databases like VigiBase), so it sits between the 4 and 5 anchors, closer to 4.

4 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — FAERS-style spontaneous-report disproportionality study design — with domain-specific triggers (FAERS, MedDRA, ROR, suspect-drug exclusion) that no general skill would claim, and the boundary is reinforced by 'cautious signal interpretation without causal overclaiming'. Minimal conflict risk; matches the 5 anchor.

5 / 5

Total

18

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

awesome-med-research-skills/Protocol Design/faers-pharmacovigilance-disproportionality-research-planner/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.