Skip to main content
Agent skill

Scientific Db Pubmed Database

Direct PubMed and NCBI E-utilities search workflows for biomedical literature, MeSH queries, PMID lookup, citation retrieval, and API-backed literature monitoring. Use when a task needs biomedical literature from PubMed rather than general web search.

Get started

Get the complete skill folder, including its scripts and reference files.

·

When to use this skill

Use Scientific Db Pubmed Database when an AI agent needs a reusable SKILL.md workflow for this job: Direct PubMed and NCBI E-utilities search workflows for biomedical literature, MeSH queries, PMID lookup, citation retrieval, and API-backed literature monitoring. Use when a task needs biomedical literature from PubMed rather than general web search.

When not to use it

Skip Scientific Db Pubmed Database when the task is outside the analysis category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/scientific-db-pubmed-database
# Save SKILL.md to ~/.claude/skills/scientific-db-pubmed-database/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/scientific-db-pubmed-database/SKILL.md. For a shared project, commit the folder at .claude/skills/scientific-db-pubmed-database/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Scientific Db Pubmed Database skill for this task: Searching MEDLINE or life-sciences literature. Confirm any required inputs or files before making changes.

What supports this recommendation?

83/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
92/100
Practical detail
92/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# PubMed Database

Use this skill when a task needs biomedical literature from PubMed rather than general web search.

## When to Use

- Searching MEDLINE or life-sciences literature. - Building PubMed queries with MeSH terms, field tags, dates, or article types. - Looking up PMIDs, abstracts, publication metadata, or related citations. - Running systematic-review search passes that need repeatable search strings. - Using NCBI E-utilities directly from Python, shell, or another HTTP client.

## Query Construction

Start with the research question, split it into concepts, then combine concepts with Boolean operators.

```text concept_1 AND concept_2 AND filter synonym_a OR synonym_b NOT exclusion_term ```

Useful PubMed field tags:

- `[ti]`: title - `[ab]`: abstract - `[tiab]`: title or abstract - `[au]`: author - `[ta]`: journal title abbreviation - `[mh]`: MeSH term - `[majr]`: major MeSH topic - `[pt]`: publication type - `[dp]`: date of publication - `[la]`: language

Examples:

```text diabetes mellitus[mh] AND treatment[tiab] AND systematic review[pt] AND 2023:2026[dp] (metformin[nm] OR insulin[nm]) AND diabetes mellitus, type 2[mh] AND randomized controlled trial[pt] smith ja[au] AND cancer[tiab] AND 2026[dp] AND english[la] ```

## MeSH and Subheadings

Prefer MeSH when the concept has a stable controlled-vocabulary term. Combine MeSH with title/abstract terms when the topic is new or terminology varies.

Correct subheading syntax puts the subheading before the field tag:

```text diabetes mellitus, type 2/drug therapy[mh] cardiovascular diseases/prevention & control[mh] ```

Use `[majr]` only when the topic must be central to the paper. It can improve precision but may miss relevant work.

## Filters

Publication types:

- `clinical trial[pt]` - `meta-analysis[pt]` - `randomized controlled trial[pt]` - `review[pt]` - `systematic review[pt]` - `guideline[pt]`

Date filters:

```text 2026[dp] 2020:2026[dp] 2026/03/15[dp] ```

Availability filters:

```text free full text[sb] hasabstract[text] ```

## E-utilities Workflow

NCBI E-utilities supports repeatable API workflows:

1. `esearch.fcgi`: search and return PMIDs. 2. `esummary.fcgi`: return lightweight article metadata. 3. `efetch.fcgi`: fetch abstracts or full records in XML, MEDLINE, or text. 4. `elink.fcgi`: find related articles and linked resources.

Use an email and API key for production scripts. Store API keys in environment variables, never in committed files or command history.

```python import os import time import requests

BASE = "https://eutils.ncbi.nlm.nih.gov/entrez/eutils"

def esearch(query: str, retmax: int = 20) -> list[str]: params = { "db": "pubmed", "term": query, "retmode": "json", "retmax": retmax, "tool": "ecc-pubmed-search", "email": os.environ.get("NCBI_EMAIL", ""), } api_key = os.environ.get("NCBI_API_KEY") if api_key: params["api_key"] = api_key

response = requests.get(f"{BASE}/esearch.fcgi", params=params, timeout=30) response.raise_for_status() time.sleep(0.35) return response.json()["esearchresult"]["idlist"]

pmids = esearch("hypertension[mh] AND randomized controlled trial[pt] AND 2024:2026[dp]") print(pmids) ```

For batches, prefer NCBI history server parameters (`usehistory=y`, `WebEnv`, `query_key`) instead of passing very long PMID lists through URLs.

## Output Discipline

For each search pass, record:

- exact search string - database searched - date searched - filters used - result count - export format - any manual exclusions

Example:

```markdown | Database | Date searched | Query | Filters | Results | | --- | --- | --- | --- | ---: | | PubMed | 2026-05-11 | `sickle cell disease[mh] AND CRISPR[tiab]` | 2020:2026[dp], English | 42 | ```

## Review Checklist

- Are field tags valid PubMed tags? - Are MeSH terms paired with free-text synonyms for newer topics? - Is the date range explicit and appropriate? - Does the search log include enough detail to reproduce the query? - Are API keys loaded from the environment? - Does HTTP code call `raise_for_status()` or otherwise handle non-200 responses before parsing? - Are rate limits respected?

## References

- [PubMed help](https://pubmed.ncbi.nlm.nih.gov/help/) - [NCBI E-utilities documentation](https://www.ncbi.nlm.nih.gov/books/NBK25501/) - [NCBI API key guidance](https://support.nlm.nih.gov/kbArticle/?pn=KA-05317) - NCBI support: <[email protected]>

Intended uses

  • Searching MEDLINE or life-sciences literature.
  • Building PubMed queries with MeSH terms, field tags, dates, or article types.
  • Looking up PMIDs, abstracts, publication metadata, or related citations.
  • Running systematic-review search passes that need repeatable search strings.
  • Using NCBI E-utilities directly from Python, shell, or another HTTP client.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.