paper-digest

Solid

Produce a content/knowledge digest of ONE paper for fast absorption of its full content — not a quality critique. Use when the user wants to "整理內容", "快速吸收", "知識整理", "內容平讀", or when /paper-sync dispatches a 📚內容 pick. The digest reorganizes the paper's full text into a teaching-style structured note (structure routed by paper type) plus self-test review cards pushed to the 複習頁 (configured `review_site.url`). REQUIRES full text: no full text → STOP and report 缺全文, never produce an abstract-only digest. NOT a critical appraisal (that is /paper-review) and NOT a multi-paper synthesis.

Code & Development 39 stars 8 forks Updated 2 weeks ago MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
53
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Paper Digest — 單篇論文內容��理(快速吸收) ## What this is (and is NOT) `/paper-review` answers **「這篇可不可信、做得好不好」**. `/paper-digest` answers **「這篇講了什麼、我怎麼最快把全部內容吸收進腦袋」**. It is for papers read as **content / knowledge material**(綜論、技術介紹、機制整理、指引). The two are independent and can both run on one paper (combined note). A digest additionally feeds the **複習迴圈**: it generates self-test cards that go to the review web page so learning doesn't end at "note written". Tone, language, and clinical framing are driven by `${persona}` (see Configuration). Follow vault note rules (Tab indent, `> [!type]` callouts, `${persona.highlight_style}` for cut-offs, no code blocks for clinical content). ## Configuration (read FIRST, every run) Read **`config.yaml`** in the sibling `paper-review/` skill directory (shared config; copy `config.example.yaml` → `config.yaml` on first setup). Keys this skill uses: `${vault.papers_dir}`, `${vault.medicine_dir}`, `${vault.inbox_note}`, `${vault.daily_section}`, `${review_site.url}`, `${review_site.push_script}`, `${persona}`. Substitute every `${...}` with the config value; a blank value means "skip that route" (e.g. empty `review_site.push_script` → no card push). ## Input DOI / PMID / title / PDF path / pasted full text. Optional flags: - `--into <note path>` — instead of creating a standalone note, **prepend** the digest as a `## 內容整理(快速吸收)` section into an existing note (used by /paper-sync when both 🔬+📚 picked, so content sits above the appraisal in on...

Details

Author
drpwchen
Repository
drpwchen/paper-review-and-digest
Created
2 months ago
Last Updated
2 weeks ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

paper-review

Deep single-paper academic analysis — journal credibility, author profiling, reference verification, citation impact, and critical appraisal. Like a teaching hospital journal club report. Use this skill whenever the user wants to deeply review, evaluate, or dissect a single academic paper, prepare a journal club presentation, verify a paper's references, check an author's track record, or do any thorough paper-level analysis. Also trigger when the user says "review this paper", "深度評讀", "journal club", "論文評讀", "幫我看這篇", or provides a DOI/PMID asking for analysis. NOT for multi-paper systematic reviews or standalone evidence grading.

39 Updated 2 weeks ago
drpwchen
AI & Automation Listed

paper-analyzer

Read an academic paper (PDF, arXiv link, pasted text, or DOI/title) and produce a complete paper-study package — full paragraph-by-paragraph Chinese translation, plus structured Chinese & English summaries, plus extracted figures / tables / algorithms / listings saved into per-paper subfolders following the paper's own numbering (Figure 1, Table 1, Algorithm 1, etc.). Detects the paper's academic field, confirms a domain glossary with the user, and preserves field-appropriate English terminology in both the Chinese translation and summary. Use this skill whenever the user shares a paper, an arXiv URL, a DOI, a paper title, or pastes a chunk of academic text and asks to "read / summarize / translate / analyze / 解读 / 翻译 / 总结 / 精读" it — even if the user does not explicitly say "use paper-analyzer". Also trigger when the user wants to compare or do a literature review starting from a single paper.

3 Updated 1 months ago
JavaLyHn
Data & Documents Listed

paper-eli5

Rewrite someone else's research paper into plain English — section by section, paragraph by paragraph, 1:1. Same headings, same paragraph order; nothing summarized, merged, dropped, or reordered; only the language changes (smart-newcomer register, jargon translated on first use). Accepts a local PDF/markdown/text path, an arXiv URL or bare ID, or any other web URL. Equations, tables, and inline math stay verbatim with an "in plain words" gloss, and every display equation also gets a "named form" — the same equation re-emitted with each variable replaced by what it actually is, plus a `where:` legend — with math normalized to canonical `$…$` / `$$…$$` so `/paper-gloss` can typeset it; figures become placeholders with rewritten captions; the references section passes through untouched. Output lands in the current repo at docs/papers/<slug>-eli5.md (papers/ if no docs/; beside the input outside a repo) and is sent to Kyle. Use whenever Kyle types /paper-eli5, or says "eli5 this paper", "simplify this paper", "pl

0 Updated yesterday
ksdisch