academic-slides
Use this skill for creating or refining an academic slide deck and the talk built around it: structuring a conference talk, thesis defense, lab meeting, or paper-to-slides deck; deciding the narrative arc and slide breakdown; improving slide design and visual hierarchy; planning rehearsal, timing, Q&A, and backup slides; or generating the .pptx. Reach for it when the user is shaping the presentation itself. Do not use for writing the paper, producing standalone speaker notes/scripts/transcripts, making posters, creating isolated figures/charts outside a slide deck, or building non-academic presentations.
- Installs
- 482
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/evoscientist/evoskills --skill academic-slides- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads academic-slides automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Academic Slides
A structured approach to creating academic presentation slides and preparing research talks. Covers narrative structure, slide design, visual hierarchy, delivery technique, and Q&A preparation.
When to Use This Skill
- User wants to create presentation slides for a research talk
- User asks about structuring an academic presentation
- User needs to prepare for a conference talk, thesis defense, or lab meeting
- User wants to design a slide deck from a paper or research project
- User mentions "slides", "presentation", "talk", "defense", "poster talk"
Before You Start: Three Questions
Before designing any slides, answer these questions clearly:
-
What works are you presenting? They must share a coherent research direction. If presenting multiple works, they should form a narrative arc — not a disconnected list.
-
What problems do these works solve in that direction? Each work should map to a specific problem. If you cannot articulate the problem in one sentence, you are not ready to present.
-
How do you use related work to naturally introduce these problems? Related work is not citation duty. It builds the motivation for YOUR problem. Each related work you mention should advance the audience toward understanding why your approach is needed.
Core Workflow
Step 1: Define scope and audience
Step 2: Draft narrative arc (outline)
Step 3: Design slide structure (section breakdown)
Step 4: Create individual slides (one idea per slide)
Step 5: Build the .pptx file (layouts, figures, charts, QA)
Step 6: Rehearse and time
Step 7: Prepare backup slides (for Q&A)
Step 1: Define Scope and Audience
| Audience | Adjust |
|---|---|
| Domain experts | Skip basics, go deep on method and results |
| Broad CS / engineering | Explain task context, moderate technical depth |
| Interdisciplinary | Start from the application, minimize jargon |
| Industry | Lead with impact and demo, light on theory |
Rule of thumb: Duration in minutes = approximate slide count. A 20-minute talk needs about 20 slides.
Step 2: Draft Narrative Arc
Use the outline template at assets/talk-outline-template.md to plan your talk before making any slides. The outline forces you to articulate your key takeaway and narrative arc.
Step 3: Design Slide Structure
Break your outline into sections with claim-style headers. See talk-structure.md for two complete talk structures and section-by-section guidance.
Step 4: Create Individual Slides
One idea per slide. Follow the 10 design rules in slide-design.md for visual hierarchy and layout.
Step 5: Build the .pptx File
Use slide-creation.md for practical .pptx creation — color palettes, layout code, charts, tables, figures, and QA workflow.
Dependencies: pip install "markitdown[pptx]" pillow (also listed in requirements.txt at the skill root) for text extraction and QA, plus the Node packages named in the Setup section of slide-creation.md. Install into the environment the user is working in.
Step 6: Rehearse and Time
See references/delivery-and-qa.md for the rehearsal protocol, delivery principles, and Q&A preparation.
Step 7: Prepare Backup Slides
Backup slides go after your "Thank You" slide. They are not part of the talk — they are your safety net for Q&A:
- Full quantitative comparison table
- Failure cases (shows honesty and preparation)
- Additional ablations or analysis
- Slides addressing anticipated tough questions
Artifact Sources from Other Skills
If you used other EvoSkills earlier in the pipeline, pull these artifacts directly:
| Source Skill | Artifact | Use In Slides |
|---|---|---|
paper-planning | Story summary (task → challenge → insight) | Motivation slides |
paper-planning | Pipeline figure sketch | Method overview slide |
paper-planning | Experiment plan | Results structure |
paper-writing | Finalized figures and tables | Method + results slides |
paper-review | Anticipated reviewer concerns | Backup Q&A slides |
See slide-creation.md for detailed layout patterns using each artifact.
Counterintuitive Presentation Rules
For the 10 design rules (one idea per slide, claim-style titles, max 6 elements, etc.), see slide-design.md. The rules below are higher-level mindset shifts.
1. Your slides are not your paper
A talk is an advertisement, not a lecture. Your goal is to make the audience interested enough to read the paper. Cut 80% of your paper's content. If someone can reconstruct your paper from your slides alone, your slides have too much.
2. Reading and listening compete
Text-heavy slides force the audience to choose between reading your slides and listening to you. They will read — and stop hearing you. When you put text on a slide, you are choosing to be ignored.
3. Enthusiasm > polish
A passionate speaker with rough slides beats a bored speaker with beautiful slides. The audience remembers your energy and clarity, not your color scheme. If you only have time to improve one thing, rehearse more — don't redesign slides.
4. Related work is not citation duty
Use related work to BUILD your problem motivation, not to show you have read papers. Each related work slide should advance the narrative: "This approach solved X, but Y remains open — which is exactly what we address."
Reference Navigation
| Topic | Reference File | When to Use |
|---|---|---|
| Talk structures | talk-structure.md | Organizing the narrative arc |
| Slide design | slide-design.md | Visual design and layout rules |
| Slide creation | slide-creation.md | Building .pptx files with code |
| Delivery and Q&A | delivery-and-qa.md | Rehearsal, timing, Q&A preparation |
| Talk outline template | talk-outline-template.md | Starting a new presentation |
FAQ
What does the academic-slides skill do?
Use this skill for creating or refining an academic slide deck and the talk built around it: structuring a conference talk, thesis defense, lab meeting, or paper-to-slides deck; deciding the narrative arc and slide breakdown; improving slide design and visual hierarchy; planning rehearsal, timing, Q&A, and backup slides; or generating the .pptx. Reach for it when the user is shaping the presentation itself. Do not use for writing the paper, producing standalone speaker notes/scripts/transcripts, making posters, creating isolated figures/charts outside a slide deck, or building non-academic presentations.
How do I install academic-slides?
Run npx skills add https://github.com/evoscientist/evoskills --skill academic-slides in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/academic-slides/ (personal) or .claude/skills/academic-slides/ (project).
Which AI agents can use academic-slides?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is academic-slides safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains academic-slides?
It is published by evoscientist in evoscientist/evoskills. It has 482 recorded installs.
More from evoscientist/evoskills
paper-review
evoscientist/evoskills
Guides self-review of YOUR OWN academic paper before submission with adversarial stress-testing. Core method: three passes (adversarial deep read; 5-aspect checklist — contribution sufficiency, writing clarity, results quality, testing completeness, method design; mechanical consistency scans and experimental protocol audit of data flow, assumptions, leakage), counterintuitive protocol (reject-first simulation, delete unsupported claims, score trust, promote limitations, attack novelty), reverse-outlining, and figure/table quality checks. Use when: user wants to self-review or self-check their own paper draft before submission, stress-test their claims, prepare for reviewer criticism, or mentions 'self-review', 'check my draft', 'is my paper ready'. Do NOT use for writing a peer review of someone else's paper, and do NOT use after receiving actual reviews (use paper-rebuttal instead). Also runs as a background expert: dispatch it async with a draft path and it reviews end-to-end while
paper-writing
evoscientist/evoskills
Guides writing academic papers section by section using an 11-step workflow with LaTeX templates and counterintuitive writing tactics. Covers Abstract, Introduction, Method, Experiments, Related Work, Conclusion, and Supplementary. Use when: user asks to write or draft a paper section, needs LaTeX templates, wants to improve academic writing quality, optimize novelty framing, or mentions 'write introduction', 'draft method', 'paper writing'. Do NOT use for pre-submission review (use paper-review), experiment execution (use experiment-pipeline), or paper planning/story design (use paper-planning).
research-ideation
evoscientist/evoskills
End-to-end research ideation pipeline: literature grounding → multi-track idea generation (3 personas: innovator/pragmatist/critic) → iterative refinement → ELO tournament ranking → update evo-memory (IDE) → user selects direction → expand into manuscript-quality proposal. Use when: user wants to find a research direction, brainstorm ideas, evaluate idea novelty, design a novel solution, rank/compare research ideas, or generate a research proposal. Do NOT use for finding/searching/reading papers (use paper-navigator), literature survey reports (use research-survey), or planning a paper (use paper-planning).
paper-rebuttal
evoscientist/evoskills
Guides writing effective rebuttals after receiving peer review feedback. Covers review diagnosis (score-driven color-coding), response strategy (champion identification, common-theme consolidation), tactical writing (18 rules), and counterintuitive rebuttal principles. Use when: user received reviewer scores/comments, needs to write a rebuttal or author response, wants to respond to specific criticism (e.g. 'limited novelty', 'missing baselines'), mentions 'rebuttal', 'reviewer comments', 'author response', or 'respond to reviewers'. Do NOT use for pre-submission self-review (use paper-review instead).
paper-planning
evoscientist/evoskills
Guides pre-writing planning for academic papers with 4 structured steps: story design (task-challenge-insight-contribution-advantage), experiment planning (comparisons + ablations), figure design (pipeline + teaser), and 4-week timeline management. Includes counterintuitive planning tactics (write a mock rejection letter to identify weaknesses before writing, narrow before broad claims, design ablations first). Use when: user wants to plan a paper before writing, design story/contributions, plan experiments, create figure sketches, set a writing timeline, or write a pre-emptive rejection letter for planning purposes. Do NOT use for actual writing (use paper-writing), running experiments (use experiment-pipeline), self-reviewing a finished draft (use paper-review), or finding research problems (use research-ideation).
experiment-pipeline
evoscientist/evoskills
Guides structured 4-stage experiment execution with attempt budgets and gate conditions: Stage 1 initial implementation (reproduce baseline), Stage 2 hyperparameter tuning, Stage 3 proposed method validation, Stage 4 ablation study. Integrates with evo-memory (load prior strategies, trigger IVE/ESE) and experiment-craft (5-step diagnostic on failure). Use when: user has a planned experiment, needs to reproduce baselines, organize experiment workflow, or systematically validate a method. Do NOT use for debugging a specific experiment failure (use experiment-craft) or designing which experiments to run (use paper-planning).
Popular docs & writing skills
grill-with-docs
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
lark-markdown
open.feishu.cn
飞书 Markdown：查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件，或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。
writing-beats
mattpocock/skills
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
writing-shape
mattpocock/skills
Writing, exploit: shape raw material into an article, paragraph by paragraph.
writing-fragments
mattpocock/skills
Writing, explore: mine raw fragments, no structure yet.
writing-for-agents
mattpocock/skills
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.