nature-academic-search
Skill0 starsChanged 2 months agoMITView on GitHub
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引用、文章引用表、 指定文章引用数、严格他引数、整理成表格.
8 other projects use a version of this, 5 of them edited.
Adopted by
Most recently taken up by
- denghuipan/nature-portfolio-skillsedited, first seen Nov 15, 2026
- dragonadam/nature-skillsedited, first seen Oct 25, 2026
- Luooops/skillsedited, first seen Oct 13, 2026
- yanjumlinnb-boop/nature-skillsedited, first seen Oct 8, 2026
- Yuan1z0825/nature-skillsedited, first seen Aug 31, 2026
- wp-a/nature-academic-searchtheir own version, first seen Aug 29, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 5
- Yuan1z0825/nature-skills★ 54k76% same
- yanjumlinnb-boop/nature-skills★ 1487% same
- dragonadam/nature-skills★ 492% same
- denghuipan/nature-portfolio-skills★ 287% same
- Luooops/skills★ 176% same
Wrote their own version · 3
- wp-a/nature-academic-search★ 259same name
- Delagong950/nature-skills★ 4same name
- vcis-wangchenxu/agent_nature-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- journal-style-learnSkill
- nature-citationSkill
- nature-dataSkill
- nature-downloaderSkill
- nature-experiment-logSkill
- nature-figure-prompt-onlySkill
- nature-figureSkill
- nature-image2pptSkill
- nature-literature-pipelineSkill
- nature-paper2pptSkill
- nature-paper-cardSkill
- nature-paper-to-patentSkill
- nature-polishingSkill
- researchwriteSkill
- nature-readerSkill
- nature-ref-verifierSkill
- nature-responseSkill
- nature-reviewerSkill
- nature-sharedSkill
- nature-statisticsSkill
- nature-writingSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Treat a source journal as metadata: preserve the source’s facts and structure.
- Distinctive: line 26
Keep this skill’s original source-processing workflow.
- Very specific: line 34
Only if journal fit or submission requirements are requested, read ../nature-shared/journal-formats/eswa.md.
- Distinctive: line 44
Do not try to apply the search logic from memory or from this router.
- Distinctive: line 48
Follow these five steps every time the skill is invoked.
- Very specific: line 52
Read manifest.yaml. It declares the workflow axis, the allowed values, and the file paths each value maps to.
- Very specific: line 74
Read the file mapped for each detected workflow (under references/workflows/).
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 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/.bibfiles.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)
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:
- 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. - The workflow fragment — its specific steps.
- 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 six 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).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

