Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

tooluniverse-drug-mechanism-research工具宇宙药物作用机制研究

Agent Skill

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

总安装

1,212

周安装

50

GitHub Stars

1,285

下载量

396
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:tooluniverse-drug-mechanism-research(工具宇宙药物作用机制研究)
来源仓库:https://github.com/mims-harvard/tooluniverse
仓库路径:skills/tooluniverse-drug-mechanism-research
安装命令:
npx skills add https://github.com/mims-harvard/tooluniverse --skill tooluniverse-drug-mechanism-research
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/mims-harvard/tooluniverse --skill tooluniverse-drug-mechanism-research

简介

用于查找、检索和筛选相关信息。tooluniverse-drug-mechanism-research 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

  • 适合根据关键词或任务场景快速定位候选研究资料。
  • 通过调用工具执行搜索任务并返回匹配结果列表。
  • 需结合来源仓库 README 核验具体用法和参数格式。
  • 安装前建议确认是否触发联网及文件读写权限。

SKILL.md

Drug Mechanism of Action Investigation

Investigation Philosophy

Drug mechanism research follows one core question chain:

Target -> Downstream Effect -> Pathway -> Organ Effect -> Clinical Outcome

Start with the drug's primary target. What receptor, enzyme, or transporter does it bind? Then trace forward: what does inhibiting/activating that target do immediately? What pathway is disrupted? What organ-level change results? What does the patient experience?

The LLM already knows drug pharmacology. This skill teaches HOW TO INVESTIGATE using available tools, not what mechanisms exist.

When to Use

  • "What is the mechanism of action of [drug]?"
  • "What are the molecular targets of [drug]?"
  • "Which pathways are affected by [drug]?"
  • "What pharmacogenomic interactions exist for [drug]?"
  • "What are the off-targets of [drug]?"
  • "Compare mechanisms of [drug A] vs [drug B]"

NOT for (use other skills)

  • Drug safety/adverse events profiling -> tooluniverse-adverse-event-detection
  • Drug repurposing/new indications -> tooluniverse-drug-repurposing
  • Target druggability assessment -> tooluniverse-drug-target-validation
  • Network pharmacology/polypharmacology -> tooluniverse-network-pharmacology
  • CPIC dosing guidelines specifically -> tooluniverse-pharmacogenomics

Step 1: Resolve the Drug

Before investigating mechanism, resolve the drug name to a canonical identifier. You need a ChEMBL ID for most downstream queries.

# Resolve drug name to ChEMBL ID
result = tu.tools.OpenTargets_get_drug_id_description_by_name(drugName="metformin")
# Alternative: OpenTargets_get_drug_chembId_by_generic_name(drugName="metformin")

# Get PharmGKB ID (needed for PGx queries)
result = tu.tools.PharmGKB_search_drugs(query="metformin")

Fallback: If OpenTargets returns no hits, try PharmGKB_search_drugs or ChEMBL_get_drug with a known ChEMBL ID.


Step 2: Identify the Primary Target

The first question: what does this drug bind to, and what does it do to that target?

Two complementary sources give you this:

# OpenTargets: quick summary of MOA with target gene symbols
moa = tu.tools.OpenTargets_get_drug_mechanisms_of_action_by_chemblId(chemblId="CHEMBL1431")
for row in moa["data"]["drug"]["mechanismsOfAction"]["rows"]:
    print(f"{row['mechanismOfAction']} ({row['actionType']}) -> {row['targetName']}")
    for t in row.get("targets", []):
        print(f"  Target gene: {t['approvedSymbol']} ({t['id']})")

# ChEMBL: detailed MOA with literature references and direct_interaction flag
mechs = tu.tools.ChEMBL_get_drug_mechanisms(drug_chembl_id__exact="CHEMBL1431")
for m in mechs["data"]["mechanisms"]:
    print(f"MOA: {m['mechanism_of_action']}, Direct: {m['direct_interaction']}")
    print(f"  Refs: {[r['ref_id'] for r in m.get('mechanism_refs', [])]}")

Key fields to extract: action_type (INHIBITOR, AGONIST, ANTAGONIST, etc.), target gene symbol, direct_interaction (boolean), and literature references.

Known issue: OpenTargets_get_associated_targets_by_drug_chemblId may fail (GraphQL schema change). Extract targets from the MOA results instead.


Step 3: Assess Off-Target Effects

