← ClaudeAtlas

nature-academic-searchlisted

Multi-source literature search, citation verification, strict independent other-citation audits, article-level citation metric tables, influential citer profiling with citation-context extraction, MeSH search strategy, citation file management (.nbib/.ris/.bib conversion), and reference management (BibTeX, related articles, ID conversion) via MCP tools (PubMed, CrossRef, arXiv, Scopus, ScienceDirect). Use for coordinated literature workflows beyond one MCP call, including 文献检索、 查文献、找文献、文献综述检索、查论文、引文核对、参考文献管理、文献去重、 严格他引、他引判定、排除自引、谁引用了我的文章、引用我的文章的人有没有大牛、 院士引用、校长引用、院长引用、杰青引用、长江学者引用、Fellow引用、文章引用表、 指定文章引用数、严格他引数、整理成表格.
szzjayson25-hub/nature-academic-skills · ★ 0 · AI & Automation · score 70
Install: claude install-skill szzjayson25-hub/nature-academic-skills
# Academic Search — Router ## Additional configured journals For Applied Soft Computing (ASC), Engineering Applications of Artificial Intelligence (EAAI), ISA Transactions, Knowledge-Based Systems (KBS), Measurement, Neurocomputing, or IEEE Transactions on Reliability, use `../nature-shared/journal-formats/index.md` to resolve the exact journal. Treat a source journal as metadata: preserve the source’s facts and structure. Load submission constraints only when target formatting or fit is requested. Keep this skill’s original source-processing workflow. ## ESWA journal context Recognize Expert Systems with Applications (`ESWA`, `Expert Syst. Appl.`) as the same journal, case-insensitively; distinguish similarly named titles. For an explicit ESWA-only search, verify the full journal title or ISSN in publisher/DOI metadata. An ESWA submission target alone is not a source filter. Only if journal fit or submission requirements are requested, read `../nature-shared/journal-formats/eswa.md`; otherwise keep this workflow source-oriented without loading submission rules. 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