Pubmed Database

PubMed Database

Overview

This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/pubmed-database from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

PubMed Database

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Core Capabilities, Tips and Best Practices, Limitations and Considerations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Searching for biomedical or life sciences research articles
• Constructing complex search queries with Boolean operators, field tags, or MeSH terms
• Conducting systematic literature reviews or meta-analyses
• Accessing PubMed data programmatically via the E-utilities API
• Finding articles by specific criteria (author, journal, publication date, article type)
• Retrieving citation information, abstracts, or full-text articles

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Identify key concepts and synonyms
2. Construct query with Boolean operators and field tags
3. Review initial results and refine query
4. Apply filters (date, article type, language)
5. Export results for analysis
6. Define research question using PICO framework
7. Identify all relevant MeSH terms and synonyms

Imported Workflow Notes

Imported: Common Workflows

Workflow 1: Basic Literature Search

1. Identify key concepts and synonyms
2. Construct query with Boolean operators and field tags
3. Review initial results and refine query
4. Apply filters (date, article type, language)
5. Export results for analysis

Workflow 2: Systematic Review Search

1. Define research question using PICO framework
2. Identify all relevant MeSH terms and synonyms
3. Construct comprehensive search strategy
4. Search multiple databases (include PubMed)
5. Document search strategy and date
6. Export results for screening and review

Workflow 3: Programmatic Data Extraction

1. Design search query and test in web interface
2. Implement search using ESearch API
3. Use history server for large result sets
4. Retrieve detailed records with EFetch
5. Parse XML/JSON responses
6. Store data locally with caching
7. Implement rate limiting and error handling

Workflow 4: Citation Discovery

1. Start with known relevant article
2. Use Similar Articles to find related work
3. Check citing articles (when available)
4. Explore MeSH terms from relevant articles
5. Construct new searches based on discoveries
6. Use ELink to find related database entries

Workflow 5: Ongoing Literature Monitoring

1. Construct comprehensive search query
2. Test and refine query for precision
3. Save search to My NCBI account
4. Set up email alerts for new matches
5. Create RSS feed for feed reader monitoring
6. Review new articles regularly

Imported: Overview

PubMed is the U.S. National Library of Medicine's comprehensive database providing free access to MEDLINE and life sciences literature. Construct advanced queries with Boolean operators, MeSH terms, and field tags, access data programmatically via E-utilities API for systematic reviews and literature analysis.

Imported: Core Capabilities

1. Advanced Search Query Construction

Construct sophisticated PubMed queries using Boolean operators, field tags, and specialized syntax.

Basic Search Strategies:

• Combine concepts with Boolean operators (AND, OR, NOT)
• Use field tags to limit searches to specific record parts
• Employ phrase searching with double quotes for exact matches
• Apply wildcards for term variations
• Use proximity searching for terms within specified distances

Example Queries:

# Recent systematic reviews on diabetes treatment
diabetes mellitus[mh] AND treatment[tiab] AND systematic review[pt] AND 2023:2024[dp]

# Clinical trials comparing two drugs
(metformin[nm] OR insulin[nm]) AND diabetes mellitus, type 2[mh] AND randomized controlled trial[pt]

# Author-specific research
smith ja[au] AND cancer[tiab] AND 2023[dp] AND english[la]

When to consult search_syntax.md:

• Need comprehensive list of available field tags
• Require detailed explanation of search operators
• Constructing complex proximity searches
• Understanding automatic term mapping behavior
• Need specific syntax for date ranges, wildcards, or special characters

Grep pattern for field tags: \[au\]|\[ti\]|\[ab\]|\[mh\]|\[pt\]|\[dp\]

2. MeSH Terms and Controlled Vocabulary

Use Medical Subject Headings (MeSH) for precise, consistent searching across the biomedical literature.

MeSH Searching:

• [mh] tag searches MeSH terms with automatic inclusion of narrower terms
• [majr] tag limits to articles where the topic is the main focus
• Combine MeSH terms with subheadings for specificity (e.g., diabetes mellitus/therapy[mh])

Common MeSH Subheadings:

• /diagnosis - Diagnostic methods
• /drug therapy - Pharmaceutical treatment
• /epidemiology - Disease patterns and prevalence
• /etiology - Disease causes
• /prevention & control - Preventive measures
• /therapy - Treatment approaches

Example:

# Diabetes therapy with specific focus
diabetes mellitus, type 2[mh]/drug therapy AND cardiovascular diseases[mh]/prevention & control

3. Article Type and Publication Filtering

Filter results by publication type, date, text availability, and other attributes.

Publication Types (use [pt] field tag):

• Clinical Trial
• Meta-Analysis
• Randomized Controlled Trial
• Review
• Systematic Review
• Case Reports
• Guideline

Date Filtering:

• Single year: 2024[dp]
• Date range: 2020:2024[dp]
• Specific date: 2024/03/15[dp]

