Skip to content
Back to search

academic-pptx

"Use this skill whenever the user wants to create or improve a presentation for an academic context — conference papers, seminar talks, thesis defenses, grant briefings, lab meetings, invited lectures, or any presentation where the audience will evaluate reasoning and evidence. Triggers include: 'conference talk', 'seminar slides', 'thesis defense', 'research presentation', 'academic deck', 'academic presentation'. Also triggers when the user asks to 'make slides' in combination with academic content (e.g., 'make slides for my paper on X', 'create a presentation for my dissertation defense', 'build a deck for my grant proposal'). This skill governs CONTENT and STRUCTURE decisions. For the technical work of creating or editing the .pptx file itself, also read the pptx SKILL.md."

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/gabberflast-academic-pptx-skill/badge.svg)](/listings/gabberflast-academic-pptx-skill)

HTML

<a href="/listings/gabberflast-academic-pptx-skill"><img src="/api/listings/gabberflast-academic-pptx-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1. Download this repository as a zip file (click **Code → Download ZIP** above) 2. In [claude.ai](https://claude.ai), go to **Customize → Skills** 3. Upload the zip file 4. Confirm the skill appears in your skills list and is toggled on

> **Requirement:** Code execution and file creation must be enabled in **Settings → Capabilities**.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 152 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. ---
  2. name: academic-pptx
  3. description: "Use this skill whenever the user wants to create or improve a presentation for an academic context — conference papers, seminar talks, thesis defenses, grant briefings, lab meetings, invited lectures, or any presentation where the audience will evaluate reasoning and evidence. Triggers include: 'conference talk', 'seminar slides', 'thesis defense', 'research presentation', 'academic deck', 'academic presentation'. Also triggers when the user asks to 'make slides' in combination with academic content (e.g., 'make slides for my paper on X', 'create a presentation for my dissertation defense', 'build a deck for my grant proposal'). This skill governs CONTENT and STRUCTURE decisions. For the technical work of creating or editing the .pptx file itself, also read the pptx SKILL.md."
  4. license: Proprietary. LICENSE.txt has complete terms
  5. ---
  6. # Academic Presentations Skill
  7. ## How This Skill Works
  8. This skill has two layers:
  9. 1. **This file** — governs content, argument structure, and design standards for academic presentations. Read it fully before planning any slides.
  10. 2. **PPTX skill** — governs the technical implementation (creating, editing, and QA-ing the .pptx file). Read it too.
  11. **Always read both before writing any code or creating any files.**
  12. ---
  13. ## Quick Reference
  14. | Task | Guide |
  15. |------|-------|
  16. | Content planning, argument structure, slide-by-slide rules | [content_guidelines.md](content_guidelines.md) |
  17. | Per-slide-type patterns (title, methods, results, etc.) | [slide_patterns.md](slide_patterns.md) |
  18. | Technical creation from scratch | PPTX skill → `pptxgenjs.md` |
  19. | Technical editing of an existing file | PPTX skill → `editing.md` |
  20. ---
  21. ## Step 1: Identify Presentation Type
  22. Before planning a single slide, determine which mode applies.
  23. ### Structured Argument (default for academic work)
  24. Use for: conference papers, seminar talks, thesis defenses, dissertation chapters, grant briefings, internal lab presentations, policy briefings, consulting-style research deliverables.
  25. **Priority order: argument structure → data → layout → aesthetics.**
  26. Follow [content_guidelines.md](content_guidelines.md) in full.
  27. ### Visual / Narrative
  28. Use for: public engagement talks, science communication to non-specialist audiences, funding pitches to lay panels, event keynotes.
  29. Follow the PPTX skill's design-forward guidelines. Argument structure still matters, but visual storytelling and emotional engagement take priority.
  30. ### When in doubt
  31. Default to **Structured Argument**. If the user mentions a paper, a study, a dataset, a thesis, a grant, or a conference, they almost certainly want structured argument mode.
  32. ---
  33. ## Step 2: Plan the Deck Before Creating Any Slides
  34. Produce a slide-by-slide outline (title, action title, exhibit type) and confirm with the user if the deck is more than 10 slides or if the content is complex. Do not start building until the outline is agreed.
  35. Use the ghost deck test during planning: read only the proposed action titles in sequence. They must tell the complete argument. If they don't, fix the outline before building.
  36. ---
  37. ## Step 3: Apply Design Standards
  38. Academic presentations use **communication-first design**. These rules override the PPTX skill's design-forward defaults.
  39. ### Color
  40. - White background for all content slides.
  41. - One sans-serif font throughout (Arial, Calibri, or Helvetica — confirm with user or match their institution's template if provided).
  42. - Maximum three colors: one primary, one accent, one for emphasis or alerts. Default: dark navy primary (`1F4E79`), mid-blue accent (`2E75B6`), white or off-white background.
  43. - No decorative color gradients, no themed color palettes unless the user explicitly requests them.
  44. - Use color to **direct attention** — highlight the key finding on a chart, mark a callout box — not for decoration.
  45. ### Typography
  46. | Element | Size | Weight |
  47. |---------|------|--------|
  48. | Action title | 24–28 pt | Bold |
  49. | Section header | 20–22 pt | Bold |
  50. | Body bullets | 20 pt | Regular |
  51. | Chart labels / annotations | 16–18 pt | Regular |
  52. | Source citations on slides | 12–14 pt | Regular, muted color |
  53. Single font face. Use size and weight for hierarchy — never multiple typefaces.
  54. ### Layout
  55. - Left-align all body text. Center only slide titles and axis labels.
  56. - Consistent grid: all text boxes and figures align to the same margins (minimum 0.5" from slide edges).
  57. - For result slides: figure on the left, interpretive bullets on the right. This matches natural left-to-right reading.
  58. - White space is a signal of analytical clarity — do not fill every inch.
  59. - 16:9 widescreen is the default. Confirm with the user if they know the venue's aspect ratio.
  60. ### Avoid (Academic-Specific)
  61. - **No decorative icons** — icons in colored circles, stock images, clip art are inappropriate for analytical academic presentations.
  62. - **No accent lines under titles** — use whitespace instead.
  63. - **No color palettes chosen for aesthetic interest** — use institution colors or the minimal defaults above.
  64. - **No full-bleed background images on content slides** — reserve for title/section dividers only if desired.
  65. - **No text-heavy slides** — if the audience is reading, they are not listening. Maximum ~40 words of body text per content slide.
  66. ---
  67. ## Step 4: Build and QA
  68. Follow the PPTX skill's QA procedure in full, including:
  69. - Content QA via `markitdown`
  70. - Visual QA via slide images (subagents if available)
  71. - Fix-and-verify loop until a full pass reveals no new issues
  72. **Additionally, run the academic-specific checks:**
  73. ```
  74. Academic QA checklist:
  75. □ Every content slide has an action title (complete sentence stating the takeaway)
  76. □ Ghost deck test passes (action titles alone tell the full argument)
  77. □ One exhibit per results slide; each exhibit has a "so what" annotation
  78. □ Every borrowed figure or data point has an in-slide citation
  79. □ A References slide exists at the end
  80. □ Conclusions slide is the last non-appendix slide (not "Thank You" or a blank)
  81. □ Contact information and/or QR code/link on the final slide
  82. □ Font sizes are readable from the back of a room (≥ 20 pt body text)
  83. □ No decorative elements that don't carry content
  84. □ Section dividers or breadcrumb bar present for decks > 15 slides
  85. ```
  86. ---
  87. ## Key Principles (Summary)
  88. **Action titles, not topic labels.** Every slide title is a complete sentence stating the takeaway. Reading titles alone should tell the whole argument (ghost deck test).
  89. **One argument, made well.** Don't present your whole paper. Pick the claim that can be made convincingly in the allotted time. Everything else goes in the appendix.
  90. **One insight per slide.** One exhibit per results slide. Highlight the key finding directly on the chart — don't make the audience hunt for it.
  91. **Slides support speech; they don't replace it.** Body text is for orientation, not information transfer. The presenter carries the argument; the slide carries the evidence.
  92. **Cite everything borrowed.** Academic integrity applies to slides. In-text citations on the slide, full references on the References slide.
  93. **End on conclusions.** The conclusions slide stays on screen during Q&A. Never end on "Thank You" or a blank slide.
  94. ---
  95. ## Dependencies
  96. Same as PPTX skill:
  97. - `pip install "markitdown[pptx]"` — text extraction
  98. - `npm install -g pptxgenjs` — creating from scratch
  99. - LibreOffice (`soffice`) — PDF conversion
  100. - Poppler (`pdftoppm`) — PDF to images
README.md · README · 58 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Academic Presentations Skill for Claude (plus basic PDF summary of general advice)
  2. A Claude Skill for creating high-quality academic presentations: conference talks, seminar slides, thesis defenses, and grant briefings. Also includes a PDF which summarizes the advice (does not require use of Claude).
  3. ## What It Does
  4. This skill overrides Claude's default design-forward presentation style and replaces it with communication-first standards appropriate for academic and analytical contexts. When active, Claude will:
  5. - Write every slide title as a **complete sentence stating the takeaway** ("action title"), not a topic label
  6. - Structure the deck as a **logical argument** (situation → complication → resolution), not a collection of independent slides
  7. - Apply the **ghost deck test**: the action titles alone, read in sequence, should tell the full story
  8. - Place **one exhibit per results slide** and annotate the key finding directly on the chart
  9. - Apply **citation standards**: in-text citations on every borrowed figure, a References slide at the end
  10. - End on a **Conclusions slide** that stays on screen during Q&A — never on "Thank You" or a blank
  11. - Apply minimal, communication-first design: white backgrounds, single sans-serif font, three colours maximum, no decorative icons
  12. ## Installation
  13. 1. Download this repository as a zip file (click **Code → Download ZIP** above)
  14. 2. In [claude.ai](https://claude.ai), go to **Customize → Skills**
  15. 3. Upload the zip file
  16. 4. Confirm the skill appears in your skills list and is toggled on
  17. > **Requirement:** Code execution and file creation must be enabled in **Settings → Capabilities**.
  18. ## Usage
  19. Just ask naturally:
  20. - *"Make slides for my conference paper on X"*
  21. - *"Build a deck for my thesis defense"*
  22. - *"Create a seminar presentation about my research on Y"*
  23. Claude will detect the academic context, load this skill automatically, and apply all guidelines before generating any slides. You do not need to give any special instructions.
  24. This skill works alongside Anthropic's built-in PPTX skill, which handles the technical file generation. This skill handles content, argument structure, and design standards.
  25. ## File Structure
  26. ```
  27. academic-pptx-skill/
  28. ├── SKILL.md # Entry point: routing logic and design standards
  29. ├── content_guidelines.md # Argument structure, action titles, citations, deck architecture
  30. ├── slide_patterns.md # Per-slide-type implementation patterns with PptxGenJS code
  31. └── README.md # This file
  32. ```
  33. ## Background
  34. The guidelines in this skill draw on:
  35. - Barbara Minto's *Pyramid Principle* (structured argument, action titles)
  36. - Naegle (2021), "Ten simple rules for effective presentation slides," *PLOS Computational Biology*
  37. - Standard consulting and academic presentation practice (McKinsey, conference norms)
  38. - Community feedback on Claude's default presentation behaviour in professional contexts
  39. ## License
  40. MIT — free to use, adapt, and share.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.