Academic Search, Router

Routing protocol

For local citation-file conversion with complete supplied records, load references/workflows/wf4-citation-file-mgmt.md and its format reference directly. Source lookup, API setup, and network preflight apply only when retrieval or verification is needed; do not require them for a requested offline conversion.

For a new task, load the core and matching resources below. Reuse already loaded guidance on follow-ups; load more only when the task needs it.

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.
• strict-other-citation-impact-audit, determine strict independent other-citations, build article-level citation metric tables, identify high-profile citers (academy members, presidents/deans, talent-award holders, fellows, field leaders), and extract how they cited the target paper.

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)