PPT Creator

Goal: Transform a simple topic into a presentation-ready, high-quality slide deck. When key information is missing, use the minimal intake form (references/INTAKE.md) to gather context or apply safe defaults. Then follow the workflow (references/WORKFLOW.md) to produce an outline, slide drafts, charts, and speaker notes. After generation, self-evaluate using the rubric (references/RUBRIC.md); if the score is < 75, automatically refine up to 2 iterations until ≥ 75 before delivery. See Deliverables section for final output structure.

When to Use This Skill

Use this skill when the user requests:

• "Make a presentation/deck/PPT/slides" on any topic
• "Improve/optimize a presentation/pitch/demo"
• Converting scattered materials into a structured, persuasive slide deck
• Creating presentations with data visualization and speaker notes
• Building decks for business reviews, product pitches, educational content, or reports

Quick Start

1. Gather Intent: If critical information is missing, ask the 10 Minimal Questions (references/INTAKE.md). If the user doesn't respond after 2 prompts, use the safe default for each item and clearly note assumptions in speaker notes.

2. Structure the Story: Apply the Pyramid Principle to establish "one conclusion → 3-5 top-level reasons → supporting evidence." Each slide uses assertion-style headings (complete sentences), with body content providing evidence (charts/tables/diagrams/data points). Templates are in references/TEMPLATES.md.

3. Choose Charts: Use the Chart Selection Dictionary in references/VIS-GUIDE.md to pick the most appropriate visualization for each point. If the user provides data (tables/CSV), optionally call scripts/chartkit.py to generate PNG charts; otherwise, create placeholder diagrams with a list of required data fields.

4. Layout & Style: Follow references/STYLE-GUIDE.md for font sizes, line spacing, white space, contrast ratios, color palettes, and accessibility (WCAG AA compliance).

5. Speaker Notes: Generate 45-60 second speaker notes for each slide, structured as: opening → core assertion → evidence explanation → transition.

6. Self-Check & Score: Use references/CHECKLIST.md for a pre-flight check, then score with references/RUBRIC.md. If total score < 75, identify the weakest 3 items and refine; repeat scoring (max 2 iterations).

7. Deliverables (all saved to /output/):

   • /output/slides.md: Markdown slides (Marp/Reveal.js compatible), with assertion-style headings + bullet points/chart placeholders + notes
   • /output/assets/*.png: Generated charts (if applicable)
   • /output/notes.md: Full speaker notes and delivery outline
   • /output/refs.md: Citations and data sources
   • /output/presentation.pptx: If python-pptx is available, export to PPTX; otherwise, keep Markdown and include instructions for "one-click conversion to PPTX" in the first screen (does not block delivery)

Orchestration Mode (End-to-End Automation)

When the user requests a "complete" or "presentation-ready" deliverable, ppt-creator automatically orchestrates the full pipeline: content creation → data synthesis → chart generation → dual-path PPTX creation (Marp + document-skills:pptx) → chart insertion. This typically delivers TWO complete PPTX files with different styling for user comparison.

Activation: Phrases like "complete PPTX", "final deliverable", "ready for presentation" Duration: 4-6 minutes (parallel execution) Output: presentation_marp_with_charts.pptx + presentation_pptx_with_charts.pptx

For orchestration details, see references/ORCHESTRATION_OVERVIEW.md (start here), then navigate to specialized guides as needed.

Core Principles (Must Follow)

• Information Organization: Conclusion first, then evidence (Pyramid Principle). Each slide conveys only 1 core idea. Headings must be testable assertion sentences, not topic labels.
• Evidence-First: Use charts/tables/evidence blocks instead of long paragraphs; limit to 3-5 bullet points per slide.
• Data Visualization: Chart selection and labeling (axes/units/sources) must comply with references/VIS-GUIDE.md. If data is insufficient, provide "placeholder chart + list of missing fields."
• Accessibility: Color and text contrast must meet AA standards (see STYLE-GUIDE). Provide alt/readable descriptions for charts and images.
• Reusability: Use consistent naming, stable paths, reproducible output. Do not hard-code random numbers in code.
• Safety & Dependencies: Do not scrape the web without permission. Only run scripts when user provides data. If matplotlib/pandas are unavailable, fall back to text + placeholder diagram instructions.

Workflow Overview

Stage 0 - Archive Input: Record user's original request, defaults used, and assumptions made.

Stage 1 - Structure Goals: Rewrite the goal into "who takes what action when" (clear CTA).

**Stage 2 -

...