skills/academic-presentation-crafter/SKILL.md
Creates and refines high-quality academic presentations from research papers. Use this skill for tasks involving the conversion of scientific or technical documents into slide decks for conferences, lectures, or academic reviews.
npx skillsauth add biswajit56546/edagent academic-presentation-crafterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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 is not only visually polished but also 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 is the most critical phase for ensuring the presentation meets academic standards. It requires meticulous attention to detail.
Action: Read and meticulously follow the checklist in references/academic_rigor_checklist.md.
This checklist covers:
This final phase focuses on aesthetics, readability, and overall presentation quality.
Action: Read and meticulously follow the checklist in references/visual_polish_checklist.md.
This checklist covers:
testing
Apply and validate GT3 backside routing policy in Innovus. Use when configuring CTS/PDN/signal layer usage, submitting GT3 consistency runs, diagnosing zero-backside-nets, or enforcing BPR-reserved-for-PDN constraints.
testing
Use git to version-control local research/EDA iterations with reproducible checkpoints, clear commit/tag structure, and explicit per-version differentiation records. Use when users ask to create baselines, compare versions, snapshot experiment states, prepare rollback points, or document each version's characteristics and distinguishing deltas.
development
Theory-level veto skill for EDA plans. Use before expensive experiment submissions or major flow/model changes to identify logically unsound assumptions, contradiction with known physics/policy, and high-risk invalid comparisons. Produces GO/CONDITIONAL/NO-GO with evidence.
tools
Package the agent+skill infrastructure into a standalone, portable repository-ready bundle with skill-local tool mirrors.