菜单
Creates and refines academic presentations from research papers. Use this skill for tasks involving the conversion of scientific or technical documents into slide decks for conferences, seminars, lectures, thesis defenses, or academic reviews. Supports beamer LaTeX (.tex), PowerPoint (.pptx), and Markdown output formats.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Execute delay-model validation gates against HPWL baselines. Use when evaluating model consistency, running Gate-0 contract checks, building Gate-1 bucketed scorecards, performing wirelength-aware correlation checks, or deciding readiness for active optimization.
Run a full EDA research chain from knowledge exploration and paper triage to idea debate, hypothesis experiment design, implementation, git versioning, validation, and retrospective. Use when the user requests an end-to-end EDA research workflow rather than a single isolated execution step.
Audit and refine academic manuscripts for structure, terminology consistency, LaTeX hygiene, and high-signal grammar fixes. Use this skill for theses, papers, proposals, and technical reports when the task is manuscript writing rather than experiment execution.
Diagnose and implement backside-routing realization paths, including targeted reroute, local DEF/OpenDB patching, and OpenROAD-backed net-level rerouter bring-up, when theory predicts benefit but the current flow does not realize BM2/BM1 usage.
Audit whether the local BSPDN physical contract is coherent across paper assumptions, GT3 tech collateral, layer/via topology, and current flow policy before promotion or expensive attribution experiments.
Manage and standardize project conda environment usage as an auxiliary utility skill, including env discovery, package availability checks, explicit env selection, and reproducible `conda run -n ...` integration for scripts and workflows.
| name | academic-presentation-crafter |
| description | Creates and refines academic presentations from research papers. Use this skill for tasks involving the conversion of scientific or technical documents into slide decks for conferences, seminars, lectures, thesis defenses, or academic reviews. Supports beamer LaTeX (.tex), PowerPoint (.pptx), and Markdown output formats. |
This skill provides a structured, multi-phase workflow for transforming dense research papers into clear, concise, and academically rigorous presentations. It ensures the final slide deck accurately reflects the paper's core contributions, data, and terminology.
The process is divided into four distinct phases. Follow these steps sequentially to ensure a high-quality outcome. For detailed checklists on rigor and visual polish, refer to the references/ directory.
When the audience is external (advisor, committee, collaborator), enforce:
Baseline, Variant-B).Case-A, Case-B) and move raw identifiers to private appendix only if requested.beamer (.tex) and compile to .pdf; otherwise keep a clean Markdown deck as fallback.Action: follow references/external_reporting_sanitization_checklist.md before finalizing.
The goal of this phase is to deeply understand the source material and create a logical structure for the presentation.
.md) with --- page separators. A typical academic structure is recommended (Motivation, Methods, Results, Conclusion). Start with 8-12 slides and expand only if necessary.This phase focuses on populating the slides with content and integrating the necessary visual aids.
This phase ensures the presentation meets academic standards. Apply the full checklist in references/academic_rigor_checklist.md, paying special attention to these critical items:
Feedback loop: After applying the checklist, revisit Phase 2 slides, update any corrected content, and re-verify data placeholders.
Apply the full checklist in references/visual_polish_checklist.md, focusing on these high-impact items:
Feedback loop: Do a full sequential walkthrough of the deck. If any slide feels unclear or visually inconsistent, return to the relevant earlier phase before finalizing.
A results slide in Markdown format:
## Results: Timing Closure Improvement
- Proposed flow achieves **12% WNS reduction** vs. baseline (Table 3)
- Area overhead: +2.1% (within PPA budget)
- Runtime: 3.2x faster than conventional approach
<!-- Source: Fig. 5, Section IV-B -->
> Speaker notes: Emphasize the WNS improvement first, then address
> the area-runtime tradeoff. Reference Table 3 for detailed breakdowns.