Text Availability:

• Free full text: Add AND free full text[sb] to query
• Has abstract: Add AND hasabstract[text] to query

Example:

# Recent free full-text RCTs on hypertension
hypertension[mh] AND randomized controlled trial[pt] AND 2023:2024[dp] AND free full text[sb]

4. Programmatic Access via E-utilities API

Access PubMed data programmatically using the NCBI E-utilities REST API for automation and bulk operations.

Core API Endpoints:

1. ESearch - Search database and retrieve PMIDs
2. EFetch - Download full records in various formats
3. ESummary - Get document summaries
4. EPost - Upload UIDs for batch processing
5. ELink - Find related articles and linked data

Basic Workflow:

import requests

# Step 1: Search for articles
base_url = "https://eutils.ncbi.nlm.nih.gov/entrez/eutils/"
search_url = f"{base_url}esearch.fcgi"
params = {
    "db": "pubmed",
    "term": "diabetes[tiab] AND 2024[dp]",
    "retmax": 100,
    "retmode": "json",
    "api_key": "YOUR_API_KEY"  # Optional but recommended
}
response = requests.get(search_url, params=params)
pmids = response.json()["esearchresult"]["idlist"]

# Step 2: Fetch article details
fetch_url = f"{base_url}efetch.fcgi"
params = {
    "db": "pubmed",
    "id": ",".join(pmids),
    "rettype": "abstract",
    "retmode": "text",
    "api_key": "YOUR_API_KEY"
}
response = requests.get(fetch_url, params=params)
abstracts = response.text

Rate Limits:

• Without API key: 3 requests/second
• With API key: 10 requests/second
• Always include User-Agent header

Best Practices:

• Use history server (usehistory=y) for large result sets
• Implement batch operations via EPost for multiple UIDs
• Cache results locally to minimize redundant calls
• Respect rate limits to avoid service disruption

When to consult api_reference.md:

• Need detailed endpoint documentation
• Require parameter specifications for each E-utility
• Constructing batch operations or history server workflows
• Understanding response formats (XML, JSON, text)
• Troubleshooting API errors or rate limit issues

Grep pattern for API endpoints: esearch|efetch|esummary|epost|elink|einfo

5. Citation Matching and Article Retrieval

Find articles using partial citation information or specific identifiers.

By Identifier:

# By PMID
12345678[pmid]

# By DOI
10.1056/NEJMoa123456[doi]

# By PMC ID
PMC123456[pmc]

Citation Matching (via ECitMatch API): Use journal name, year, volume, page, and author to find PMIDs:

Format: journal|year|volume|page|author|key|
Example: Science|2008|320|5880|1185|key1|

By Author and Metadata:

# First author with year and topic
smith ja[1au] AND 2023[dp] AND cancer[tiab]

# Journal, volume, and page
nature[ta] AND 2024[dp] AND 456[vi] AND 123-130[pg]

6. Systematic Literature Reviews

Conduct comprehensive literature searches for systematic reviews and meta-analyses.

PICO Framework (Population, Intervention, Comparison, Outcome): Structure clinical research questions systematically:

# Example: Diabetes treatment effectiveness
# P: diabetes mellitus, type 2[mh]
# I: metformin[nm]
# C: lifestyle modification[tiab]
# O: glycemic control[tiab]

diabetes mellitus, type 2[mh] AND
(metformin[nm] OR lifestyle modification[tiab]) AND
glycemic control[tiab] AND
randomized controlled trial[pt]

Comprehensive Search Strategy:

# Include multiple synonyms and MeSH terms
(disease name[tiab] OR disease name[mh] OR synonym[tiab]) AND
(treatment[tiab] OR therapy[tiab] OR intervention[tiab]) AND
(systematic review[pt] OR meta-analysis[pt] OR randomized controlled trial[pt]) AND
2020:2024[dp] AND
english[la]

Search Refinement:

1. Start broad, review results
2. Add specificity with field tags
3. Apply date and publication type filters
4. Use Advanced Search to view query translation
5. Combine search history for complex queries

When to consult common_queries.md:

• Need example queries for specific disease types or research areas
• Require templates for different study designs
• Looking for population-specific query patterns (pediatric, geriatric, etc.)
• Constructing methodology-specific searches
• Need quality filters or best practice patterns

Grep pattern for query examples: diabetes|cancer|cardiovascular|clinical trial|systematic review

7. Search History and Saved Searches

Use PubMed's search history and My NCBI features for efficient research workflows.

Search History (via Advanced Search):

• Maintains up to 100 searches
• Expires after 8 hours of inactivity
• Combine previous searches using # references
• Preview result counts before executing

Example:

#1: diabetes mellitus[mh]
#2: cardiovascular diseases[mh]
#3: #1 AND #2 AND risk factors[tiab]

My NCBI Features:

