科研 Skill
学术演讲幻灯片设计
research-slides-authoring
Plans and audits research talks or posters with assertion-evidence slides, audience-matched content, and a render-and-look check. Use when preparing or fixing a conference talk deck.
SKILL.md
Research slides authoring
When to load this skill
Load before creating, revising or reviewing anything that will be presented rather than read at a desk: a talk deck, a poster, a status or funder briefing, a defense, a lab-meeting update. Load it for small requests too ("fix this slide", "make the figure fit", "add a slide about X"). The failures this skill prevents happen most often on small edits, because a small edit feels too small to check.
It is toolchain-agnostic. Every audit rule is stated against the
rendered PDF, which every toolchain produces. Toolchain specifics
live in references/toolchain-beamer.md and
references/toolchain-marp.md.
This is not a file-format skill. A pptx skill handles reading and
writing .pptx files. This skill decides what goes on the slides and
checks that it arrived. For a PowerPoint deck, load both.
The governing test
Could someone who has not read the project, glancing up from their phone, restate this slide's point?
A deck is not a project directory with page breaks. Every rule below serves this test.
The four principles
- Argue, don't file. A deck makes a claim and builds evidence for it. The order of the work plan is not an argument.
- Write for someone who is not you. The audience has not read the repository, does not share its vocabulary, and was not in the room when decisions were made.
- Form carries meaning. Colour, size, position, grouping and repetition each say something. Use them on purpose, consistently.
- Look, don't assume. A clean build proves the source compiled. It says nothing about whether the slide is right. Render it and look.
Workflow and gates
| Phase | Output | Gate |
|---|---|---|
| 1. Discovery | Answers to one batch of questions | Nothing asked that could have been read |
| 2. Brief | notes/talk_brief.md, one screen | User approves |
| 3. Plan | notes/talk_plan.md: claim, beats, one line per slide | User approves |
| 4. Draft | The deck | Build succeeds |
| 5. Audit | Rendered pages checked | After every visual edit, not once at the end |
| 6. Distribute | PDF delivered, location stated | Privacy pass if shared publicly |
For a one-slide edit, phases 1 to 3 shrink to reading the deck's existing plan. Phase 5 never shrinks.
Rules by phase
Each rule has one line here and full treatment in a reference file. Load the reference for the phase you are in, not all of them.
Discovery and brief: references/discovery-and-brief.md
- D1 Read before asking. Read the project, the material the talk
presents, and any per-project
AGENTS.md"Audience composition" field. Never ask what you can read or measure. - D2 Ask once, in one batch: toolchain and template, audience mix, venue and time slot, title, abstract, URLs to show, and whether the PDF will be distributed.
- D3 The audience sets the density of math, code and jargon. With a mixed audience, both directions of jargon are jargon.
- D4 The abstract or headline claim is the contract. Every planned slide supports it. Reconcile the deck with the abstract, or propose one.
Structure: references/deck-structure.md
- S1 Plan before drafting. A slide plan, one line per slide (claim plus visual idiom), approved by the user. Structure is not recoverable by editing slides.
- S2 The titles, read alone in order, make the argument. If they are noun phrases with no verbs, the deck is documentation.
- S3 Each slide opens on something the previous one established.
- S4 Required slots: a title slide with date and version; contents and section dividers when there are 8 or more slides; acknowledgements (including AI assistance); a specific call to action; backup material at the end.
- S5 Several artefacts make parallel tracks, joined at the start and the end, unless one really depends on another.
- S6 A recurring spine figure is one source with highlight variants, so one fix reaches every copy.
- S7 Budget about one slide per minute.
Composition: references/slide-composition.md
- C1 Assertion-evidence. The title is a full-sentence finding. The body is mostly a visual that supports it.
- C2 One point per slide. Split a slide that makes two.
- C3 Three or more discrete items become a list, diagram or table, never a chain of commas.
- C4 The slide carries the bones; the speaker carries the sentences. A bullet of 20 or more words is speaker text.
- C5 Code: only the one line the audience will type.
- C6 Math: one display equation per claim. Every symbol is defined at or before first use, one symbol means one thing for the whole deck, and every equation is compiled.
- C7 Spell out abbreviations where they first appear. No slide sends the reader to a file.
- C8 A number points at its source or is labelled as a target.
- C9 URLs: vital ones get a QR code, the text URL and a caption; private ones are removed; all are clickable in a distributed PDF.
- C10 Reconcile new material against the whole deck, not just the slide that asked for it. Re-verify cited facts at every build, including facts your own session may have made stale.
- C11 A figure must not contradict its caption, title or geometry.
Visual design: references/visual-design.md
- V1 Consistency. Polish one figure, polish all. Style each element type once (theme, preamble, macros), never per slide.
- V2 One colour per role, a legend when colour encodes state, and a conclusion colour distinct from context.
- V3 Hierarchy carries meaning. Named subjects look different from generic groupings.
- V4 Restrained depth: one elevation level, or none.
- V5 Titles fit on one line, confirmed in the render.
- V6 Run the diagram-failure checklist: arrows through text, labels on lines, cramped or stranded boxes, connectors too short to read.
- V7 Accessibility: contrast, a colour-blind-safe palette, no more than about six elements per slide.
- V8 Figures are generated by committed scripts and referenced by name, never embedded as bytes in the deck source.
Render and audit: references/render-audit.md
- A1 A clean build is not done. After every visual edit: build,
render the changed pages, look at each as if for the first time,
fix, then report. Use
scripts/audit-pages.sh. - A2 Size renders in pixels, not DPI: about 1000 to 1100 px on the long edge for review. Crop and magnify for edges and labels. A thumbnail grid checks content, never boundaries.
- A3 Boundary check: edges, footer clearance, code and table overflow, hyphenation in narrow boxes.
- A4 Count what must survive. Every heading in the source must
appear in the PDF text (
audit-pages.sh -e). An overfull slide or a flowed poster column can drop a block silently. - A5 Sweep the deck rule by rule, not slide by slide. Check arrows against text in a separate pass after layout.
- A6 Distrust your checker before your deck. Calibrate a new tool on a known-good input. When a check and a reader disagree, magnify before retuning.
Distribution
- X1 Ship the PDF and say where it is, with the command that opens it. Keep a PDF fallback for any live-rendered format.
- X2 Never overwrite without being asked. Archive earlier versions.
- X3 A visible version stamp on the title slide.
- X4 Before sharing publicly, apply root
AGENTS.mdSection 6.7: no private URLs or QR codes, no machine-local paths or claims, no unreleased results unless the user says so.
Posters follow the same rules with different geometry and reading
distance: see references/posters.md (provisional).
Common rationalizations
| Thought | Rebuttal |
|---|---|
| "The build is clean, so it's done." | The most repeated failure in the evidence. Render the changed pages and look. |
| "The thumbnail grid looks fine." | A grid compresses a 2 mm clip to under a pixel. Grids check content, not edges. |
| "I only changed one slide." | One partial fix once left 28 defects across a deck. Reconcile, then render the changed pages. |
| "Trim prose until it fits." | Fitting is a structure problem first. Split the slide or move detail to the speaker. |
| "The checker passed." | It passed the checks it has. Look anyway, and calibrate the checker on a known-good slide. |
| "The audience will read the bullets." | They will read or listen, not both. Move sentences to the speaker. |
| "Same numbers as last time." | Cited facts drift, including ones your own session changed. Re-verify at build time. |
Done checklist
Before reporting a deck as finished: references/self-review-checklist.md
(one check per rule above). At minimum: the brief and plan were
approved; every changed page was rendered and viewed; all expected
headings survived (audit-pages.sh -e); the titles read as an argument;
the PDF location was reported.
Interactions with other skills
human-facing-doc-authoring: section I prose habits apply to slide text, rule K (self-invalidating facts) generalises C10, and rule L generalises whole-deck reconciliation. Cite them; do not restate.research-paper-writing:research-paper-writing/references/abstract.mdfor D4, andresearch-paper-writing/references/paper-review.mdfor an adversarial pass over the finished deck.agent-resource-discipline:agent-resource-discipline/references/pdf-lifecycle.md(text extraction order is not visual order) andagent-resource-discipline/references/public-surface-hygiene.md(X4).- A pptx skill, for
.pptxfile mechanics.
Prior art
- K. M. Naegle, "Ten simple rules for effective presentation slides", PLoS Computational Biology 17(12): e1009554 (2021).
- M. Alley and J. Garner, the assertion-evidence approach (assertion-evidence.com).
- Anthropic's
pptxskill: rendered visual QA with fresh eyes. Noi1r/beamer-skill(MIT): a gated Beamer workflow with density caps and the observation that Beamer hides overflow inside blocks.
Created 2026-10-14 by A. Attia. Consolidated from the slide-authoring proposal (issue #3, with evidence appends #4 and #5) and per-project journals: about 30 sessions across four projects in two independent lineages (Beamer and Marp), which converged on the same core rules. All four projects are the maintainer's own; external evidence is still needed. Maintained by A. Attia.
示例提示词
我要准备一场学术报告,帮我规划幻灯片内容结构和讲稿要点。
所属插件
安装该插件会一并获得同领域的 54 个 Skill / MCP。
同插件的其他科研 Skill
- 智能体资源节约守则Applies token- and context-saving habits for tool choice, PDF handling, persistent memory, and privacy checks. Use at the start of sessions with many files or PDFs, or multi-session work.
- 英文论文双语精读器把英文论文转成中英对照精读档并生成离线双语阅读器,标注要点并输出读书笔记。精读单篇英文论文、要中英对照阅读时使用。
- 研究方法比较论证Compares quantitative, qualitative, and mixed research methods against what each can and cannot answer to build a methods table. Use when justifying a method choice in a thesis.
- 复杂系统分析方法Analyzes complex systems with power-law fitting, Hurst exponent, fractal dimension, agent-based modeling, and entropy measures. Use for nonlinear or complex-system data.
- 研究环境容器化部署Builds Docker and Singularity containers for reproducible computation and HPC deployment of research environments. Use when packaging an analysis pipeline for reuse or HPC.
- DVC数据版本管理Sets up DVC for dataset and pipeline versioning, remote storage, and experiment comparison in reproducible ML research workflows. Use when tracking large datasets or ML experiment runs.
- 期刊级统计图表绘制Creates publication-quality multi-panel figures with matplotlib, seaborn, or ggplot2 using colorblind-safe palettes and journal export settings. Use when preparing figures for a paper.
- 综述模块拆解规划Breaks a refined literature-review question into 3-5 non-overlapping modules to build a reading map, outline, or search plan. Use when structuring a literature review.
- 学位论文答辩教练模拟学位口试委员提问并提供承认回应证据三段式答辩框架与模拟问答。准备论文口试或研讨会问答环节时使用。
- 实验设计与样本量规划Designs rigorous experiments covering sample-size calculation, randomization strategy, pre-registration, and A/B test duration estimation. Use when planning an experiment or A/B test.
- 管理实验设计架构为管理与商学情境实验规划组间组内设计、对抗平衡与操弄检核,并产出设计书与情境材料模板。做商学实验设计时使用。
- 科研经费申请撰写Structures research grant proposals including NSF/NIH Specific Aims, budget justification, ERC narrative sections, and biosketch formatting. Use when drafting a funding application.
- 人类可读文档撰写规范Guides writing human-facing docs like README, PLAN, survey notes, and reviewer-response drafts with a clear two-tier structure. Use for text a human collaborator will read.
- 知识图谱与SPARQL检索Builds knowledge graphs and runs SPARQL queries over RDF and Wikidata for entity linking in research and library data. Use when modeling research entities as a linked graph.
- LaTeX论文写作与排版Writes, compiles, and submits LaTeX papers covering IMRaD structure, key packages, bibliography management, and arXiv preparation. Use when authoring or debugging a LaTeX manuscript.
- 文献比较矩阵构建器把一批PDF整理成含撤稿查核与APA7书目的文献资料库,并生成横向比较矩阵表。整理综述前要比较文献时使用。
- 跨库学术文献检索Searches OpenAlex, Semantic Scholar, and arXiv for academic literature with deduplication, citation snowballing, and BibTeX export. Use when collecting papers for a review or topic.
- 文献调研语料库维护Finds, verifies, and maintains a literature corpus from arXiv, OpenAlex, Crossref, and related databases with BibTeX entries and per-paper notes. Use when sourcing references for a paper.
- 文献综述研究缺口定位Converts a literature-review synthesis into a concrete, defensible research gap and future-research direction. Use when writing a conclusion or thesis contribution section.
- 文献矛盾结论梳理Analyzes conflicting findings across papers and explains disagreement by sample, method, or context differences for a stronger synthesis. Use when review sources disagree.
- 效应量汇总元分析Pools effect sizes across studies with fixed and random-effects models, heterogeneity tests, forest and funnel plots, and subgroup analysis. Use to synthesize quantitative study results.
- 缺失数据处理Diagnoses missing-data mechanisms such as MCAR, MAR, or MNAR and applies multiple imputation or deletion with sensitivity analysis. Use when a dataset has missing values.
- 混合方法研究设计Designs mixed-methods studies integrating qualitative coding, triangulation, content analysis, and QCA with inter-rater reliability checks. Use when combining qual and quant data.
- 科研机器学习流程Applies machine learning to research questions with scikit-learn pipelines, AutoML, SHAP explainability, and nested cross-validation. Use when building a predictive model for a study.
常见问题
学术演讲幻灯片设计能做什么?
Plans and audits research talks or posters with assertion-evidence slides, audience-matched content, and a render-and-look check. Use when preparing or fixing a conference talk deck。
如何安装学术演讲幻灯片设计?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「学术演讲幻灯片设计」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
学术演讲幻灯片设计需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
学术演讲幻灯片设计经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。