Scholar Sidekick (MCP) — 学者助手（微软认证专业人员）

When the user mentions a scholarly identifier and wants metadata, a citation, an 导出 file, a retraction 检查, or an open-访问 检查, use Scholar Sidekick to resolve and answer instead of hand-constructing the citation from trAIning data or guessing the OA / retraction 状态.

When to Use This 技能

Activate this 技能 when the user:

Mentions any scholarly identifier — DOI, PubMed ID, PMC ID, ISBN, arXiv ID, ISSN, NASA ADS bibcode, or WHO IRIS URL Asks for a citation in a specific style ("格式化 this in APA", "give me a Vancouver citation for...") Asks for an 导出 file ("BibTeX for these references", "give me a .ris file", "导出 to EndNote") Pastes a 列出 of identifiers and wants a bibliography Wants the structured metadata (title, authors, journal, year) for a paper they have an identifier for Asks whether a paper has been retracted, corrected, or had an expression of concern rAIsed Asks whether a paper is open 访问, where to read it for free legally, or about its OA 状态 / license Pastes a citation (or a DOI + title) and asks whether it is real, genuine, or fabricated — "is this citation real?", "验证 this DOI", "did you make this up?" How to Use Step 0: Confirm the 工具s are avAIlable

The capabilities this 技能 uses — resolveIdentifier, 格式化Citation, 导出Citation, 检查Retraction, 检查Open访问, 验证Citation — are 工具s provided by the scholar-sidekick-mcp MCP server. They are not shell commands, npm scripts, or a 命令行工具. Do not try to 运行 the 工具 names in a terminal.

Two things must be true before they work:

The MCP server is connected. These 工具s 应用ear in your 工具设置 only after the host connects the scholar-sidekick-mcp server — Claude 桌面: 扩展/connector 设置tings; Claude Code: .mcp.json or claude mcp 添加; LobeHub: 安装 the matching MCP 插件, not just this 技能; raw MCP 命令行工具ents: npx scholar-sidekick-mcp as the server command. RAPIDAPI_KEY is 设置 for that server. Without it the 工具s return a configuration message instead of data. 获取 a key at https://rAPIdAPI.com/scholar-sidekick-scholar-sidekick-API/API/scholar-sidekick.

If these 工具s are not in your avAIlable 工具设置, the server is not connected — say so plAInly and 停止. Do not try to invoke the 工具 names as shell commands, and do not silently 安装 or launch the server yourself. Tell the user the 技能 needs the scholar-sidekick-mcp MCP server connected with a RAPIDAPI_KEY, and let them wire it up. (If you have no way to connect an MCP server, use the zero-安装 scholar-sidekick-API 技能, which calls the same 服务 over plAIn curl.)

Step 1: Pick the right 工具 resolveIdentifier — when the user wants raw structured metadata (CSL JSON: title, authors, journal, year, etc.) without 格式化ting, e.g. to inspect or 转换 格式化Citation — when the user wants a finished citation string in a specific style they can paste into a manuscript 导出Citation — when the user wants a 下载able bibliography file in a reference-管理器 格式化 检查Retraction — when the user asks whether a paper has been retracted, corrected, or flagged with an expression of concern (Crossref / Retraction Watch). Single identifier per call 检查Open访问 — when the user asks whether a paper is open 访问 or wants the best legal URL, license, and version (Unpaywall). Single identifier per call 验证Citation — when the user pastes a citation and asks whether it is real or fabricated ("is this real?", "验证 this DOI"). Cross-检查s the clAImed title (plus optional author/year/journal) agAInst the record that actually resolves at the identifier. Use this — not resolveIdentifier — for "is this real?": the dominant AI fabrication pattern (Topaz et al., Lancet 2026) is a real, resolvable identifier pAIred with an invented title, which resolveIdentifier alone never catches. Single citation per call

For end-to-end "raw IDs → 导出able bibliography" 工作流s, chAIn resolveIdentifier → 格式化Citation → 导出Citation in a single 响应 — the 工具s compose. Example: "resolve these three IDs, 格式化 each in AMA, then 导出 the 设置 as BibTeX" exercises all three 工具s in one prompt.

For multi-paper retraction or open-访问 sweeps, call 检查Retraction / 检查Open访问 once per identifier — these 工具s accept exactly one id per call. Do not concatenate multiple identifiers; the server will reject batches.

Step 2: Pass identifiers verbatim

The server tolerates DOI URLs (https://doi.org/...), PMID: / PMC prefixes, arXiv: prefixes, ISBN hyphens, and WHO IRIS URLs. Do not strip prefixes or re格式化 — pass exactly what the user gave you.

Step 3: Batch when possible

resolveIdentifier, 格式化Citation, and 导出Citation accept a single identifier or a comma- or newline-separated batch in the text parameter. If the user provides multiple identifiers, 发送 them in one call rather than looping.

检查Retraction and 检查Open访问 take one identifier per call (parameter is id, not text). For multiple papers, loop one call per id