• Save searches indefinitely
• Set up email alerts for new matching articles
• Create collections of saved articles
• Organize research by project or topic

RSS Feeds: Create RSS feeds for any search to monitor new publications in your area of interest.

8. Related Articles and Citation Discovery

Find related research and explore citation networks.

Similar Articles Feature: Every PubMed article includes pre-calculated related articles based on:

• Title and abstract similarity
• MeSH term overlap
• Weighted algorithmic matching

ELink for Related Data:

# Find related articles programmatically
elink.fcgi?dbfrom=pubmed&db=pubmed&id=PMID&cmd=neighbor

Citation Links:

• LinkOut to full text from publishers
• Links to PubMed Central free articles
• Connections to related NCBI databases (GenBank, ClinicalTrials.gov, etc.)

9. Export and Citation Management

Export search results in various formats for citation management and further analysis.

Export Formats:

• .nbib files for reference managers (Zotero, Mendeley, EndNote)
• AMA, MLA, APA, NLM citation styles
• CSV for data analysis
• XML for programmatic processing

Clipboard and Collections:

• Clipboard: Temporary storage for up to 500 items (8-hour expiration)
• Collections: Permanent storage via My NCBI account

Batch Export via API:

# Export citations in MEDLINE format
efetch.fcgi?db=pubmed&id=PMID1,PMID2&rettype=medline&retmode=text

Examples

Example 1: Ask for the upstream workflow directly

Use @pubmed-database to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @pubmed-database against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @pubmed-database for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @pubmed-database using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/pubmed-database, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Imported Reference Notes

Imported: Working with Reference Files

This skill includes three comprehensive reference files in the references/ directory:

references/api_reference.md

Complete E-utilities API documentation including all nine endpoints, parameters, response formats, and best practices. Consult when:

• Implementing programmatic PubMed access
• Constructing API requests
• Understanding rate limits and authentication
• Working with large datasets via history server
• Troubleshooting API errors

references/search_syntax.md

Detailed guide to PubMed search syntax including field tags, Boolean operators, wildcards, and special characters. Consult when:

• Constructing complex search queries
• Understanding automatic term mapping
• Using advanced search features (proximity, wildcards)
• Applying filters and limits
• Troubleshooting unexpected search results

references/common_queries.md

Extensive collection of example queries for various research scenarios, disease types, and methodologies. Consult when:

• Starting a new literature search
• Need templates for specific research areas
• Looking for best practice query patterns
• Conducting systematic reviews
• Searching for specific study designs or populations

Reference Loading Strategy: Load reference files into context as needed based on the specific task. For brief queries or basic searches, the information in this SKILL.md may be sufficient. For complex operations, consult the appropriate reference file.

Imported: Support Resources

• PubMed Help: https://pubmed.ncbi.nlm.nih.gov/help/
• E-utilities Documentation: https://www.ncbi.nlm.nih.gov/books/NBK25501/
• NLM Help Desk: 1-888-FIND-NLM (1-888-346-3656)
• Technical Support: vog.hin.mln.ibcn@seitilitue
• Mailing List: utilities-announce@ncbi.nlm.nih.gov

Imported: Tips and Best Practices

Search Strategy

• Start broad, then narrow with field tags and filters
• Include synonyms and MeSH terms for comprehensive coverage
• Use quotation marks for exact phrases
• Check Search Details in Advanced Search to verify query translation
• Combine multiple searches using search history

API Usage

• Obtain API key for higher rate limits (10 req/sec vs 3 req/sec)
• Use history server for result sets > 500 articles
• Implement exponential backoff for rate limit handling
• Cache results locally to minimize redundant requests
• Always include descriptive User-Agent header

Quality Filtering

• Prefer systematic reviews and meta-analyses for synthesized evidence
• Use publication type filters to find specific study designs
• Filter by date for most recent research
• Apply language filters as appropriate
• Use free full text filter for immediate access

Citation Management

• Export early and often to avoid losing search results
• Use .nbib format for compatibility with most reference managers
• Create My NCBI account for permanent collections
• Document search strategies for reproducibility
• Use Collections to organize research by project

Imported: Limitations and Considerations

Database Coverage

• Primarily biomedical and life sciences literature
• Pre-1975 articles often lack abstracts
• Full author names available from 2002 forward
• Non-English abstracts available but may default to English display

Search Limitations

• Display limited to 10,000 results maximum
• Search history expires after 8 hours of inactivity
• Clipboard holds max 500 items with 8-hour expiration
• Automatic term mapping may produce unexpected results

API Considerations

• Rate limits apply (3-10 requests/second)
• Large queries may time out (use history server)
• XML parsing required for detailed data extraction
• API key recommended for production use

Access Limitations

• PubMed provides citations and abstracts (not always full text)
• Full text access depends on publisher, institutional access, or open access status
• LinkOut availability varies by journal and institution
• Some content requires subscription or payment