pm-navigate-pages

Navigate PubMed search result pages and switch between date and relevance sorting.

19|6|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/cookjohn/pm-skills --skill pm-navigate-pages
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-navigate-pages
Source: https://github.com/cookjohn/pm-skills/tree/main/skills/pm-navigate-pages
Command: npx skills add https://github.com/cookjohn/pm-skills --skill pm-navigate-pages

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Navigate PubMed search results and adjust ordering without manually rebuilding URLs or re-running full searches.

Core Features & Use Cases

  • Page navigation: go to the next/previous page or jump to a specific page number.
  • Sort control: switch between date-relevance sorting to refine results.
  • Context requirement: relies on an active pm-search context (query, page, size, total) to function.

Quick Start

After performing a pm-search, invoke the navigate command with next, previous, page N, or sort by date to update the results.

Frequently Asked Questions about pm-navigate-pages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I navigate PubMed search results to the next page without re-running the query?

To navigate PubMed search results without re-running the query, use this Skill to update pagination after a prior pm-search. It leverages esearch to fetch the specific page you request using the existing search context.

Can I change the sort order of PubMed results between date and relevance?

Yes, you can change the sort order of PubMed results between date and relevance. This Skill updates the sort parameter within your active pm-search context, fetching reordered summaries via esummary without manual URL rebuilding.

Do I need an active pm-search context to jump to a specific page in PubMed?

Yes, an active pm-search context is required to jump to a specific page. This Skill relies on pre-existing query, page, and size parameters from a prior pm-search to calculate and fetch the correct PubMed results.

What is the best way to update PubMed pagination when analyzing large result sets?

The best way to update PubMed pagination for large result sets is using this Skill to jump to specific page numbers. It utilizes the total result count from the initial search context to navigate pages seamlessly via esearch.

Why does PubMed pagination fail when I try to navigate without a search context?

PubMed pagination fails without a search context because this Skill requires pre-existing query, page, and size parameters from a prior pm-search to function. Without this context, it cannot construct the esearch request to fetch updated results.

How does esummary work when reordering PubMed search results?

When reordering PubMed search results, esummary fetches the updated summaries based on the new sort order or page number. The Skill uses esearch to define the updated result set, then esummary retrieves the corresponding article data.