CtrlK
BlogDocsLog inGet started
Tessl Logo

single-drug-faers-safety-profile-research-planner

Generates complete FAERS pharmacovigilance study designs for one-drug whole-profile safety mapping using signal detection, subgroup analysis, onset/seriousness characterization, and conservative label-gap interpretation.

62

Quality

78%

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/single-drug-faers-safety-profile-research-planner/SKILL.md
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 well-structured, well-disciplined instruction skill: the 7-step execution flow has explicit validation checkpoints and feedback loops, and progressive disclosure is exemplary with eight real, one-level-deep reference files. The main weakness is redundancy — duplicated trigger examples and near-identical hard rules inflate the token budget without adding guidance.

Suggestions

Delete the 'Sample Triggers' section, which repeats the four Input Validation example bullets verbatim.

Merge Hard Rules 3 and 14 (both forbid incidence/absolute-risk framing of disproportionality signals) and Hard Rules 10 and 13 (both forbid silent scope switching) into single rules.

DimensionReasoningScore

Conciseness

The body is mostly efficient rule-driven prose, but contains real duplication: the 'Sample Triggers' section repeats the four Input Validation examples verbatim, Hard Rules 3 and 14 both forbid presenting disproportionality signals as incidence/absolute risk, and Hard Rules 10 and 13 overlap heavily. This fits the 3 anchor (mostly efficient but could be tightened) rather than 4, since the repetition is substantive enough to remove whole blocks.

3 / 5

Actionability

For an instruction-only planning skill the guidance is concrete: exact pattern and config selection tables, named output sections A–J with required fields, minimum retrieval counts ('2–4 drug/safety-background references'), an exact disclaimer line to reproduce, and per-reference format rules. Fits the 4 anchor (mostly executable guidance with minor gaps); not 5 because several directives remain abstract ('Explain the logic of each decision') and concrete templates are deferred to reference files.

4 / 5

Workflow Clarity

The 'Execution — 7 Steps (always run in order)' section gives a clear sequence with an explicit pre-output validation checkpoint (Step 5 dependency consistency check) and a fix loop ('If any dependency inconsistency is found, revise the plan before outputting'), plus input validation with a stop-and-redirect and a hard-rules checklist. This matches the 5 anchor (explicit validation steps, feedback loops, checklists).

5 / 5

Progressive Disclosure

Eight '→' links are well-signaled at each point of need, all point to real files in references/, and are exactly one level deep with no nested references inside the bundle files; the body keeps only overview-level content while details are split into appropriately scoped files. This matches the 5 anchor (clear overview with well-signaled one-level-deep references, easy navigation).

5 / 5

Total

17

/

20

Passed

Description

71%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 third-person description that concretely enumerates the skill's capabilities in its niche. Its main weakness is the absence of any explicit 'Use when...' trigger clause, which caps completeness, and some natural user phrasings (e.g., 'adverse events', 'post-marketing surveillance') are missing from the trigger vocabulary.

Suggestions

Append an explicit trigger clause, e.g., 'Use when the user asks for a single-drug FAERS safety-atlas study design, whole-profile adverse-event signal scan, or pharmacovigilance research plan for one medication.'

Add natural synonyms users would say, such as 'adverse events', 'post-marketing surveillance', and 'drug safety profile', to improve trigger-term coverage.

Sharpen distinctiveness against sibling skills by leading with the single-drug constraint, e.g., 'Designs one-drug (not active-comparator) FAERS safety-profile studies...'

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Generates... study designs', 'signal detection', 'subgroup analysis', 'onset/seriousness characterization', 'conservative label-gap interpretation' — covering the skill's full module set in correct third-person voice. It matches the 5 anchor (multiple specific concrete actions, comprehensive coverage) rather than 4, since no module category is missing.

5 / 5

Completeness

The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the judging guidelines cap at 3. It fits the 3 anchor (clear 'what', 'when' missing or only weakly implied) rather than 4, which would require an explicit 'when' clause.

3 / 5

Trigger Term Quality

'FAERS', 'pharmacovigilance', 'signal detection', and 'safety' are natural domain keywords a user would say, but common variants like 'adverse events', 'post-marketing surveillance', and 'drug safety' are absent. Good coverage with a few natural terms missing fits the 4 anchor, below 5 (which requires comprehensive synonym coverage) and above 3 (which implies noticeably sparser keywords).

4 / 5

Distinctiveness Conflict Risk

'One-drug whole-profile safety mapping' carves a specific niche with distinct triggers, but the broad lead 'FAERS pharmacovigilance study designs' overlaps with closely related sibling skills (e.g., comparative FAERS designs referenced in the body). Mostly distinct with minor overlap risk fits the 4 anchor rather than 5.

4 / 5

Total

16

/

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