Agent skill · Design & Presentation

journal-club-ppt

Use this skill whenever the user provides a scientific paper PDF and asks for a group-meeting literature report, journal-club slides, 文献汇报PPT, 组会PPT, paper presentation, article walkthrough, or to explain a paper with PowerPoint. The skill first reconstructs the paper's scientific logic, then builds author/background sections, chooses an evidence-driven slide outline, crops only main-text figure panels from the PDF, and creates an academic PPT with 10–30 slides including title and conclusion/discussion. Always use this skill for '把这篇论文做成PPT', '文献汇报', 'journal club', or '组会汇报', even if the user

Zhougeng Xu584★ · +324/wk · 1 repos on radarProfile →
claude-codeAGPL-3.0
Install
npx skills add xuzhougeng/wisp-science --skill journal-club-ppt --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 14 KB
Bundled scripts: none
Path: skills/journal-club-ppt/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 895 · +311 this week
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Journal Club PPT — scientific paper → academic group-meeting slides This skill turns a scientific paper PDF into a claim-driven PPT for lab meeting, journal club, or 文献汇报. The deck must explain the paper's logic, not merely summarize sections or paste screenshots. Default language: Chinese, with key technical terms preserved in English when helpful. Use another language only if the user asks. ## Hard constraints 1. **Read the argument before designing slides.** Do not create a slide outline until you can state the paper's central question, knowledge gap, hypothesis, experimental/computational strategy, evidence chain, and final claim. 2. **Include author introduction.** At minimum: first author(s), corresponding/senior author(s), affiliations, research direction inferred from the paper, and why this team is relevant to the work. Use external sources only for text facts when available and appropriate; never import external images. 3. **Include background introduction.** Explain the field context as: broad problem → unresolved gap → why this paper matters → what question the paper asks. 4. **Confirm a PPT outline before filling slides unless the user asked for a fully automatic fin

What's inside
Steps it walks through
  1. Hard constraints
  2. Wisp-specific workflow
  3. Phase 1 — Paper logic reconstruction
  4. Phase 2 — Author and background preparation
  5. Author slide
  6. Background slides
  7. Phase 3 — Main-text figure inventory
  8. Phase 4 — Subfigure selection rules
  9. Phase 5 — Cropping and figure handling
  10. Phase 6 — Deck outline design
  11. Phase 7 — Slide writing rules
  12. Phase 8 — Strengths, limitations, and discussion
  13. Phase 9 — Deliverables
  14. Self-check before final delivery
More from wisp-science
All skills →
About this skill
What does the journal-club-ppt skill do?

Use this skill whenever the user provides a scientific paper PDF and asks for a group-meeting literature report, journal-club slides, 文献汇报PPT, 组会PPT, paper presentation, article walkthrough, or to explain a paper with PowerPoint. The skill first reconstructs the paper's scientific logic, then builds author/background sections, chooses an evidence-driven slide outline, crops only main-text figure panels from the PDF, and creates an academic PPT with 10–30 slides including title and conclusion/discussion. Always use this skill for '把这篇论文做成PPT', '文献汇报', 'journal club', or '组会汇报', even if the user

How do I install it?

Run `npx skills add xuzhougeng/wisp-science --skill journal-club-ppt --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From xuzhougeng/wisp-science, a repository with 895 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going