Most drugs bind more than one target at clinical concentrations. After identifying the primary target, ask: what other proteins does this drug interact with? Off-target binding explains many side effects and drug interactions.

# ChEMBL bioactivity data shows binding affinity across targets
activities = tu.tools.ChEMBL_get_target_activities(target_chembl_id__exact="CHEMBL2364")

# STRING interaction partners reveal the target's protein network
partners = tu.tools.STRING_get_interaction_partners(identifiers="PRKAA1", species=9606)

Reasoning strategy: If ChEMBL MOA lists multiple targets, compare their action types. Same action type across related targets suggests on-pathway polypharmacology. Different action types suggest true off-target effects. The binding affinity (IC50/Ki from bioactivity data) tells you which targets matter at clinical doses -- nanomolar affinity is primary, micromolar is likely off-target.


Step 4: Map to Pathway Context

A drug target does not work in isolation. Map it to its pathway to understand the breadth of effect.

Key question: Is the target upstream (affects many downstream genes, broader effects, more side effects) or downstream (narrow, specific effect)?

# KEGG: find gene ID, then get pathways
genes = tu.tools.kegg_find_genes(keyword="PRKAA1", organism="hsa")
pathways = tu.tools.KEGG_get_gene_pathways(gene_id="hsa:5562")

# Reactome: map protein to pathways (needs UniProt ID)
reactome = tu.tools.Reactome_map_uniprot_to_pathways(uniprot_id="Q13131")

# WikiPathways: search by gene symbol
wp = tu.tools.WikiPathways_find_pathways_by_gene(gene="PRKAA1")

# STRING: functional annotations (GO terms, pathway memberships)
annot = tu.tools.STRING_get_functional_annotations(identifiers="PRKAA1", species=9606)

For multi-target drugs, run pathway enrichment to find convergent pathways:

# Reactome enrichment (space-separated gene list, NOT array)
enrichment = tu.tools.ReactomeAnalysis_pathway_enrichment(identifiers="PRKAA1 PRKAA2 PRKAB1")

# STRING enrichment
enrichment = tu.tools.STRING_functional_enrichment(identifiers="PRKAA1 PRKAA2", species=9606)

Reasoning strategy: If multiple drug targets converge on the same pathway, that pathway is the drug's true mechanism. If targets are in different pathways, the drug has genuinely multi-pathway effects -- report each separately.


Step 5: Get the Regulatory View (DailyMed)

Drug labels describe WHAT the drug does. This is the FDA-approved mechanism narrative.

DailyMed requires a two-step process: search for the drug to get a setid, then parse specific label sections.

# Step 1: Get setid
spls = tu.tools.DailyMed_search_spls(drug_name="metformin")
setid = spls["data"][0]["setid"]

# Step 2: Parse the clinical pharmacology section (MOA, PK/PD, metabolism)
pharmacology = tu.tools.DailyMed_parse_clinical_pharmacology(
    operation="parse_clinical_pharmacology", setid=setid)

# Drug interactions from the label
interactions = tu.tools.DailyMed_parse_drug_interactions(
    operation="parse_drug_interactions", setid=setid)

# Contraindications
contra = tu.tools.DailyMed_parse_contraindications(
    operation="parse_contraindications", setid=setid)

Other DailyMed parse tools: DailyMed_parse_adverse_reactions, DailyMed_parse_dosing.

Reasoning strategy: The label's clinical pharmacology section often describes the mechanism differently from database entries. The label emphasizes clinically relevant effects; databases emphasize molecular detail. Both perspectives are needed.


Step 6: Check Pharmacogenomics

Pharmacogenomic variants affect how a patient responds to the drug. This matters for mechanism because PGx genes are often the drug's metabolizing enzymes or targets.

# CPIC gene-drug pairs (gold standard for PGx)
pairs = tu.tools.CPIC_search_gene_drug_pairs(gene_symbol="CYP2C19", cpiclevel="A", limit=20)
# Or search by drug
drug_info = tu.tools.CPIC_get_drug_info(name="clopidogrel")

# FDA PGx biomarkers (what's on the label)
fda_pgx = tu.tools.fda_pharmacogenomic_biomarkers(drug_name="clopidogrel", limit=100)
# Or find all drugs affected by a gene
fda_pgx = tu.tools.fda_pharmacogenomic_biomarkers(biomarker="CYP2D6", limit=100)

# PharmGKB gene details
gene_info = tu.tools.PharmGKB_search_genes(query="CYP2C19")

