PPTX creation, editing, and analysis
🎯 Load Full PAI Context
Before starting any task with this skill, load complete PAI context:
read ~/.claude/skills/CORE/SKILL.md
This provides access to:
- Complete contact list (Angela, Bunny, Saša, Greg, team members)
- Stack preferences (TypeScript>Python, bun>npm, uv>pip)
- Security rules and repository safety protocols
- Response format requirements (structured emoji format)
- Voice IDs for agent routing (ElevenLabs)
- Personal preferences and operating instructions
🔀 When to Use This Sub-Skill
Explicit Triggers
Route to this sub-skill when user requests contain:
Creation Triggers:
- "create presentation", "new presentation", "make slides"
- "build PowerPoint", "generate pptx"
- "presentation from scratch"
Editing Triggers:
- "edit presentation", "modify slides", "update PowerPoint"
- "change slide content", "edit pptx"
Template Triggers:
- "use presentation template", "based on template"
- "apply template design", "template slides"
Design Triggers:
- "presentation design", "slide layout"
- "speaker notes", "add notes to slides"
- "pitch deck", "slide deck"
Contextual Triggers
Route to this sub-skill when:
- Working with .pptx files
- User mentions "PowerPoint"
- User mentions "pitch deck" or "slide deck"
- User mentions "keynote" (if exporting to pptx)
- Presentation-related file paths or operations
Workflow Routing
Once in this sub-skill, route to specific workflows:
Creation Workflow (html2pptx):
- "create presentation", "new slides", "build from scratch"
- No template mentioned
- → Read
html2pptx.md completely, use html2pptx.js
Template Workflow:
- "use template", "based on template", "apply template"
- Existing pptx file to use as template
- → Follow rearrange/replace workflow with inventory.py
Editing Workflow (OOXML):
- "edit presentation", "modify existing slides"
- Need to change specific content in existing pptx
- → Read
ooxml.md completely, use unpack/pack scripts
Text Extraction Workflow:
- "extract text", "read presentation", "what's in this pptx"
- → Use markitdown:
python -m markitdown file.pptx
Visual Analysis Workflow:
- "show slides", "thumbnail grid", "preview slides"
- → Use thumbnail.py script for grid visualization
Speaker Notes Workflow:
- "add speaker notes", "presenter notes"
- → Use OOXML workflow, edit notesSlide{N}.xml files
Overview
A user may ask you to create, edit, or analyze the contents of a .pptx file. A .pptx file is essentially a ZIP archive containing XML files and other resources that you can read or edit. You have different tools and workflows available for different tasks.
Reading and analyzing content
Text extraction
If you just need to read the text contents of a presentation, you should convert the document to markdown:
# Convert document to markdown
python -m markitdown path-to-file.pptx
Raw XML access
You need raw XML access for: comments, speaker notes, slide layouts, animations, design elements, and complex formatting. For any of these features, you'll need to unpack a presentation and read its raw XML contents.
Unpacking a file
python ooxml/Scripts/unpack.py <office_file> <output_dir>
Note: The unpack.py script is located at skills/pptx/ooxml/Scripts/unpack.py relative to the project root. If the script doesn't exist at this path, use find . -name "unpack.py" to locate it.
Key file structures
ppt/presentation.xml - Main presentation metadata and slide references
ppt/slides/slide{N}.xml - Individual slide contents (slide1.xml, slide2.xml, etc.)
ppt/notesSlides/notesSlide{N}.xml - Speaker notes for each slide
ppt/comments/modernComment_*.xml - Comments for specific slides
ppt/slideLayouts/ - Layout templates for slides
ppt/slideMasters/ - Master slide templates
ppt/theme/ - Theme and styling information
ppt/media/ - Images and other media files
Typography and color extraction
When given an example design to emulate: Always analyze the presentation's typography and colors first using the methods below:
- Read theme file: Check
ppt/theme/theme1.xml for colors (<a:clrScheme>) and fonts (<a:fontScheme>)
- Sample slide content: Examine
ppt/slides/slide1.xml for actual font usage (<a:rPr>) and colors
- Search for patterns: Use grep to find color (
<a:solidFill>, <a:srgbClr>) and font references across all XML files
Creating a new PowerPoint presentation without a template
When creating a new PowerPoint presentation from scratch, use the html2pptx workflow to convert HTML slides to PowerPoint with accurate positioning.
Design Principles
CRITICAL: Before creating any presentation, analyze the content and choose appropriate design elements:
- Consider the subject matter: What is this presentation about? What tone, industry, or mood does it suggest?
- Check for branding: If the user mentions a company/organization, consider their brand colors and identity
- Match palette to content: Select colors that reflect the subject
- State your approach: Explain your design choices before writing code
Requirements:
- ✅ State your content-informed design approach BEFORE writing code
- ✅ Use web-safe fonts only: Arial, Helvetica, Times New Roman, Georgia, Courier New, Verdana, Tahoma, Trebuchet MS, Impact
- ✅ Create clear visual hierarchy through size, weight, and color
- ✅ Ensure readability: strong contrast, appropriately sized text, clean alignment
- ✅ Be consistent: repeat patterns, spacing, and visual language across slides
Color Palette Selection
Choosing colors creatively:
- Think beyond defaults: What colors genuinely match this specific topic? Avoid autopilot choices.
- Consider multiple angles: Topic, industry, mood, energy level, target audience, brand identity (if mentioned)
- Be adventurous: Try unexpected combinations - a healthcare presentation doesn't have to be green, finance doesn't have to be navy
- Build your palette: Pick 3-5 colors that work together (dominant colors + supporting tones + accent)
- Ensure contrast: Text must be clearly readable on backgrounds
Example color palettes (use these to spark creativity - choose one, adapt it, or create your own):
- Classic Blue: Deep navy (#1C2833), slate gray (#2E4053), silver (#AAB7B8), off-white (#F4F6F6)
- Teal & Coral: Teal (#5EA8A7), deep teal (#277884), coral (#FE4447), white (#FFFFFF)
- Bold Red: Red (#C0392B), bright red (#E74C3C), orange (#F39C12), yellow (#F1C40F), green (#2ECC71)
- Warm Blush: Mauve (#A49393), blush (#EED6D3), rose (#E8B4B8), cream (#FAF7F2)
- Burgundy Luxury: Burgundy (#5D1D2E), crimson (#951233), rust (#C15937), gold (#997929)
- Deep Purple & Emerald: Purple (#B165FB), dark blue (#181B24), emerald (#40695B), white (#FFFFFF)
- Cream & Forest Green: Cream (#FFE1C7), forest green (#40695B), white (#FCFCFC)
- Pink & Purple: Pink (#F8275B), coral (#FF574A), rose (#FF737D), purple (#3D2F68)
- Lime & Plum: Lime (#C5DE82), plum (#7C3A5F), coral (#FD8C6E), blue-gray (#98ACB5)
- Black & Gold: Gold (#BF9A4A), black (#000000), cream (#F4F6F6)
- Sage & Terracotta: Sage (#87A96B), terracotta (#E07A5F), cream (#F4F1DE), charcoal (#2C2C2C)
- Charcoal & Red: Charcoal (#292929), red (#E33737), light gray (#CCCBCB)
- Vibrant Orange: Orange (#F96D00), light gray (#F2F2F2), charcoal (#222831)
- Forest Green: Black (#191A19), green (#4E9F3D), dark green (#1E5128), white (#FFFFFF)
- Retro Rainbow: Purple (#722880), pink (#D72D51), orange (#EB5C18), amber (#F08800), gold (#DEB600)
- Vintage Earthy: Mustard (#E3B448), sage (#CBD18F), forest green (#3A6B35), cream (#F4F1DE)
- Coastal Rose: Old rose (#AD7670), beaver (#B49886), eggshell (#F3ECDC), ash gray (#BFD5BE)
- Orange & Turquoise: Light orange (#FC993E), grayish turquoise (#667C6F), white (#FCFCFC)
Visual Details Options
Geometric Patterns:
- Diagonal section dividers instead of horizontal
- Asymmetric column widths (30/70, 40/60, 25/75)
- Rotated text headers at 90° or 270°
- Circular/hexagonal frames for images
- Triangular accent shapes in corners
- Overlapping shapes for depth
Border & Frame Treatments:
- Thick single-color borders (10-20pt) on one side only
- Double-line borders with contrasting colors
- Corner brackets instead of full frames
- L-shaped borders (top+left or bottom+right)
- Underline accents beneath headers (3-5pt thick)
Typography Treatments:
- Extreme size contrast (72pt headlines vs 11pt body)
- All-caps headers with wide letter spacing
- Numbered sections in oversized display type
- Monospace (Courier New) for data/stats/technical content
- Condensed fonts (Arial Narrow) for dense information
- Outlined text for emphasis
Chart & Data Styling:
- Monochrome charts with single accent color for key data
- Horizontal bar charts instead of vertical
- Dot plots instead of bar charts
- Minimal gridlines or none at all
- Data labels directly on elements (no legends)
- Oversized numbers for key metrics
Layout Innovations:
- Full-bleed images with text overlays
- Sidebar column (20-30% width) for navigation/context
- Modular grid systems (3×3, 4×4 blocks)
- Z-pattern or F-pattern content flow
- Floating text boxes over colored shapes
- Magazine-style multi-column layouts
Background Treatments:
- Solid color blocks occupying 40-60% of slide
- Gradient fills (vertical or diagonal only)
- Split backgrounds (two colors, diagonal or vertical)
- Edge-to-edge color bands
- Negative space as a design element
Layout Tips
When creating slides with charts or tables:
- Two-column layout (PREFERRED): Use a header spanning the full width, then two columns below - text/bullets in one column and the featured content in the other. This provides better balance and makes charts/tables more readable. Use flexbox with unequal column widths (e.g., 40%/60% split) to optimize space for each content type.
- Full-slide layout: Let the featured content (chart/table) take up the entire slide for maximum impact and readability
- NEVER vertically stack: Do not place charts/tables below text in a single column - this causes poor readability and layout issues
Workflow
- MANDATORY - READ ENTIRE FILE: Read
html2pptx.md completely from start to finish. NEVER set any range limits when reading this file. Read the full file content for detailed syntax, critical formatting rules, and best practices before proceeding with presentation creation.
- Create an HTML file for each slide with proper dimensions (e.g., 720pt × 405pt for 16:9)
- Use
<p>, <h1>-<h6>, <ul>, <ol> for all text content
- Use
class="placeholder" for areas where charts/tables will be added (render with gray background for visibility)
- CRITICAL: Rasterize gradients and icons as PNG images FIRST using Sharp, then reference in HTML
- LAYOUT: For slides with charts/tables/images, use either full-slide layout or two-column layout for better readability
- Create and run a JavaScript file using the
html2pptx.js library to convert HTML slides to PowerPoint and save the presentation
- Use the
html2pptx() function to process each HTML file
- Add charts and tables to placeholder areas using PptxGenJS API
- Save the presentation using
pptx.writeFile()
- Visual validation: Generate thumbnails and inspect for layout issues
- Create thumbnail grid:
python scripts/thumbnail.py output.pptx workspace/thumbnails --cols 4
- Read and carefully examine the thumbnail image for:
- Text cutoff: Text being cut off by header bars, shapes, or slide edges
- Text overlap: Text overlapping with other text or shapes
- Positioning issues: Content too close to slide boundaries or other elements
- Contrast issues: Insufficient contrast between text and backgrounds
- If issues found, adjust HTML margins/spacing/colors and regenerate the presentation
- Repeat until all slides are visually correct
Editing an existing PowerPoint presentation
When edit slides in an existing PowerPoint presentation, you need to work with the raw Office Open XML (OOXML) format. This involves unpacking the .pptx file, editing the XML content, and repacking it.
Workflow
- MANDATORY - READ ENTIRE FILE: Read
ooxml.md (~500 lines) completely from start to finish. NEVER set any range limits when reading this file. Read the full file content for detailed guidance on OOXML structure and editing workflows before any presentation editing.
- Unpack the presentation:
python ooxml/Scripts/unpack.py <office_file> <output_dir>
- Edit the XML files (primarily
ppt/slides/slide{N}.xml and related files)
- CRITICAL: Validate immediately after each edit and fix any validation errors before proceeding:
python ooxml/Scripts/validate.py <dir> --original <file>
- Pack the final presentation:
python ooxml/Scripts/pack.py <input_directory> <office_file>
Creating a new PowerPoint presentation using a template
When you need to create a presentation that follows an existing template's design, you'll need to duplicate and re-arrange template slides before then replacing placeholder context.
Workflow
Extract template text AND create visual thumbnail grid:
- Extract text:
python -m markitdown template.pptx > template-content.md
- Read
template-content.md: Read the entire file to understand the contents of the template presentation. NEVER set any range limits when reading this file.
- Create thumbnail grids:
python scripts/thumbnail.py template.pptx
- See Creating Thumbnail Grids section for more details
Analyze template and save inventory to a file:
- Visual Analysis: Review thumbnail grid(s) to understand slide layouts, design patterns, and visual structure
- Create and save a template inventory file at
template-inventory.md containing:# Template Inventory Analysis
**Total Slides: [count]**
**IMPORTANT: Slides are 0-indexed (first slide = 0, last slide = count-1)**
## [Category Name]
- Slide 0: [Layout code if available] - Description/purpose
- Slide 1: [Layout code] - Description/purpose
- Slide 2: [Layout code] - Description/purpose
[... EVERY slide must be listed individually with its index ...]
- Using the thumbnail grid: Reference the visual thumbnails to identify:
- Layout patterns (title slides, content layouts, section dividers)
- Image placeholder locations and counts
- Design consistency across slide groups
- Visual hierarchy and structure
- This inventory file is REQUIRED for selecting appropriate templates in the next step
Create presentation outline based on template inventory:
- Review available templates from step 2.
- Choose an intro or title template for the first slide. This should be one of the first templates.
- Choose safe, text-based layouts for the other slides.
- CRITICAL: Match layout structure to actual content:
- Single-column layouts: Use for unified narrative or single topic
- Two-column layouts: Use ONLY when you have exactly 2 distinct items/concepts
- Three-column layouts: Use ONLY when you have exactly 3 distinct items/concepts
- Image + text layouts: Use ONLY when you have actual images to insert
- Quote layouts: Use ONLY for actual quotes from people (with attribution), never for emphasis
- Never use layouts with more placeholders than you have content
- If you have 2 items, don't force them into a 3-column layout
- If you have 4+ items, consider breaking into multiple slides or using a list format
- Count your actual content pieces BEFORE selecting the layout
- Verify each placeholder in the chosen layout will be filled with meaningful content
- Select one option representing the best layout for each content section.
- Save
outline.md with content AND template mapping that leverages available designs
- Example template mapping:
# Template slides to use (0-based indexing)
# WARNING: Verify indices are within range! Template with 73 slides has indices 0-72
# Mapping: slide numbers from outline -> template slide indices
template_mapping = [
0, # Use slide 0 (Title/Cover)
34, # Use slide 34 (B1: Title and body)
34, # Use slide 34 again (duplicate for second B1)
50, # Use slide 50 (E1: Quote)
54, # Use slide 54 (F2: Closing + Text)
]
Duplicate, reorder, and delete slides using rearrange.py:
- Use the
scripts/rearrange.py script to create a new presentation with slides in the desired order:python scripts/rearrange.py template.pptx working.pptx 0,34,34,50,52
- The script handles duplicating repeated slides, deleting unused slides, and reordering automatically
- Slide indices are 0-based (first slide is 0, second is 1, etc.)
- The same slide index can appear multiple times to duplicate that slide
Extract ALL text using the inventory.py script:
Run inventory extraction:
python scripts/inventory.py working.pptx text-inventory.json
Read text-inventory.json: Read the entire text-inventory.json file to understand all shapes and their properties. NEVER set any range limits when reading this file.
The inventory JSON structure:
{
"slide-0": {
"shape-0": {
"placeholder_type": "TITLE", // or null for non-placeholders
"left": 1.5, // position in inches
"top": 2.0,
"width": 7.5,
"height": 1.2,
"paragraphs": [
{
"text": "Paragraph text",
// Optional properties (only included when non-default):
"bullet": true, // explicit bullet detected
"level": 0, // only included when bullet is true
"alignment": "CENTER", // CENTER, RIGHT (not LEFT)
"space_before": 10.0, // space before paragraph in points
"space_after": 6.0, // space after paragraph in points
"line_spacing": 22.4, // line spacing in points
"font_name": "Arial", // from first run
"font_size": 14.0, // in points
"bold": true,
"italic": false,
"underline": false,
"color": "FF0000" // RGB color
}
]
}
}
}
Key features:
- Slides: Named as "slide-0", "slide-1", etc.
- Shapes: Ordered by visual position (top-to-bottom, left-to-right) as "shape-0", "shape-1", etc.
- Placeholder types: TITLE, CENTER_TITLE, SUBTITLE, BODY, OBJECT, or null
- Default font size:
default_font_size in points extracted from layout placeholders (when available)
- Slide numbers are filtered: Shapes with SLIDE_NUMBER placeholder type are automatically excluded from inventory
- Bullets: When
bullet: true, level is always included (even if 0)
- Spacing:
space_before, space_after, and line_spacing in points (only included when set)
- Colors:
color for RGB (e.g., "FF0000"), theme_color for theme colors (e.g., "DARK_1")
- Properties: Only non-default values are included in the output
Generate replacement text and save the data to a JSON file
Based on the text inventory from the previous step:
- CRITICAL: First verify which shapes exist in the inventory - only reference shapes that are actually present
- VALIDATION: The replace.py script will validate that all shapes in your replacement JSON exist in the inventory
- If you reference a non-existent shape, you'll get an error showing available shapes
- If you reference a non-existent slide, you'll get an error indicating the slide doesn't exist
- All validation errors are shown at once before the script exits
- IMPORTANT: The replace.py script uses inventory.py internally to identify ALL text shapes
- AUTOMATIC CLEARING: ALL text shapes from the inventory will be cleared unless you provide "paragraphs" for them
- Add a "paragraphs" field to shapes that need content (not "replacement_paragraphs")
- Shapes without "paragraphs" in the replacement JSON will have their text cleared automatically
- Paragraphs with bullets will be automatically left aligned. Don't set the
alignment property on when "bullet": true
- Generate appropriate replacement content for placeholder text
- Use shape size to determine appropriate content length
- CRITICAL: Include paragraph properties from the original inventory - don't just provide text
- IMPORTANT: When bullet: true, do NOT include bullet symbols (•, -, *) in text - they're added automatically
- ESSENTIAL FORMATTING RULES:
- Headers/titles should typically have
"bold": true
- List items should have
"bullet": true, "level": 0 (level is required when bullet is true)
- Preserve any alignment properties (e.g.,
"alignment": "CENTER" for centered text)
- Include font properties when different from default (e.g.,
"font_size": 14.0, "font_name": "Lora")
- Colors: Use
"color": "FF0000" for RGB or "theme_color": "DARK_1" for theme colors
- The replacement script expects properly formatted paragraphs, not just text strings
- Overlapping shapes: Prefer shapes with larger default_font_size or more appropriate placeholder_type
- Save the updated inventory with replacements to
replacement-text.json
- WARNING: Different template layouts have different shape counts - always check the actual inventory before creating replacements
Example paragraphs field showing proper formatting:
"paragraphs": [
{
"text": "New presentation title text",
"alignment": "CENTER",
"bold": true
},
{
"text": "Section Header",
"bold": true
},
{
"text": "First bullet point without bullet symbol",
"bullet": true,
"level": 0
},
{
"text": "Red colored text",
"color": "FF0000"
},
{
"text": "Theme colored text",
"theme_color": "DARK_1"
},
{
"text": "Regular paragraph text without special formatting"
}
]
Shapes not listed in the replacement JSON are automatically cleared:
{
"slide-0": {
"shape-0": {
"paragraphs": [...] // This shape gets new text
}
// shape-1 and shape-2 from inventory will be cleared automatically
}
}
Common formatting patterns for presentations:
- Title slides: Bold text, sometimes centered
- Section headers within slides: Bold text
- Bullet lists: Each item needs
"bullet": true, "level": 0
- Body text: Usually no special properties needed
- Quotes: May have special alignment or font properties
Apply replacements using the replace.py script
python scripts/replace.py working.pptx replacement-text.json output.pptx
The script will:
- First extract the inventory of ALL text shapes using functions from inventory.py
- Validate that all shapes in the replacement JSON exist in the inventory
- Clear text from ALL shapes identified in the inventory
- Apply new text only to shapes with "paragraphs" defined in the replacement JSON
- Preserve formatting by applying paragraph properties from the JSON
- Handle bullets, alignment, font properties, and colors automatically
- Save the updated presentation
Example validation errors:
ERROR: Invalid shapes in replacement JSON:
- Shape 'shape-99' not found on 'slide-0'. Available shapes: shape-0, shape-1, shape-4
- Slide 'slide-999' not found in inventory
ERROR: Replacement text made overflow worse in these shapes:
- slide-0/shape-2: overflow worsened by 1.25" (was 0.00", now 1.25")
Creating Thumbnail Grids
To create visual thumbnail grids of PowerPoint slides for quick analysis and reference:
python scripts/thumbnail.py template.pptx [output_prefix]
Features:
- Creates:
thumbnails.jpg (or thumbnails-1.jpg, thumbnails-2.jpg, etc. for large decks)
- Default: 5 columns, max 30 slides per grid (5×6)
- Custom prefix:
python scripts/thumbnail.py template.pptx my-grid
- Note: The output prefix should include the path if you want output in a specific directory (e.g.,
workspace/my-grid)
- Adjust columns:
--cols 4 (range: 3-6, affects slides per grid)
- Grid limits: 3 cols = 12 slides/grid, 4 cols = 20, 5 cols = 30, 6 cols = 42
- Slides are zero-indexed (Slide 0, Slide 1, etc.)
Use cases:
- Template analysis: Quickly understand slide layouts and design patterns
- Content review: Visual overview of entire presentation
- Navigation reference: Find specific slides by their visual appearance
- Quality check: Verify all slides are properly formatted
Examples:
# Basic usage
python scripts/thumbnail.py presentation.pptx
# Combine options: custom name, columns
python scripts/thumbnail.py template.pptx analysis --cols 4
Converting Slides to Images
To visually analyze PowerPoint slides, convert them to images using a two-step process:
Convert PPTX to PDF:
soffice --headless --convert-to pdf template.pptx
Convert PDF pages to JPEG images:
pdftoppm -jpeg -r 150 template.pdf slide
This creates files like slide-1.jpg, slide-2.jpg, etc.
Options:
-r 150: Sets resolution to 150 DPI (adjust for quality/size balance)
-jpeg: Output JPEG format (use -png for PNG if preferred)
-f N: First page to convert (e.g., -f 2 starts from page 2)
-l N: Last page to convert (e.g., -l 5 stops at page 5)
slide: Prefix for output files
Example for specific range:
pdftoppm -jpeg -r 150 -f 2 -l 5 template.pdf slide # Converts only pages 2-5
Code Style Guidelines
IMPORTANT: When generating code for PPTX operations:
- Write concise code
- Avoid verbose variable names and redundant operations
- Avoid unnecessary print statements
Examples
Example 1: Create a presentation from scratch
User: "Make a pitch deck for my startup idea"
→ Reads html2pptx.md for syntax
→ Creates HTML slides with proper styling and layout
→ Converts to PowerPoint, validates with thumbnails
Example 2: Use a template
User: "Create slides using this company template"
→ Extracts template inventory with thumbnail grid
→ Maps content to appropriate slide layouts
→ Replaces placeholder text, preserves formatting
Example 3: Add speaker notes to existing deck
User: "Add speaker notes to my presentation"
→ Unpacks PPTX, navigates to notesSlide XML files
→ Adds notes content to each slide
→ Repacks and validates the presentation
Dependencies
Required dependencies (should already be installed):
- markitdown:
pip install "markitdown[pptx]" (for text extraction from presentations)
- pptxgenjs:
npm install -g pptxgenjs (for creating presentations via html2pptx)
- playwright:
npm install -g playwright (for HTML rendering in html2pptx)
- react-icons:
npm install -g react-icons react react-dom (for icons)
- sharp:
npm install -g sharp (for SVG rasterization and image processing)
- LibreOffice:
sudo apt-get install libreoffice (for PDF conversion)
- Poppler:
sudo apt-get install poppler-utils (for pdftoppm to convert PDF to images)
- defusedxml:
pip install defusedxml (for secure XML parsing)
1---2name: pptx-23description: PowerPoint processing. USE WHEN pptx, PowerPoint, slides. SkillSearch('pptx') for docs.4---5
6# PPTX creation, editing, and analysis
7
8## 🎯 Load Full PAI Context
9
10**Before starting any task with this skill, load complete PAI context:**
11
12`read ~/.claude/skills/CORE/SKILL.md`
13
14This provides access to:
15- Complete contact list (Angela, Bunny, Saša, Greg, team members)
16- Stack preferences (TypeScript>Python, bun>npm, uv>pip)
17- Security rules and repository safety protocols
18- Response format requirements (structured emoji format)
19- Voice IDs for agent routing (ElevenLabs)
20- Personal preferences and operating instructions
21
22## 🔀 When to Use This Sub-Skill
23
24### Explicit Triggers
25Route to this sub-skill when user requests contain:
26
27**Creation Triggers:**
28- "create presentation", "new presentation", "make slides"
29- "build PowerPoint", "generate pptx"
30- "presentation from scratch"
31
32**Editing Triggers:**
33- "edit presentation", "modify slides", "update PowerPoint"
34- "change slide content", "edit pptx"
35
36**Template Triggers:**
37- "use presentation template", "based on template"
38- "apply template design", "template slides"
39
40**Design Triggers:**
41- "presentation design", "slide layout"
42- "speaker notes", "add notes to slides"
43- "pitch deck", "slide deck"
44
45### Contextual Triggers
46Route to this sub-skill when:
47- Working with .pptx files
48- User mentions "PowerPoint"
49- User mentions "pitch deck" or "slide deck"
50- User mentions "keynote" (if exporting to pptx)
51- Presentation-related file paths or operations
52
53### Workflow Routing
54
55Once in this sub-skill, route to specific workflows:
56
57**Creation Workflow (html2pptx):**
58- "create presentation", "new slides", "build from scratch"
59- No template mentioned
60- → Read `html2pptx.md` completely, use html2pptx.js
61
62**Template Workflow:**
63- "use template", "based on template", "apply template"
64- Existing pptx file to use as template
65- → Follow rearrange/replace workflow with inventory.py
66
67**Editing Workflow (OOXML):**
68- "edit presentation", "modify existing slides"
69- Need to change specific content in existing pptx
70- → Read `ooxml.md` completely, use unpack/pack scripts
71
72**Text Extraction Workflow:**
73- "extract text", "read presentation", "what's in this pptx"
74- → Use markitdown: `python -m markitdown file.pptx`
75
76**Visual Analysis Workflow:**
77- "show slides", "thumbnail grid", "preview slides"
78- → Use thumbnail.py script for grid visualization
79
80**Speaker Notes Workflow:**
81- "add speaker notes", "presenter notes"
82- → Use OOXML workflow, edit notesSlide{N}.xml files
83
84## Overview
85
86A user may ask you to create, edit, or analyze the contents of a .pptx file. A .pptx file is essentially a ZIP archive containing XML files and other resources that you can read or edit. You have different tools and workflows available for different tasks.
87
88## Reading and analyzing content
89
90### Text extraction
91If you just need to read the text contents of a presentation, you should convert the document to markdown:
92
93```bash
94# Convert document to markdown
95python -m markitdown path-to-file.pptx
96```
97
98### Raw XML access
99You need raw XML access for: comments, speaker notes, slide layouts, animations, design elements, and complex formatting. For any of these features, you'll need to unpack a presentation and read its raw XML contents.
100
101#### Unpacking a file
102`python ooxml/Scripts/unpack.py <office_file> <output_dir>`
103
104**Note**: The unpack.py script is located at `skills/pptx/ooxml/Scripts/unpack.py` relative to the project root. If the script doesn't exist at this path, use `find . -name "unpack.py"` to locate it.
105
106#### Key file structures
107* `ppt/presentation.xml` - Main presentation metadata and slide references
108* `ppt/slides/slide{N}.xml` - Individual slide contents (slide1.xml, slide2.xml, etc.)
109* `ppt/notesSlides/notesSlide{N}.xml` - Speaker notes for each slide
110* `ppt/comments/modernComment_*.xml` - Comments for specific slides
111* `ppt/slideLayouts/` - Layout templates for slides
112* `ppt/slideMasters/` - Master slide templates
113* `ppt/theme/` - Theme and styling information
114* `ppt/media/` - Images and other media files
115
116#### Typography and color extraction
117**When given an example design to emulate**: Always analyze the presentation's typography and colors first using the methods below:
1181. **Read theme file**: Check `ppt/theme/theme1.xml` for colors (`<a:clrScheme>`) and fonts (`<a:fontScheme>`)
1192. **Sample slide content**: Examine `ppt/slides/slide1.xml` for actual font usage (`<a:rPr>`) and colors
1203. **Search for patterns**: Use grep to find color (`<a:solidFill>`, `<a:srgbClr>`) and font references across all XML files
121
122## Creating a new PowerPoint presentation **without a template**
123
124When creating a new PowerPoint presentation from scratch, use the **html2pptx** workflow to convert HTML slides to PowerPoint with accurate positioning.
125
126### Design Principles
127
128**CRITICAL**: Before creating any presentation, analyze the content and choose appropriate design elements:
1291. **Consider the subject matter**: What is this presentation about? What tone, industry, or mood does it suggest?
1302. **Check for branding**: If the user mentions a company/organization, consider their brand colors and identity
1313. **Match palette to content**: Select colors that reflect the subject
1324. **State your approach**: Explain your design choices before writing code
133
134**Requirements**:
135- ✅ State your content-informed design approach BEFORE writing code
136- ✅ Use web-safe fonts only: Arial, Helvetica, Times New Roman, Georgia, Courier New, Verdana, Tahoma, Trebuchet MS, Impact
137- ✅ Create clear visual hierarchy through size, weight, and color
138- ✅ Ensure readability: strong contrast, appropriately sized text, clean alignment
139- ✅ Be consistent: repeat patterns, spacing, and visual language across slides
140
141#### Color Palette Selection
142
143**Choosing colors creatively**:
144- **Think beyond defaults**: What colors genuinely match this specific topic? Avoid autopilot choices.
145- **Consider multiple angles**: Topic, industry, mood, energy level, target audience, brand identity (if mentioned)
146- **Be adventurous**: Try unexpected combinations - a healthcare presentation doesn't have to be green, finance doesn't have to be navy
147- **Build your palette**: Pick 3-5 colors that work together (dominant colors + supporting tones + accent)
148- **Ensure contrast**: Text must be clearly readable on backgrounds
149
150**Example color palettes** (use these to spark creativity - choose one, adapt it, or create your own):
151
1521. **Classic Blue**: Deep navy (#1C2833), slate gray (#2E4053), silver (#AAB7B8), off-white (#F4F6F6)
1532. **Teal & Coral**: Teal (#5EA8A7), deep teal (#277884), coral (#FE4447), white (#FFFFFF)
1543. **Bold Red**: Red (#C0392B), bright red (#E74C3C), orange (#F39C12), yellow (#F1C40F), green (#2ECC71)
1554. **Warm Blush**: Mauve (#A49393), blush (#EED6D3), rose (#E8B4B8), cream (#FAF7F2)
1565. **Burgundy Luxury**: Burgundy (#5D1D2E), crimson (#951233), rust (#C15937), gold (#997929)
1576. **Deep Purple & Emerald**: Purple (#B165FB), dark blue (#181B24), emerald (#40695B), white (#FFFFFF)
1587. **Cream & Forest Green**: Cream (#FFE1C7), forest green (#40695B), white (#FCFCFC)
1598. **Pink & Purple**: Pink (#F8275B), coral (#FF574A), rose (#FF737D), purple (#3D2F68)
1609. **Lime & Plum**: Lime (#C5DE82), plum (#7C3A5F), coral (#FD8C6E), blue-gray (#98ACB5)
16110. **Black & Gold**: Gold (#BF9A4A), black (#000000), cream (#F4F6F6)
16211. **Sage & Terracotta**: Sage (#87A96B), terracotta (#E07A5F), cream (#F4F1DE), charcoal (#2C2C2C)
16312. **Charcoal & Red**: Charcoal (#292929), red (#E33737), light gray (#CCCBCB)
16413. **Vibrant Orange**: Orange (#F96D00), light gray (#F2F2F2), charcoal (#222831)
16514. **Forest Green**: Black (#191A19), green (#4E9F3D), dark green (#1E5128), white (#FFFFFF)
16615. **Retro Rainbow**: Purple (#722880), pink (#D72D51), orange (#EB5C18), amber (#F08800), gold (#DEB600)
16716. **Vintage Earthy**: Mustard (#E3B448), sage (#CBD18F), forest green (#3A6B35), cream (#F4F1DE)
16817. **Coastal Rose**: Old rose (#AD7670), beaver (#B49886), eggshell (#F3ECDC), ash gray (#BFD5BE)
16918. **Orange & Turquoise**: Light orange (#FC993E), grayish turquoise (#667C6F), white (#FCFCFC)
170
171#### Visual Details Options
172
173**Geometric Patterns**:
174- Diagonal section dividers instead of horizontal
175- Asymmetric column widths (30/70, 40/60, 25/75)
176- Rotated text headers at 90° or 270°
177- Circular/hexagonal frames for images
178- Triangular accent shapes in corners
179- Overlapping shapes for depth
180
181**Border & Frame Treatments**:
182- Thick single-color borders (10-20pt) on one side only
183- Double-line borders with contrasting colors
184- Corner brackets instead of full frames
185- L-shaped borders (top+left or bottom+right)
186- Underline accents beneath headers (3-5pt thick)
187
188**Typography Treatments**:
189- Extreme size contrast (72pt headlines vs 11pt body)
190- All-caps headers with wide letter spacing
191- Numbered sections in oversized display type
192- Monospace (Courier New) for data/stats/technical content
193- Condensed fonts (Arial Narrow) for dense information
194- Outlined text for emphasis
195
196**Chart & Data Styling**:
197- Monochrome charts with single accent color for key data
198- Horizontal bar charts instead of vertical
199- Dot plots instead of bar charts
200- Minimal gridlines or none at all
201- Data labels directly on elements (no legends)
202- Oversized numbers for key metrics
203
204**Layout Innovations**:
205- Full-bleed images with text overlays
206- Sidebar column (20-30% width) for navigation/context
207- Modular grid systems (3×3, 4×4 blocks)
208- Z-pattern or F-pattern content flow
209- Floating text boxes over colored shapes
210- Magazine-style multi-column layouts
211
212**Background Treatments**:
213- Solid color blocks occupying 40-60% of slide
214- Gradient fills (vertical or diagonal only)
215- Split backgrounds (two colors, diagonal or vertical)
216- Edge-to-edge color bands
217- Negative space as a design element
218
219### Layout Tips
220**When creating slides with charts or tables:**
221- **Two-column layout (PREFERRED)**: Use a header spanning the full width, then two columns below - text/bullets in one column and the featured content in the other. This provides better balance and makes charts/tables more readable. Use flexbox with unequal column widths (e.g., 40%/60% split) to optimize space for each content type.
222- **Full-slide layout**: Let the featured content (chart/table) take up the entire slide for maximum impact and readability
223- **NEVER vertically stack**: Do not place charts/tables below text in a single column - this causes poor readability and layout issues
224
225### Workflow
2261. **MANDATORY - READ ENTIRE FILE**: Read [`html2pptx.md`](html2pptx.md) completely from start to finish. **NEVER set any range limits when reading this file.** Read the full file content for detailed syntax, critical formatting rules, and best practices before proceeding with presentation creation.
2272. Create an HTML file for each slide with proper dimensions (e.g., 720pt × 405pt for 16:9)
228 - Use `<p>`, `<h1>`-`<h6>`, `<ul>`, `<ol>` for all text content
229 - Use `class="placeholder"` for areas where charts/tables will be added (render with gray background for visibility)
230 - **CRITICAL**: Rasterize gradients and icons as PNG images FIRST using Sharp, then reference in HTML
231 - **LAYOUT**: For slides with charts/tables/images, use either full-slide layout or two-column layout for better readability
2323. Create and run a JavaScript file using the [`html2pptx.js`](scripts/html2pptx.js) library to convert HTML slides to PowerPoint and save the presentation
233 - Use the `html2pptx()` function to process each HTML file
234 - Add charts and tables to placeholder areas using PptxGenJS API
235 - Save the presentation using `pptx.writeFile()`
2364. **Visual validation**: Generate thumbnails and inspect for layout issues
237 - Create thumbnail grid: `python scripts/thumbnail.py output.pptx workspace/thumbnails --cols 4`
238 - Read and carefully examine the thumbnail image for:
239 - **Text cutoff**: Text being cut off by header bars, shapes, or slide edges
240 - **Text overlap**: Text overlapping with other text or shapes
241 - **Positioning issues**: Content too close to slide boundaries or other elements
242 - **Contrast issues**: Insufficient contrast between text and backgrounds
243 - If issues found, adjust HTML margins/spacing/colors and regenerate the presentation
244 - Repeat until all slides are visually correct
245
246## Editing an existing PowerPoint presentation
247
248When edit slides in an existing PowerPoint presentation, you need to work with the raw Office Open XML (OOXML) format. This involves unpacking the .pptx file, editing the XML content, and repacking it.
249
250### Workflow
2511. **MANDATORY - READ ENTIRE FILE**: Read [`ooxml.md`](ooxml.md) (~500 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Read the full file content for detailed guidance on OOXML structure and editing workflows before any presentation editing.
2522. Unpack the presentation: `python ooxml/Scripts/unpack.py <office_file> <output_dir>`
2533. Edit the XML files (primarily `ppt/slides/slide{N}.xml` and related files)
2544. **CRITICAL**: Validate immediately after each edit and fix any validation errors before proceeding: `python ooxml/Scripts/validate.py <dir> --original <file>`
2555. Pack the final presentation: `python ooxml/Scripts/pack.py <input_directory> <office_file>`
256
257## Creating a new PowerPoint presentation **using a template**
258
259When you need to create a presentation that follows an existing template's design, you'll need to duplicate and re-arrange template slides before then replacing placeholder context.
260
261### Workflow
2621. **Extract template text AND create visual thumbnail grid**:
263 * Extract text: `python -m markitdown template.pptx > template-content.md`
264 * Read `template-content.md`: Read the entire file to understand the contents of the template presentation. **NEVER set any range limits when reading this file.**
265 * Create thumbnail grids: `python scripts/thumbnail.py template.pptx`
266 * See [Creating Thumbnail Grids](#creating-thumbnail-grids) section for more details
267
2682. **Analyze template and save inventory to a file**:
269 * **Visual Analysis**: Review thumbnail grid(s) to understand slide layouts, design patterns, and visual structure
270 * Create and save a template inventory file at `template-inventory.md` containing:
271 ```markdown
272 # Template Inventory Analysis
273 **Total Slides: [count]**
274 **IMPORTANT: Slides are 0-indexed (first slide = 0, last slide = count-1)**
275
276 ## [Category Name]
277 - Slide 0: [Layout code if available] - Description/purpose
278 - Slide 1: [Layout code] - Description/purpose
279 - Slide 2: [Layout code] - Description/purpose
280 [... EVERY slide must be listed individually with its index ...]
281 ```
282 * **Using the thumbnail grid**: Reference the visual thumbnails to identify:
283 - Layout patterns (title slides, content layouts, section dividers)
284 - Image placeholder locations and counts
285 - Design consistency across slide groups
286 - Visual hierarchy and structure
287 * This inventory file is REQUIRED for selecting appropriate templates in the next step
288
2893. **Create presentation outline based on template inventory**:
290 * Review available templates from step 2.
291 * Choose an intro or title template for the first slide. This should be one of the first templates.
292 * Choose safe, text-based layouts for the other slides.
293 * **CRITICAL: Match layout structure to actual content**:
294 - Single-column layouts: Use for unified narrative or single topic
295 - Two-column layouts: Use ONLY when you have exactly 2 distinct items/concepts
296 - Three-column layouts: Use ONLY when you have exactly 3 distinct items/concepts
297 - Image + text layouts: Use ONLY when you have actual images to insert
298 - Quote layouts: Use ONLY for actual quotes from people (with attribution), never for emphasis
299 - Never use layouts with more placeholders than you have content
300 - If you have 2 items, don't force them into a 3-column layout
301 - If you have 4+ items, consider breaking into multiple slides or using a list format
302 * Count your actual content pieces BEFORE selecting the layout
303 * Verify each placeholder in the chosen layout will be filled with meaningful content
304 * Select one option representing the **best** layout for each content section.
305 * Save `outline.md` with content AND template mapping that leverages available designs
306 * Example template mapping:
307 ```
308 # Template slides to use (0-based indexing)
309 # WARNING: Verify indices are within range! Template with 73 slides has indices 0-72
310 # Mapping: slide numbers from outline -> template slide indices
311 template_mapping = [
312 0, # Use slide 0 (Title/Cover)
313 34, # Use slide 34 (B1: Title and body)
314 34, # Use slide 34 again (duplicate for second B1)
315 50, # Use slide 50 (E1: Quote)
316 54, # Use slide 54 (F2: Closing + Text)
317 ]
318 ```
319
3204. **Duplicate, reorder, and delete slides using `rearrange.py`**:
321 * Use the `scripts/rearrange.py` script to create a new presentation with slides in the desired order:
322 ```bash
323 python scripts/rearrange.py template.pptx working.pptx 0,34,34,50,52
324 ```
325 * The script handles duplicating repeated slides, deleting unused slides, and reordering automatically
326 * Slide indices are 0-based (first slide is 0, second is 1, etc.)
327 * The same slide index can appear multiple times to duplicate that slide
328
3295. **Extract ALL text using the `inventory.py` script**:
330 * **Run inventory extraction**:
331 ```bash
332 python scripts/inventory.py working.pptx text-inventory.json
333 ```
334 * **Read text-inventory.json**: Read the entire text-inventory.json file to understand all shapes and their properties. **NEVER set any range limits when reading this file.**
335
336 * The inventory JSON structure:
337 ```json
338 {
339 "slide-0": {
340 "shape-0": {
341 "placeholder_type": "TITLE", // or null for non-placeholders
342 "left": 1.5, // position in inches
343 "top": 2.0,
344 "width": 7.5,
345 "height": 1.2,
346 "paragraphs": [
347 {
348 "text": "Paragraph text",
349 // Optional properties (only included when non-default):
350 "bullet": true, // explicit bullet detected
351 "level": 0, // only included when bullet is true
352 "alignment": "CENTER", // CENTER, RIGHT (not LEFT)
353 "space_before": 10.0, // space before paragraph in points
354 "space_after": 6.0, // space after paragraph in points
355 "line_spacing": 22.4, // line spacing in points
356 "font_name": "Arial", // from first run
357 "font_size": 14.0, // in points
358 "bold": true,
359 "italic": false,
360 "underline": false,
361 "color": "FF0000" // RGB color
362 }
363 ]
364 }
365 }
366 }
367 ```
368
369 * Key features:
370 - **Slides**: Named as "slide-0", "slide-1", etc.
371 - **Shapes**: Ordered by visual position (top-to-bottom, left-to-right) as "shape-0", "shape-1", etc.
372 - **Placeholder types**: TITLE, CENTER_TITLE, SUBTITLE, BODY, OBJECT, or null
373 - **Default font size**: `default_font_size` in points extracted from layout placeholders (when available)
374 - **Slide numbers are filtered**: Shapes with SLIDE_NUMBER placeholder type are automatically excluded from inventory
375 - **Bullets**: When `bullet: true`, `level` is always included (even if 0)
376 - **Spacing**: `space_before`, `space_after`, and `line_spacing` in points (only included when set)
377 - **Colors**: `color` for RGB (e.g., "FF0000"), `theme_color` for theme colors (e.g., "DARK_1")
378 - **Properties**: Only non-default values are included in the output
379
3806. **Generate replacement text and save the data to a JSON file**
381 Based on the text inventory from the previous step:
382 - **CRITICAL**: First verify which shapes exist in the inventory - only reference shapes that are actually present
383 - **VALIDATION**: The replace.py script will validate that all shapes in your replacement JSON exist in the inventory
384 - If you reference a non-existent shape, you'll get an error showing available shapes
385 - If you reference a non-existent slide, you'll get an error indicating the slide doesn't exist
386 - All validation errors are shown at once before the script exits
387 - **IMPORTANT**: The replace.py script uses inventory.py internally to identify ALL text shapes
388 - **AUTOMATIC CLEARING**: ALL text shapes from the inventory will be cleared unless you provide "paragraphs" for them
389 - Add a "paragraphs" field to shapes that need content (not "replacement_paragraphs")
390 - Shapes without "paragraphs" in the replacement JSON will have their text cleared automatically
391 - Paragraphs with bullets will be automatically left aligned. Don't set the `alignment` property on when `"bullet": true`
392 - Generate appropriate replacement content for placeholder text
393 - Use shape size to determine appropriate content length
394 - **CRITICAL**: Include paragraph properties from the original inventory - don't just provide text
395 - **IMPORTANT**: When bullet: true, do NOT include bullet symbols (•, -, *) in text - they're added automatically
396 - **ESSENTIAL FORMATTING RULES**:
397 - Headers/titles should typically have `"bold": true`
398 - List items should have `"bullet": true, "level": 0` (level is required when bullet is true)
399 - Preserve any alignment properties (e.g., `"alignment": "CENTER"` for centered text)
400 - Include font properties when different from default (e.g., `"font_size": 14.0`, `"font_name": "Lora"`)
401 - Colors: Use `"color": "FF0000"` for RGB or `"theme_color": "DARK_1"` for theme colors
402 - The replacement script expects **properly formatted paragraphs**, not just text strings
403 - **Overlapping shapes**: Prefer shapes with larger default_font_size or more appropriate placeholder_type
404 - Save the updated inventory with replacements to `replacement-text.json`
405 - **WARNING**: Different template layouts have different shape counts - always check the actual inventory before creating replacements
406
407 Example paragraphs field showing proper formatting:
408 ```json
409 "paragraphs": [
410 {
411 "text": "New presentation title text",
412 "alignment": "CENTER",
413 "bold": true
414 },
415 {
416 "text": "Section Header",
417 "bold": true
418 },
419 {
420 "text": "First bullet point without bullet symbol",
421 "bullet": true,
422 "level": 0
423 },
424 {
425 "text": "Red colored text",
426 "color": "FF0000"
427 },
428 {
429 "text": "Theme colored text",
430 "theme_color": "DARK_1"
431 },
432 {
433 "text": "Regular paragraph text without special formatting"
434 }
435 ]
436 ```
437
438 **Shapes not listed in the replacement JSON are automatically cleared**:
439 ```json
440 {
441 "slide-0": {
442 "shape-0": {
443 "paragraphs": [...] // This shape gets new text
444 }
445 // shape-1 and shape-2 from inventory will be cleared automatically
446 }
447 }
448 ```
449
450 **Common formatting patterns for presentations**:
451 - Title slides: Bold text, sometimes centered
452 - Section headers within slides: Bold text
453 - Bullet lists: Each item needs `"bullet": true, "level": 0`
454 - Body text: Usually no special properties needed
455 - Quotes: May have special alignment or font properties
456
4577. **Apply replacements using the `replace.py` script**
458 ```bash
459 python scripts/replace.py working.pptx replacement-text.json output.pptx
460 ```
461
462 The script will:
463 - First extract the inventory of ALL text shapes using functions from inventory.py
464 - Validate that all shapes in the replacement JSON exist in the inventory
465 - Clear text from ALL shapes identified in the inventory
466 - Apply new text only to shapes with "paragraphs" defined in the replacement JSON
467 - Preserve formatting by applying paragraph properties from the JSON
468 - Handle bullets, alignment, font properties, and colors automatically
469 - Save the updated presentation
470
471 Example validation errors:
472 ```
473 ERROR: Invalid shapes in replacement JSON:
474 - Shape 'shape-99' not found on 'slide-0'. Available shapes: shape-0, shape-1, shape-4
475 - Slide 'slide-999' not found in inventory
476 ```
477
478 ```
479 ERROR: Replacement text made overflow worse in these shapes:
480 - slide-0/shape-2: overflow worsened by 1.25" (was 0.00", now 1.25")
481 ```
482
483## Creating Thumbnail Grids
484
485To create visual thumbnail grids of PowerPoint slides for quick analysis and reference:
486
487```bash
488python scripts/thumbnail.py template.pptx [output_prefix]
489```
490
491**Features**:
492- Creates: `thumbnails.jpg` (or `thumbnails-1.jpg`, `thumbnails-2.jpg`, etc. for large decks)
493- Default: 5 columns, max 30 slides per grid (5×6)
494- Custom prefix: `python scripts/thumbnail.py template.pptx my-grid`
495 - Note: The output prefix should include the path if you want output in a specific directory (e.g., `workspace/my-grid`)
496- Adjust columns: `--cols 4` (range: 3-6, affects slides per grid)
497- Grid limits: 3 cols = 12 slides/grid, 4 cols = 20, 5 cols = 30, 6 cols = 42
498- Slides are zero-indexed (Slide 0, Slide 1, etc.)
499
500**Use cases**:
501- Template analysis: Quickly understand slide layouts and design patterns
502- Content review: Visual overview of entire presentation
503- Navigation reference: Find specific slides by their visual appearance
504- Quality check: Verify all slides are properly formatted
505
506**Examples**:
507```bash
508# Basic usage
509python scripts/thumbnail.py presentation.pptx
510
511# Combine options: custom name, columns
512python scripts/thumbnail.py template.pptx analysis --cols 4
513```
514
515## Converting Slides to Images
516
517To visually analyze PowerPoint slides, convert them to images using a two-step process:
518
5191. **Convert PPTX to PDF**:
520 ```bash
521 soffice --headless --convert-to pdf template.pptx
522 ```
523
5242. **Convert PDF pages to JPEG images**:
525 ```bash
526 pdftoppm -jpeg -r 150 template.pdf slide
527 ```
528 This creates files like `slide-1.jpg`, `slide-2.jpg`, etc.
529
530Options:
531- `-r 150`: Sets resolution to 150 DPI (adjust for quality/size balance)
532- `-jpeg`: Output JPEG format (use `-png` for PNG if preferred)
533- `-f N`: First page to convert (e.g., `-f 2` starts from page 2)
534- `-l N`: Last page to convert (e.g., `-l 5` stops at page 5)
535- `slide`: Prefix for output files
536
537Example for specific range:
538```bash
539pdftoppm -jpeg -r 150 -f 2 -l 5 template.pdf slide # Converts only pages 2-5
540```
541
542## Code Style Guidelines
543**IMPORTANT**: When generating code for PPTX operations:
544- Write concise code
545- Avoid verbose variable names and redundant operations
546- Avoid unnecessary print statements
547
548## Examples
549
550**Example 1: Create a presentation from scratch**
551```
552User: "Make a pitch deck for my startup idea"
553→ Reads html2pptx.md for syntax
554→ Creates HTML slides with proper styling and layout
555→ Converts to PowerPoint, validates with thumbnails
556```
557
558**Example 2: Use a template**
559```
560User: "Create slides using this company template"
561→ Extracts template inventory with thumbnail grid
562→ Maps content to appropriate slide layouts
563→ Replaces placeholder text, preserves formatting
564```
565
566**Example 3: Add speaker notes to existing deck**
567```
568User: "Add speaker notes to my presentation"
569→ Unpacks PPTX, navigates to notesSlide XML files
570→ Adds notes content to each slide
571→ Repacks and validates the presentation
572```
573
574## Dependencies
575
576Required dependencies (should already be installed):
577
578- **markitdown**: `pip install "markitdown[pptx]"` (for text extraction from presentations)
579- **pptxgenjs**: `npm install -g pptxgenjs` (for creating presentations via html2pptx)
580- **playwright**: `npm install -g playwright` (for HTML rendering in html2pptx)
581- **react-icons**: `npm install -g react-icons react react-dom` (for icons)
582- **sharp**: `npm install -g sharp` (for SVG rasterization and image processing)
583- **LibreOffice**: `sudo apt-get install libreoffice` (for PDF conversion)
584- **Poppler**: `sudo apt-get install poppler-utils` (for pdftoppm to convert PDF to images)
585- **defusedxml**: `pip install defusedxml` (for secure XML parsing)