Token导航 LogoToken导航

Agent Skill · 研究检索

tooluniverse-adverse-event-detection(tooluniverse 不良事件检测)

tooluniverse-adverse-event-detection 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

tooluniverse-adverse-event-detection 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 22,471。

总安装 4,543周安装 182GitHub Stars 1,285下载 1,471核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:tooluniverse-adverse-event-detection(tooluniverse 不良事件检测)
来源仓库:https://github.com/mims-harvard/tooluniverse
仓库路径:skills/tooluniverse-adverse-event-detection
安装命令:
npx skills add https://github.com/mims-harvard/tooluniverse --skill tooluniverse-adverse-event-detection
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/mims-harvard/tooluniverse --skill tooluniverse-adverse-event-detection

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

tooluniverse-adverse-event-detection 用于查找、检索和筛选相关信息。适用于药物安全性监测或不良事件识别的研究场景。通过 npx skills add 命令从指定 GitHub 仓库安装并使用。安装前需确认权限范围、维护状态及是否触发联网或文件读写操作。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/tooluniverse-adverse-event-detection

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/mims-harvard/tooluniverse --skill tooluniverse…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

tooluniverse-adverse-event-detection 怎么安装?

在终端执行 npx skills add https://github.com/mims-harvard/tooluniverse --skill tooluniverse-adverse-e…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

tooluniverse-adverse-event-detection 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

tooluniverse-adverse-event-detection 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

tooluniverse-adverse-event-detection 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

tooluniverse-adverse-event-detection 用的人多吗?

公开数据是累计安装 4,543 次,近一周安装 182 次,下载 1,471 次,GitHub 1,285 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

tooluniverse-adverse-event-detection 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 来源仓库有 1,285 星,维护活跃度相对可查。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
tooluniverse-adverse-event-detection

tooluniverse 不良事件检测 · 本页

4,5431,285只读未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

COMPUTE, DON'T DESCRIBE

When analysis requires computation (statistics, data processing, scoring, enrichment), write and run Python code via Bash. Don't describe what you would do — execute it and report actual results. Use ToolUniverse tools to retrieve data, then Python (pandas, scipy, statsmodels, matplotlib) to analyze it.

Adverse Drug Event Signal Detection & Analysis

Automated pipeline for detecting, quantifying, and contextualizing adverse drug event signals using FAERS disproportionality analysis, FDA label mining, mechanism-based prediction, and literature evidence. Produces a quantitative Safety Signal Score (0-100) for regulatory and clinical decision-making.

KEY PRINCIPLES:

  1. Signal quantification first - Every adverse event must have PRR/ROR/IC with confidence intervals
  2. Serious events priority - Deaths, hospitalizations, life-threatening events always analyzed first
  3. Multi-source triangulation - FAERS + FDA labels + OpenTargets + DrugBank + literature
  4. Context-aware assessment - Distinguish drug-specific vs class-wide vs confounding signals
  5. Report-first approach - Create report file FIRST, update progressively
  6. Evidence grading mandatory - T1 (regulatory/boxed warning) through T4 (computational)
  7. English-first queries - Always use English drug names in tool calls, respond in user's language

REASONING STRATEGY — Start Here: Start with the signal: What adverse event was reported more than expected? (PRR >= 2.0, N >= 3, lower CI > 1.0 is the threshold). Then ask three questions in order:

  1. Biologically plausible? Given the drug's mechanism of action and targets, does this adverse event make sense? An off-target kinase inhibitor causing cardiac events is plausible; a topical agent causing systemic toxicity needs more scrutiny. LOOK UP DON'T GUESS — use OpenTargets_get_drug_mechanisms_of_action_by_chemblId and drugbank_get_targets_by_drug_name_or_drugbank_id to check targets before asserting plausibility.
  2. Timing consistent? Acute reactions (within hours/days) suggest immune or direct pharmacologic mechanism. Delayed reactions (weeks/months) suggest cumulative toxicity or idiosyncratic response. Check FAERS time-to-onset distribution.
  3. Could confounders explain it? Patients taking this drug likely have the underlying disease — compare against background rate in that population, not the general population. Class-wide signals (appearing for all drugs in the class) suggest mechanism-based rather than molecule-specific toxicity.

Causality Assessment — Naranjo Algorithm Reasoning: When determining whether an adverse event is drug-caused (not just associated), apply these steps systematically. LOOK UP DON'T GUESS — search FAERS and FDA labels for each criterion:

  1. Prior reports? Are there previous conclusive reports of this reaction? Check FDA label (FDA_get_adverse_reactions_by_drug_name) and literature (PubMed_search_articles). Yes = +1.
  2. Temporal relationship? Did the AE appear after drug administration? Onset within expected pharmacokinetic window (1-5 half-lives) = +2. Use FAERS_stratify_by_demographics for time-to-onset data.
  3. Dechallenge? Did the AE improve when the drug was stopped? Positive dechallenge = +1. Look for rechallenge/dechallenge case reports in literature.
  4. Rechallenge? Did the AE reappear when the drug was restarted? Positive rechallenge = +2 (strongest single piece of evidence for causality).
  5. Alternative causes? Could the underlying disease, concomitant drugs, or other factors explain the AE? Check drugbank_get_drug_interactions_by_drug_name_or_id for interacting drugs.
  6. Dose-response? Did the reaction worsen with higher doses or improve with lower doses? Dose-dependent AEs suggest on-target toxicity.
  7. Drug level confirmation? Was the drug detected in body fluids at toxic concentrations?
  • Score: Definite (>=9), Probable (5-8), Possible (1-4), Doubtful (<=0).
  • Even without individual patient data, you can estimate causality from aggregate FAERS signals + label evidence + mechanistic plausibility.

Reference files (in this directory):

  • PHASE_DETAILS.md - Detailed tool calls, code examples, and output templates per phase
  • REPORT_TEMPLATE.md - Full report template and completeness checklist
  • TOOL_REFERENCE.md - Tool parameter reference and fallback chains
  • QUICK_START.md - Quick examples and common drug names

When to Use

Apply when user asks:

  • "What are the safety signals for [drug]?"
  • "Detect adverse events for [drug]"
  • "Is [drug] associated with [adverse event]?"
  • "What are the FAERS signals for [drug]?"
  • "Compare safety of [drug A] vs [drug B] for [adverse event]"
  • "What are the serious adverse events for [drug]?"
  • "Are there emerging safety signals for [drug]?"
  • "Post-market surveillance report for [drug]"
  • "Pharmacovigilance signal detection for [drug]"

Differentiation from tooluniverse-pharmacovigilance: This skill focuses specifically on signal detection and quantification using disproportionality analysis (PRR, ROR, IC) with statistical rigor, produces a quantitative Safety Signal Score (0-100), and performs comparative safety analysis across drug classes.


Workflow Overview

Phase 0: Input Parsing & Drug Disambiguation
  Parse drug name, resolve to ChEMBL ID, DrugBank ID
  Identify drug class, mechanism, and approved indications
    |
Phase 1: FAERS Adverse Event Profiling
  Top adverse events by frequency
  Seriousness and outcome distributions
  Demographics (age, sex, country)
    |
Phase 2: Disproportionality Analysis (Signal Detection)
  Calculate PRR, ROR, IC with 95% CI for each AE
  Apply signal detection criteria
  Classify signal strength (Strong/Moderate/Weak/None)
    |
Phase 3: FDA Label Safety Information
  Boxed warnings, contraindications
  Warnings and precautions, adverse reactions
  Drug interactions, special populations
    |
Phase 4: Mechanism-Based Adverse Event Context
  Target-based AE prediction (OpenTargets safety)
  Off-target effects, ADMET predictions
  Drug class effects comparison
    |
Phase 5: Comparative Safety Analysis
  Compare to drugs in same class
  Identify unique vs class-wide signals
  Head-to-head disproportionality comparison
    |
Phase 6: Drug-Drug Interactions & Risk Factors
  Known DDIs causing AEs
  Pharmacogenomic risk factors (PharmGKB)
  FDA PGx biomarkers
    |
Phase 7: Literature Evidence
  PubMed safety studies, case reports
  OpenAlex citation analysis
  Preprint emerging signals (EuropePMC)
    |
Phase 8: Risk Assessment & Safety Signal Score
  Calculate Safety Signal Score (0-100)
  Evidence grading (T1-T4) for each signal
  Clinical significance assessment
    |
Phase 9: Report Synthesis & Recommendations
  Monitoring recommendations
  Risk mitigation strategies
  Completeness checklist

Phase Summaries

Phase 0: Input Parsing & Drug Disambiguation

Resolve drug name to ChEMBL ID, DrugBank ID. Get mechanism of action, blackbox warning status, targets, and approved indications.

  • Tools: OpenTargets_get_drug_chembId_by_generic_name, OpenTargets_get_drug_mechanisms_of_action_by_chemblId, OpenTargets_get_drug_blackbox_status_by_chembl_ID, drugbank_get_safety_by_drug_name_or_drugbank_id, drugbank_get_targets_by_drug_name_or_drugbank_id, OpenTargets_get_drug_indications_by_chemblId

Phase 1: FAERS Adverse Event Profiling

