Skill-Details
powerpoint-slides
Full PPTX creation and review workflow, especially for academic decks.
Vor Nutzung prüfen
Die automatische Prüfung bewertet Relevanz, nicht Sicherheit oder Empfehlung. Lies vor der Nutzung die Quellanweisungen.
SKILL.md
Dieser Auszug wurde bei der Prüfung gespeichert. Die externe Quelle enthält die vollständige und aktuelle Version.
--- name: powerpoint-slides description: | Create visually rich PowerPoint (.pptx) presentations from academic papers, research notes, or any content the user wants in slide format. Uses PptxGenJS + LaTeX formula rendering. Always use this skill when the user wants PPT/PPTX output instead of Beamer/LaTeX slides. Trigger on: powerpoint, pptx, PPT, make a ppt, 做PPT, 做幻灯片, make slides (non-LaTeX), prepare a presentation (when context implies PPT), 做个报告, presentation slides, help me prepare a talk (when not Beamer), convert paper to slides (when PPT implied). Even if the user just says "make slides" or "做个演示" without specifying format, trigger this skill and ask whether they want PPT or Beamer — don't silently default to Beamer. Do NOT trigger on: beamer, latex slides, .tex files, tikz — those belong to the beamer skill. argument-hint: "[action] [file] — actions: create, compile, review, audit, pedagogy, excellence, visual-check, validate, extract-figures" allowed-tools: ["Read", "Write", "Edit", "Bash", "Grep", "Glob", "Agent", "AskUserQuestion", "TaskCreate", "TaskUpdate", "TaskList", "TaskGet"] --- # PowerPoint Slides Workflow Academic PowerPoint presentation skill. Full lifecycle: create → compile → review → polish → verify. Execution model: Claude writes a PptxGenJS (Node.js) script → executes → `.pptx`. Math formulas: OMML (native math, default) or LaTeX → PNG/SVG pipeline (paragraph-mode fallback). --- ## 0. Quick Reference | Task | Command | Description | |------|---------|-------------| | Create from paper | `create [topic]` | Full Phase 0-5 pipeline | | Execute JS script | `compile [file.js]` | Run script, produce .pptx | | Proofread | `review [file.pptx]` | Grammar, typos, consistency | | Visual audit | `audit [file.pptx]` | Per-slide layout inspection | | Teaching quality | `pedagogy [file.pptx]` | 13 pedagogical patterns | | Full review | `excellence [file.pptx]` | 5 parallel agent review | | Visual check | `visual-check [file.pptx]` | PDF→image systematic check | | Validate metrics | `validate [file.pptx] [duration]` | Slide count, file size | | Extract figures | `extract-figures [file.pdf] [pages]` | Extract paper figures for slides | Parse `$ARGUMENTS` to determine which action to run. If no action specified, ask. --- ## 1. Hard Rules (Non-Negotiable) 1. **Motivation before formalism** — every concept starts with "Why?" before "What?". Never drop a definition without context. 2. **Worked example within 2 slides** — every definition must have a concrete worked example within 2 slides of its introduction. 3. **Telegraphic style** — keyword phrases, not full sentences. Slides are speaker prompts, not manuscripts. Exception: one framing sentence per slide to set context. 4. **Every slide earns its place** — must contain at least one substantive element (formula, diagram, table, theorem, algorithm, chart). A slide with only 3 short bullets and nothing else must be merged or enriched. 5. **Max 2 accent cards per slide** — more dilutes emphasis. Accent cards are colored boxes, callout shapes, or highlighted regions. Demote lower-priority items to plain text. 6. **Reference slide** — the second-to-last slide (before Thank You) must list key cited works. Include the primary paper and 3-5 most relevant references. 7. **Color-blind safe palette** — blue+orange preferred, never red+green for binary contrasts. WCAG AA contrast ratio ≥ 4.5:1 for text on backgrounds. Semantic colors defined in theme. 8. **Font size hierarchy** — `F` constant object defines default baselines: cover 48pt, section 36pt, title bar 22pt, body 15pt, small 12pt, caption 11pt, cardTitle 18pt, tblHead 13pt, tblCell 12pt. Never go below 10pt. When a card or region has sparse content (text fills <50% of available area), scale up by 2-4pt in the QA fix pass. 9. **Backup slides** — 3-5 after Thank You, separated by an appendix divider slide. For anticipated questions: detailed proofs, extended comparisons, additional data. 10. **VeVollständige Quelle auf GitHub lesen (öffnet externe Seite)