npx skills add smithery/u9401066 --skill pubmed-pico-search
u9401066/pubmed-search-mcp · Archived
pubmed-pico-search
Agent-guided PICO clinical question search using validate_pico_plan handoff and unified_search. Triggers: PICO, 臨床問題, A比B好嗎, treatment comparison, clinical question, 療效比較
Installation
npx skills add u9401066/pubmed-search-mcp --skill pubmed-pico-search
Stronger alternatives
This repository is archived — consider an actively maintained alternative.
Cline harness for PubMed Search MCP. Triggers: pubmed search, literature search, unified_search…
3 installsBounded, reproducible review-seed search using generate_search_queries and unified_search. Trig…
2 installsQuick literature search using unified_search. Triggers: 搜尋, 找論文, search papers, find artic…
2 installsDeep exploration from a key paper using related, citing, reference, and citation tree tools. Tr…
2 installsSimilar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsArchitect and provision enterprise Azure infrastructure from workload descriptions. For cloud a…
402.8K installsAlso in this package
Other skills from u9401066/pubmed-search-mcp · top by installs.
npx skills add u9401066/pubmed-search-mcp
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
master
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md3,679 B -
docs
SUMMARY.md218 B
History
- First seen on skills.sh
- First recorded snapshot · 1 installs
SKILL.md
PICO Clinical Question Search
Use this workflow for clinical comparison questions. The MCP server does not semantically parse natural-language clinical questions. The agent extracts P/I/C/O, submits the structured handoff through validatepicoplan, and then executes the returned template: pico pipeline or an expanded Boolean query.
PICO Elements
| Element | Meaning | Example |
|---|---|---|
P |
Population / patient group | ICU patients requiring sedation |
I |
Intervention / exposure / index test | remimazolam |
C |
Comparator, optional | propofol |
O |
Outcome, recommended | delirium, hypotension, sedation efficacy |
Workflow
Agent extracts P/I/C/O
-> validate_pico_plan(description, p, i, c, o)
-> optional generate_search_queries for P/I/C/O expansion
-> unified_search(query=original_question, pipeline=validate_pico_plan.pipeline)
Step 1: Agent Extracts PICO
Do the semantic work in the agent. Do not ask the MCP server to infer P/I/C/O from free text. If P or I is unclear, ask the user before searching. Do not invent missing clinical details.
Step 2: Validate The Handoff
pico = validate_pico_plan(
description="Is remimazolam better than propofol for ICU sedation?",
p="ICU patients requiring sedation",
i="remimazolam",
c="propofol",
o="delirium, hypotension, sedation efficacy",
question_type="therapy",
sources=["pubmed", "europe_pmc"],
limit=50,
)
Expected useful fields:
validation: whether required P/I fields are presentpico: human-readable P/I/C/Oquery_elements: search fragments that the backend will usepipeline: ready-to-runtemplate: picoYAMLnexttoolcall: suggestedunified_searchcall
When only description is provided, validatepicoplan returns a schema and asks the agent to call it again with structured elements.
Step 3: Optional MeSH / Synonym Expansion
Use this when the topic needs controlled vocabulary or systematic-review style coverage.
generate_search_queries(topic="ICU patients")
generate_search_queries(topic="remimazolam")
generate_search_queries(topic="propofol")
generate_search_queries(topic="delirium")
If you build high-quality fragments, pass them back as:
validate_pico_plan(
description="Is remimazolam better than propofol for ICU sedation?",
p="ICU patients requiring sedation",
p_query='("Intensive Care Units"[MeSH] OR ICU[tiab])',
i="remimazolam",
i_query="(remimazolam[tiab] OR CNS7056[tiab])",
c="propofol",
c_query='("Propofol"[MeSH] OR propofol[tiab])',
o="delirium",
o_query='("Delirium"[MeSH] OR delirium[tiab])',
)
Step 4: Execute Search
unified_search(
query="Is remimazolam better than propofol for ICU sedation?",
pipeline=pico["pipeline"],
ranking="quality",
)
The backend PICO pipeline searches O-aware precision and recall variants, deduplicates results, merges ranked lists, and enriches the final set.
Missing Fields
- Missing
C: allowed. Do not invent a comparator. - Missing
O: allowed but discouraged. Ask the user when the outcome is central. - Missing
PorI: ask the user before running a structured PICO search.
Recommended Reporting
Always show the final P/I/C/O table, the query or pipeline profile used, and the main limits such as sources, years, species, and clinical query filter.