Query FAERS for top adverse events, seriousness distribution, outcomes, demographics, and death-related events. Filter serious events by type (death, hospitalization, life-threatening). Get MedDRA hierarchy rollup.

  • Tools: FAERS_count_reactions_by_drug_event, FAERS_count_seriousness_by_drug_event, FAERS_count_outcomes_by_drug_event, FAERS_count_patient_age_distribution, FAERS_count_death_related_by_drug, FAERS_count_reportercountry_by_drug_event, FAERS_filter_serious_events, FAERS_rollup_meddra_hierarchy

Phase 2: Disproportionality Analysis (Signal Detection)

CRITICAL PHASE. For each top adverse event (at least 15-20), calculate PRR, ROR, IC with 95% CI. Classify signal strength. Stratify strong signals by demographics.

  • Tools: FAERS_calculate_disproportionality, FAERS_stratify_by_demographics
  • MedDRA term level note: FAERS_count_reactions_by_drug_event filters by MedDRA Lowest Level Term (reactionmeddraverse) while FAERS_calculate_disproportionality uses Preferred Terms. Case counts can differ dramatically — always use disproportionality analysis as the primary signal metric, not raw counts.
  • Signal criteria: PRR >= 2.0 AND lower CI > 1.0 AND N >= 3
  • Strength: Strong (PRR >= 5), Moderate (PRR 3-5), Weak (PRR 2-3)
  • See PHASE_DETAILS.md for full signal classification table

Phase 3: FDA Label Safety Information

Extract boxed warnings, contraindications, warnings/precautions, adverse reactions, drug interactions, and special population info. Note: {error: {code: "NOT_FOUND"}} is normal when a section does not exist.

  • Tools: FDA_get_boxed_warning_info_by_drug_name, FDA_get_contraindications_by_drug_name, FDA_get_warnings_by_drug_name, FDA_get_adverse_reactions_by_drug_name, FDA_get_drug_interactions_by_drug_name, FDA_get_pregnancy_or_breastfeeding_info_by_drug_name, FDA_get_geriatric_use_info_by_drug_name, FDA_get_pediatric_use_info_by_drug_name, FDA_get_pharmacogenomics_info_by_drug_name

Phase 4: Mechanism-Based Adverse Event Context

Get target safety profile, OpenTargets adverse events, ADMET toxicity predictions (if SMILES available), and drug warnings.

  • Tools: OpenTargets_get_target_safety_profile_by_ensemblID, OpenTargets_get_drug_adverse_events_by_chemblId, ADMETAI_predict_toxicity, ADMETAI_predict_CYP_interactions, OpenTargets_get_drug_warnings_by_chemblId

Phase 5: Comparative Safety Analysis

Head-to-head comparison with class members using FAERS_compare_drugs. Aggregate class AEs. Identify class-wide vs drug-specific signals.

  • Tools: FAERS_compare_drugs, FAERS_count_additive_adverse_reactions, FAERS_count_additive_seriousness_classification

Phase 6: Drug-Drug Interactions & Risk Factors

Extract DDIs from FDA label, DrugBank, and DailyMed. Query PharmGKB for pharmacogenomic risk factors and dosing guidelines. Check FDA PGx biomarkers.

  • Tools: FDA_get_drug_interactions_by_drug_name, drugbank_get_drug_interactions_by_drug_name_or_id, DailyMed_parse_drug_interactions, PharmGKB_search_drugs, PharmGKB_get_drug_details, PharmGKB_get_dosing_guidelines, fda_pharmacogenomic_biomarkers

Phase 7: Literature Evidence

Search PubMed, OpenAlex, and EuropePMC for safety studies, case reports, and preprints.

  • Tools: PubMed_search_articles, openalex_search_works, EuropePMC_search_articles

Phase 8: Risk Assessment & Safety Signal Score

Calculate Safety Signal Score (0-100) from four components: FAERS signal strength (0-35), serious AEs (0-30), FDA label warnings (0-25), literature evidence (0-10). Grade each signal T1-T4. See PHASE_DETAILS.md for scoring rubric.

Phase 9: Report Synthesis

Generate comprehensive markdown report with executive summary, all phase outputs, monitoring recommendations, risk mitigation strategies, patient counseling points, and completeness checklist. See REPORT_TEMPLATE.md for full template.


Edge Cases

  • No FAERS reports: Skip Phases 1-2; rely on FDA label, mechanism predictions, literature
  • Generic vs Brand name: Try both in FAERS; use OpenTargets_get_drug_chembId_by_generic_name to resolve
  • Drug combinations: Use FAERS_count_additive_adverse_reactions for aggregate class analysis
  • Confounding by indication: Compare AE profile to the disease being treated; note limitation in report
  • Drugs with boxed warnings: Score component automatically 25/25 for label warnings; prioritize boxed warning events

平台分布

Codex

37.44%
按下载量换算551

Claude

32.13%
按下载量换算473

Cursor

19.1%
按下载量换算281

Gemini CLI

8.72%
按下载量换算128

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills