nature-literature-pipeline
Skill0 starsChanged 2 months agoMITView on GitHub
Complete automated literature discovery pipeline: multi-source search → six-dimension scoring → fine reading → formatted delivery → archival. Combines a configurable engine with daily cron-driven application layer. Works with Feishu, Telegram, or any messaging platform.
4 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- Luooops/skillsedited, first seen Oct 13, 2026
- Yuan1z0825/nature-skillsedited, first seen Aug 31, 2026
- Delagong950/nature-skillstheir own version, first seen Jul 6, 2026
- vcis-wangchenxu/agent_nature-skillstheir own version, first seen Jul 1, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- Yuan1z0825/nature-skills★ 54k99% same
- Luooops/skills★ 199% same
Wrote their own version · 2
- 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-academic-searchSkill
- nature-citationSkill
- nature-dataSkill
- nature-downloaderSkill
- nature-experiment-logSkill
- nature-figure-prompt-onlySkill
- nature-figureSkill
- nature-image2pptSkill
- 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
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Treat a source journal as metadata: preserve the source’s facts and structure.
- Distinctive: line 24
Keep this skill’s original source-processing workflow.
- Very specific: line 32
Only if journal fit or submission requirements are requested, read ../nature-shared/journal-formats/eswa.md.
- Distinctive: line 67
After installing, tell your agent:
- Distinctive: line 92
All domain-specific content is configurable:
“Common” is measured: kept by at least 6 in 10 of the 4 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
Nature Literature Pipeline
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.
Apply an ESWA venue filter only when the user requests it; verify full
journal identity in metadata and preserve the existing discovery/delivery scope.
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.
A complete, production-tested automated literature pipeline. Not just "search for papers" — it's a structured engine that scores, classifies, reads, delivers, and archives research papers daily.
What It Does
Cron (daily trigger, e.g. 08:30)
│
├─ ① SEARCH (30 candidates)
│ arXiv / OpenAlex / Crossref / Semantic Scholar (auto-degradation)
│
├─ ② COARSE FILTER (30 → 5)
│ Six-dimension scoring: topic match × 35 + methodology × 20
│ + journal quality × 15 + network relevance × 10
│ + applied value × 10 + archival value × 10
│
├─ ③ FINE READ (top 5)
│ Abstract-level or full-text. Source level tagged:
│ Full-text / Abstract only / Metadata only
│
├─ ④ DELIVER
│ Formatted digest to Feishu/Telegram/etc.
│ 🏅 rank | title | journal | ⭐ score | 💡 one-liner
│ 🔬 methods | 📊 key results | 🧭 commentary
│
└─ ⑤ ARCHIVE
DOI/arXiv de-dup → classify → write notes → update indexQuick Start
After installing, tell your agent:
My research area is [X], keywords: [Y], deliver to [feishu group name], archive to [path]The agent will configure keywords, delivery target, and archive path automatically.
Then set up a daily cron job:
Set up a daily literature push at 08:30 Beijing time, 30 candidates, top 5 deliveredArchitecture
The skill is organized in two layers:
| Layer | Purpose | Files |
| Engine | Scoring, classification, note templates, gap analysis | references/scoring-system.md, references/gap-analysis.md, references/note-template.md |
| Application | Daily cron pipeline, delivery formatting, archival workflow | references/push-format.md, references/cron-setup.md, references/review-compilation-workflow.md |
Configuration
All domain-specific content is configurable:
- Keywords — your research keywords (English + Chinese)
- Scoring weights — adjust the six dimensions for your field
- Classification rules — define your own tier system (A-E or custom)
- Delivery target — Feishu group, Telegram channel, email, etc.
- Archive path — local vault/wiki directory
A config template is provided in templates/literature-push-template.md.
Built-in Safeguards
- Score validation: Each dimension capped, total recalculated — no 11/10 allowed
- Triple de-duplication: DOI / arXiv ID / OpenAlex ID
- Graceful degradation: Semantic Scholar down → auto-switch to OpenAlex + Crossref + arXiv
- Read-only archive: Daily pipeline writes to
raw/literature directory only; never modifies wiki/knowledge base without user approval
Related Skills
nature-academic-search— ad-hoc literature search (complementary; this skill adds structured daily automation)nature-citation— CNS citation export (for importing pipeline discoveries into manuscripts)zotero— library management (for long-term organization of pipeline outputs)arxiv— arXiv API (used as a search source)
References
| Reference | Purpose |
references/scoring-system.md | Six-dimension scoring rubric with weights, caps, and evaluation logic |
references/gap-analysis.md | Methodology for identifying research gaps through systematic literature survey |
references/note-template.md | Standardized literature note format with YAML frontmatter |
references/push-format.md | Daily digest message template with field guidelines and example |
references/cron-setup.md | Cron job creation, verification, and manual fallback procedures |
references/review-compilation-workflow.md | End-to-end workflow for concentrated literature review writing |
Pitfalls
- Keyword drift: Review keywords monthly — research directions evolve
- Score inflation: Subagents may inflate scores; always validate arithmetic
- Duplicate creep: Classic papers will reappear; maintain a dedup index
- Wiki safety: Pipeline writes to
raw/only; wiki integration is manual - Cron locality: Hermes cron is local, not cloud — machine must be running
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.

