Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Search and synthesize biomedical literature for medical, clinical, epidemiologic, public-health, and translational research questions. Use when the user asks what the literature says, asks for evidence on a medical claim, wants PubMed or biomedical database searching, asks for a literature review, or needs studies found, screened, compared, or summarized. Do not use for patient-specific diagnosis or treatment advice.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-06 | ✗→✓ | ▲ Improved | 189% | 0% |
| case-10 | ✗→✓ | ▲ Improved | 863% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 298% | 0% |
| case-16 | ✗→✓ | ▲ Improved | 569% | 0% |
| case-17 | ✗→✓ | ▲ Improved | 311% | 0% |
Use this skill to answer biomedical research questions from the literature. The work is evidence retrieval and synthesis: search well, cover the field honestly, cite sources, weigh evidence, and state uncertainty.
This is not primarily a manuscript-writing workflow. Do not force protocol design, PRISMA language, or publication ceremony unless the user asks for systematic-review or meta-analysis rigor.
Use method detail proportionally: quick questions need searched, cited answers; formal reviews need reproducible methods.
Start from the user's real intent.
Before choosing depth or sources, infer the underlying evidence need: clinical background, mechanism, safety signal, guideline question, controversy, study identification, or formal review support.
Do not answer from memory when current or source-grounded literature is needed. Source-grounded evidence beats model recall.
Do not accommodate false premises for politeness; correct them briefly and cite the correction when it matters.
Proceed with reasonable assumptions when a first-pass search can answer the user.
Ask a blocking question only when:
When proceeding under assumptions, state them briefly in the answer or search coverage.
Use the lightest depth that can answer honestly.
Use for focused questions. Run a targeted search, inspect the best sources, and answer with a bottom line, key citations, brief evidence strength, and limits. Name the search scope briefly; do not turn the answer into a protocol.
Use for topic overviews. Search across the main concepts and synthesize by theme, question, population, intervention/exposure, outcome, mechanism, or study design. Use search coverage and study tables only when they make the review clearer.
Use when the user wants strong coverage. Track sources searched, query families, approximate records reviewed, key inclusion assumptions, and remaining gaps. Include study tables when many papers matter.
Use when requested or when the requested deliverable clearly requires publication-grade reproducibility. Define the review question, eligibility criteria, screening rules, extraction fields, risk-of-bias tools, and certainty framework; document the search reproducibly under Coverage Discipline.
Search by concepts, not by the user's exact phrasing.
OR; combine concepts with AND.For PubMed, prefer transparent queries that can be audited:
text("concept one"[tiab] OR synonym[tiab]) AND ("concept two"[tiab] OR synonym[tiab])
Use MeSH only when appropriate:
text("Heart Failure"[MeSH] OR "heart failure"[tiab] OR HFpEF[tiab]) AND ("Sodium-Glucose Transporter 2 Inhibitors"[MeSH] OR SGLT2[tiab] OR empagliflozin[tiab])
Do not repeat failed queries with cosmetic changes. Change the concept strategy.
Use any available source or tool that is academically or scientifically appropriate for the question. The list below is not exhaustive.
Prefer biomedical databases, trial registries, official agencies, guidelines, primary literature, established reviews, and scholarly discovery indexes for evidence claims.
If an important source is unavailable, state that limitation. Do not imply exhaustive coverage from one database.
For rapid answers, briefly name what was searched.
For focused or comprehensive reviews, maintain enough search trace for audit:
markdown| Source | Query family | Date searched | Records reviewed | Purpose | | --- | --- | --- | ---: | --- | | PubMed | disease + outcome synonyms | YYYY-MM-DD | 25 | broad biomedical search |
For formal systematic review support, record exact search strings, platforms, dates searched, limits/filters, record counts, deduplication, screening decisions, and exclusion reasons.
Stop searching when:
Never present "no evidence found" as proof of no effect. Say what was searched and what was not found.
Rank evidence according to the question. Treat these as judgment heuristics, not mechanical rules; directness, recency, quality, and fit to the question matter.
When foregrounding sources, prefer evidence that is direct, current, methodologically credible, and central to the field. Use lower-level evidence when it is the best available, and label why.
Separate these layers:
Do not assign confident quality labels from abstract-only review. Say "abstract-level signal" or "full-text appraisal needed."
For the main bottom line, describe evidence strength in plain language: strong, moderate, limited, preliminary, or unclear. Explain the reason briefly. Do not treat this as formal GRADE unless formal certainty appraisal is requested.
Use formal tools only when the task calls for formal appraisal:
When screening candidate studies, use the user's criteria. If criteria are absent, infer provisional criteria from the question and label them provisional.
At title/abstract stage:
maybe over exclude when uncertainmaybeWhen handling many records, deduplicate by stable identifiers first: DOI, PMID, trial registration ID, or another database ID. If identifiers are absent, compare exact title, then normalized title plus first author and year.
Use this table when screening matters:
markdown| Study | Decision | Rationale | Confidence | Needs | | --- | --- | --- | ---: | --- | | Author Year | keep / maybe / exclude | criterion-linked reason | 0.0-1.0 | full text / outcome detail / population detail |
Use this table when comparing evidence:
markdown| Study | Design | Population | Intervention/exposure | Comparator | Outcome | Main result/effect | Source reviewed | Key limits | | --- | --- | --- | --- | --- | --- | --- | --- | --- |
Every named paper, guideline, trial, report, or dataset needs a source pointer when possible.
Prefer, in order:
Never fabricate identifiers, references, sample sizes, effect estimates, confidence intervals, p values, guideline recommendations, or trial statuses.
If a reference cannot be verified, mark it:
text[UNVERIFIED - needs manual check]
If only abstracts were reviewed, say so. Do not imply full-text appraisal.
Adapt the answer to the user's requested depth. Do not dump raw search logs unless the search strategy is part of the deliverable.
markdown## Bottom Line ## Evidence ## Evidence Strength ## Limits
markdown## Bottom Line ## Search Coverage ## Evidence Map ## Synthesis ## Conflicts And Gaps ## Key Sources ## Limits
markdown## Search Question ## Search Strategy ## Sources Searched ## Evidence Table ## Synthesis ## Missing Or Unresolved Areas ## Next Steps
Before finalizing, check:
Other measured skills in the registry, with their headline benchmark lift.