agentleFS
szzjayson25-hubszzjayson25-hub/nature-academic-skills/nature-literature-pipeline/SKILL.md

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

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
  1. Distinctive:

    Treat a source journal as metadata: preserve the source’s facts and structure.

    line 22
  2. Distinctive:

    Keep this skill’s original source-processing workflow.

    line 24
  3. Very specific:

    Only if journal fit or submission requirements are requested, read ../nature-shared/journal-formats/eswa.md.

    line 32
  4. Distinctive:

    After installing, tell your agent:

    line 67
  5. Distinctive:

    All domain-specific content is configurable:

    line 92

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 index

Quick 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 delivered

Architecture

The skill is organized in two layers:

LayerPurposeFiles
EngineScoring, classification, note templates, gap analysisreferences/scoring-system.md, references/gap-analysis.md, references/note-template.md
ApplicationDaily cron pipeline, delivery formatting, archival workflowreferences/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

ReferencePurpose
references/scoring-system.mdSix-dimension scoring rubric with weights, caps, and evaluation logic
references/gap-analysis.mdMethodology for identifying research gaps through systematic literature survey
references/note-template.mdStandardized literature note format with YAML frontmatter
references/push-format.mdDaily digest message template with field guidelines and example
references/cron-setup.mdCron job creation, verification, and manual fallback procedures
references/review-compilation-workflow.mdEnd-to-end workflow for concentrated literature review writing

Pitfalls

  1. Keyword drift: Review keywords monthly — research directions evolve
  2. Score inflation: Subagents may inflate scores; always validate arithmetic
  3. Duplicate creep: Classic papers will reappear; maintain a dedup index
  4. Wiki safety: Pipeline writes to raw/ only; wiki integration is manual
  5. Cron locality: Hermes cron is local, not cloud — machine must be running

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.