Reasoning strategy: CPIC Level A/B pairs have strong evidence and actionable guidelines. If a drug has CPIC Level A interactions, those genes are critical to its mechanism (usually metabolizing enzymes or direct targets). FDA PGx biomarkers tell you what's on the approved label.


Step 7: Gather Literature Evidence

Literature describes WHY the mechanism works. Combine with labels (what) for a complete picture.

# PubMed: returns a plain list of article dicts
articles = tu.tools.PubMed_search_articles(
    query="metformin mechanism of action AMPK mitochondrial", limit=10)

# EuropePMC: returns {status, data, metadata}
articles = tu.tools.EuropePMC_search_articles(
    query="metformin mechanism action mitochondrial", limit=10)

# Follow citation chains for seminal papers
citations = tu.tools.EuropePMC_get_citations(source="MED", identifier="12345678")

Search strategy: Start with "[drug] mechanism of action [primary target]". If the mechanism is debated, add the competing hypotheses as separate queries. Recent reviews (add "review" to query) give the current consensus.


Step 8: Integrate and Report

Evidence Hierarchy

  • Tier 1 (Regulatory): FDA label (DailyMed), CPIC Level A, FDA PGx biomarker
  • Tier 2 (Experimental): ChEMBL mechanisms with literature refs, binding data
  • Tier 3 (Database): OpenTargets MOA, pathway databases (KEGG/Reactome/WikiPathways)
  • Tier 4 (Literature): PubMed/EuropePMC articles

Report Structure

## Drug Mechanism Report: [Drug Name]

### Drug Identity
- ChEMBL ID, PharmGKB ID, approval status

### Primary Mechanism
- Target: [gene symbol], Action: [INHIBITOR/AGONIST/etc.]
- Mechanism narrative (from DailyMed + databases)
- Direct interaction: yes/no

### Off-Target Effects
- Additional targets with action types and binding affinities
- Which off-targets explain known side effects

### Pathway Context
- Key pathways (from KEGG/Reactome/WikiPathways)
- Upstream vs downstream position of target
- Convergent pathways for multi-target drugs

### Pharmacogenomics
- CPIC gene-drug pairs with levels
- FDA PGx biomarkers

### Drug Interactions
- Mechanism-based interactions (enzyme inhibition/induction)
- Key interactions from DailyMed

### Evidence Summary
| Finding | Source | Tier |
|---------|--------|------|
| Primary MOA | ChEMBL + DailyMed | T1/T2 |
| Off-targets | ChEMBL bioactivity | T2 |
| Pathways | KEGG/Reactome | T3 |
| PGx | CPIC/FDA | T1 |

Comparing Two Drugs

When comparing mechanisms, run Steps 2-4 for both drugs, then align:

  1. Same target, different action? (e.g., agonist vs antagonist at the same receptor)
  2. Different targets, same pathway? (e.g., both affect insulin signaling but at different nodes)
  3. Different pathways entirely? (e.g., metformin on AMPK vs pioglitazone on PPAR-gamma)
for drug in [("metformin", "CHEMBL1431"), ("pioglitazone", "CHEMBL595")]:
    moa = tu.tools.OpenTargets_get_drug_mechanisms_of_action_by_chemblId(chemblId=drug[1])
    clin = tu.tools.DailyMed_parse_clinical_pharmacology(drug_name=drug[0])

Fallback Strategies

StepPrimary ToolFallback
Drug IDOpenTargets_get_drug_id_description_by_namePharmGKB_search_drugs
MOAOpenTargets_get_drug_mechanisms_of_action_by_chemblIdChEMBL_get_drug_mechanisms
PathwaysKEGG_get_gene_pathwaysWikiPathways_find_pathways_by_gene, Reactome_map_uniprot_to_pathways
PGxCPIC_search_gene_drug_pairsfda_pharmacogenomic_biomarkers
Clinical infoDailyMed_parse_clinical_pharmacologyOpenTargets_get_drug_description_by_chemblId
DDIDailyMed_parse_drug_interactionsPubMed_search_articles (DDI query)
LiteraturePubMed_search_articlesEuropePMC_search_articles

MetaCyc note: MetaCyc requires a paid account and is not available. Use KEGG, Reactome, or WikiPathways instead.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

32.66%
按下载量换算129

Claude

31.17%
按下载量换算123

Cursor

18.01%
按下载量换算71

Gemini CLI

9.73%
按下载量换算39

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills