인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
생산성 및 협업 · SKILL.md

nature-literature-pipeline

nature-literature-pipeline

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.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill 문서

GitHub

name: nature-literature-pipeline description: | 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. license: MIT metadata: author: Jiahao8595 hermes: tags: [research, literature, pipeline, cron, automation, discovery] related_skills: [nature-academic-search, nature-citation, arxiv, zotero]

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
저장한 Skills