Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
yuan1z0825 avatar

Nature Academic Search

  • 5.4k installs
  • 33.4k repo stars
  • Updated August 4, 2026
  • yuan1z0825/nature-skills

nature-academic-search routes multi-step academic literature workflows across MCP sources with static core modules and dynamic workflow fragments.

About

Nature Academic Search is a router skill for coordinated literature research beyond a single MCP call. A static layer under static/ holds MCP tool inventory, source routing, and operational rules, while this router plus manifest.yaml selects one of five workflows: multi-source search, citation verification, MeSH strategy, citation file management, or reference management. Each invocation loads manifest.yaml, always reads core/tools.md and core/routing-and-ops.md, detects the workflow axis, then loads only the matching references/workflows fragment. Execution follows the T1 to T2 to T3 source fallback chain, reports tool failures, broadens terms on empty results, and falls back to manual metadata generation if scripts fail twice. Triggers include literature review, citation verification, .nbib or .ris or .bib conversion, BibTeX work, and Chinese phrases like 文献检索 or 引文核对. The router stays short on purpose; scope changes belong in fragments and references, not the top-level file.

  • Five routed workflows: search, citation verify, MeSH strategy, file mgmt, references.
  • Always loads core/tools.md and core/routing-and-ops.md before workflow fragments.
  • T1 to T2 to T3 source routing with MCP tool failure reporting and term broadening.
  • Supports .nbib, .ris, .bib conversion plus BibTeX and ID conversion tasks.
  • Loads only the workflow fragment needed per invocation to keep context lean.

Nature Academic Search by the numbers

  • 5,370 all-time installs (skills.sh)
  • +942 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #142 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

nature-academic-search capabilities & compatibility

Capabilities
workflow detection across five academic axes · mcp tool inventory and source tier routing · citation file conversion and reference managemen · mesh and pubmed search strategy building · on demand shared modules and script fallback
Works with
openai
Use cases
research · documentation
Runs
Local or remote
Pricing
Bring your own API key
From the docs

What nature-academic-search says it does

Do not try to apply the search logic from memory or from this router.
SKILL.md
npx skills add https://github.com/yuan1z0825/nature-skills --skill nature-academic-search

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs5.4k
repo stars33.4k
Security audit2 / 3 scanners passed
Last updatedAugust 4, 2026
Repositoryyuan1z0825/nature-skills

How do I run coordinated literature search, citation checks, or reference file workflows across multiple academic MCP tools?

Run multi-step academic literature workflows across PubMed, CrossRef, arXiv, Scopus, and ScienceDirect MCP tools with routed workflow fragments.

Who is it for?

Researchers and developers running literature reviews, citation verification, or reference file conversions via MCP.

Skip if: Skip for a single quick PubMed lookup when no multi-step workflow is needed.

When should I use this skill?

User needs literature search, citation verification, MeSH strategy, or .nbib/.ris/.bib management.

What you get

Correct workflow selection, source routing, and tool usage for academic search and citation management tasks.

  • Paper metadata results
  • Verified DOI records
  • RIS or EndNote citation exports

By the numbers

  • MCP server bundles 5 Python dependencies: mcp, requests, toml, lxml, and pybiliometrics
  • Supports multilingual triggers for literature search, DOI verification, and citation export

Files

SKILL.mdMarkdownGitHub ↗

Academic Search — Router

This skill is split into two layers:

  • A static layer under static/ that holds versioned, reusable content fragments (the MCP tool inventory and shared modules, and source routing plus operational rules).
  • A dynamic layer (this file plus manifest.yaml) that detects which workflow the user needs and loads that workflow, reaching for shared modules and scripts only when a step needs them.

Do not try to apply the search logic from memory or from this router. Always load fragments from disk as described below.

Routing protocol

Follow these five steps every time the skill is invoked.

1. Load the manifest and the core layer

Read manifest.yaml. It declares the workflow axis, the allowed values, and the file paths each value maps to.

Also read every file listed under always_load:

  • static/core/tools.md — the MCP tool inventory (core search, extended search, PubMed utilities) and the shared-module map.
  • static/core/routing-and-ops.md — the T1→T2→T3 source routing quick guide, environment setup, error handling, and limitations.

2. Detect the workflow

Map the user's need to one or more workflow values:

  • multi-source-search — find literature across sources.
  • citation-verification — verify citations extracted from a document.
  • mesh-strategy — build a MeSH/PubMed search strategy.
  • citation-file-mgmt — convert/manage .nbib/.ris/.bib files.
  • reference-mgmt — BibTeX, related-article discovery, ID conversion.

A combined request (for example search then export) may need more than one. State the detected workflow(s) in one short line before proceeding.

3. Load the matching workflow fragment(s)

Read the file mapped for each detected workflow (under references/workflows/). Do not read every workflow. Each workflow file links to the shared modules it needs.

4. Run the workflow using the loaded material

Apply the loaded material in this order:

1. Core tools and routing (core/tools.md, core/routing-and-ops.md) — which MCP tool for which need, and the T1→T2→T3 fallback chain that is the standard execution order across all workflows. 2. The workflow fragment — its specific steps. 3. Shared modules and scripts on demand (dedup, citation parser, search strategy, RIS/BibTeX format, format converter).

Report specific tool failures and continue with remaining tools; broaden terms when there are no results; fall back to manual generation from MCP-fetched metadata if a script fails twice.

5. Reach for references only when needed

The files under references/ (and scripts/) are deep references, not defaults. Open them on demand per the references.on_demand table in the manifest — for example references/source-tiers.md for the full reliability classification, references/dedup-engine.md / references/citation-parser.md / references/search-strategy.md / references/ris-bibtex-format.md for the shared modules, and scripts/academic_search.py (no-MCP fallback discovery search) / scripts/format-converter.py / scripts/preflight.py for the tooling.

Why this split

  • The static layer is versioned and reviewable; the workflow files and shared modules were already factored this way.
  • The dynamic layer keeps each invocation cheap: only the workflow the user needs enters context, instead of all five plus every module.
  • The router itself is short on purpose. Update fragments and references, not this file, when adding scope.
  • This structure mirrors the other nature-* skills (nature-writing, nature-polishing, nature-reader, nature-paper2ppt, nature-figure, nature-citation, nature-response, nature-data).

Related skills

Forks & variants (1)

Nature Academic Search has 1 known copy in the catalog totaling 2 installs. They canonicalize to this original listing.

FAQ

Must I load every workflow file?

No. Detect the workflow from the user request and load only the mapped references/workflows fragment.

What is the standard source order?

Follow the T1 to T2 to T3 fallback chain documented in core/routing-and-ops.md across all workflows.

What if an MCP script fails twice?

Fall back to manual generation from MCP-fetched metadata and continue with remaining tools.

Is Nature Academic Search safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

AI & Agent Buildingresearchautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.