powerpoint-toolkit
Skill8 starsChanged 9 months agoMITView on GitHub
Build, edit, analyze, and improve PowerPoint presentations (.pptx). Use when a user asks to: (1) Create a new presentation from scratch, (2) Edit or modify slides, text, images, or layouts, (3) Analyze a presentation for quality, consistency, or content, (4) Improve an existing presentation's design, structure, or readability, (5) Extract text or speaker notes, (6) Add charts, tables, or media to slides, (7) Review or critique a presentation.
In this repository6 other files it gives its agents.
- agent-councilSkill
- brainstormingSkill
- building-frontend-componentsSkill
- excel-toolkitSkill
- writing-plansSkill
- writing-skillsSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 62
Before writing code, always:
- Distinctive: line 69
Use web-safe fonts only: Arial, Verdana, Georgia, Tahoma, Trebuchet MS, Times New Roman, Courier New
- Distinctive: line 70
Create clear visual hierarchy through size, weight, and color
- Distinctive: line 71
Keep text concise — aim for ≤6 bullet points, ≤6 words per bullet
- Distinctive: line 72
Ensure strong contrast between text and backgrounds
- Distinctive: line 73
Use consistent spacing and alignment across all slides
- Distinctive: line 74
Add speaker notes for presentation delivery
- Distinctive: line 128
When asked to review or improve a presentation:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PowerPoint Toolkit
Setup (First Use)
python3 scripts/setup_deps.pyInstalls: python-pptx, Pillow, pyyaml. Skip if already installed.
Workflow Decision Tree
- Inspect structure → Run
scripts/inspect_pptx.py - Extract text → Run
scripts/extract_text.py - Analyze & get improvement suggestions → Run
scripts/analyze_pptx.py - Generate visual thumbnails → Run
scripts/thumbnails.py - Create new presentation → Use python-pptx (see
references/design-and-creation.md) - Edit existing presentation → Use python-pptx or OOXML (see
references/ooxml-editing.md)
Quick-Start Scripts
Inspect File Structure
python3 scripts/inspect_pptx.py deck.pptx # Overview
python3 scripts/inspect_pptx.py deck.pptx --text # With all text
python3 scripts/inspect_pptx.py deck.pptx --notes # With speaker notes
python3 scripts/inspect_pptx.py deck.pptx --layouts # With layout details
python3 scripts/inspect_pptx.py deck.pptx --slide 0 # Single slide
python3 scripts/inspect_pptx.py deck.pptx --text --notes # Full contentReturns JSON: slide count, dimensions, shapes, text, images, charts, tables, notes.
Extract Text
python3 scripts/extract_text.py deck.pptx # Markdown format
python3 scripts/extract_text.py deck.pptx --format json # Structured JSON
python3 scripts/extract_text.py deck.pptx --format text # Plain text
python3 scripts/extract_text.py deck.pptx --notes # Include speaker notesAnalyze & Improve
python3 scripts/analyze_pptx.py deck.pptx # Full analysis
python3 scripts/analyze_pptx.py deck.pptx --verbose # Extra detailReturns JSON with stats (fonts, sizes, layouts, text density) and issues (readability, consistency, missing notes, visual balance).
Generate Thumbnails
python3 scripts/thumbnails.py deck.pptx # Default 4-col grid
python3 scripts/thumbnails.py deck.pptx preview --cols 3 # Custom layoutRequires LibreOffice + poppler (pdftoppm). Creates a JPEG grid for visual review.
Creating Presentations
Design Principles
Before writing code, always:
- Analyze content — What topic, tone, audience?
- Choose palette — See
references/design-and-creation.mdfor 10 curated palettes - Plan layout — Decide slide types: title, content, section, closing
- State approach — Explain design choices before implementation
Key Rules
- Use web-safe fonts only: Arial, Verdana, Georgia, Tahoma, Trebuchet MS, Times New Roman, Courier New
- Create clear visual hierarchy through size, weight, and color
- Keep text concise — aim for ≤6 bullet points, ≤6 words per bullet
- Ensure strong contrast between text and backgrounds
- Use consistent spacing and alignment across all slides
- Add speaker notes for presentation delivery
Quick Creation Template
from pptx import Presentation
from pptx.util import Inches, Pt
from pptx.dml.color import RGBColor
prs = Presentation()
prs.slide_width = Inches(13.333)
prs.slide_height = Inches(7.5)
# Title slide
slide = prs.slides.add_slide(prs.slide_layouts[0])
slide.shapes.title.text = "Title"
slide.placeholders[1].text = "Subtitle"
# Content slide
slide = prs.slides.add_slide(prs.slide_layouts[1])
slide.shapes.title.text = "Section"
body = slide.placeholders[1].text_frame
body.text = "First point"
p = body.add_paragraph()
p.text = "Second point"
p.level = 0
prs.save("output.pptx")For full creation reference (shapes, formatting, charts, tables, images, notes) → see references/design-and-creation.md.
Editing Presentations
Simple Edits (python-pptx)
from pptx import Presentation
prs = Presentation("existing.pptx")
slide = prs.slides[0]
for shape in slide.shapes:
if shape.has_text_frame:
for para in shape.text_frame.paragraphs:
for run in para.runs:
run.text = run.text.replace("old", "new")
prs.save("modified.pptx")Advanced Edits (OOXML)
For operations beyond python-pptx (animations, complex formatting, raw XML manipulation) → see references/ooxml-editing.md.
Providing Improvement Feedback
When asked to review or improve a presentation:
- Run
scripts/inspect_pptx.py deck.pptx --text --notes - Run
scripts/analyze_pptx.py deck.pptx - Optionally generate thumbnails for visual review
- Present findings in this order:
- Overview: slide count, layout types, visual balance
- Content Issues: text density, empty slides, missing titles
- Design Issues: font consistency, size readability, color contrast
- Structure Issues: flow, pacing, section organization
- Suggestions: specific actionable improvements with slide references
Common Slide Patterns
| Pattern | Layout | When to Use |
| Title Slide | Layout 0 | Opening, section dividers |
| Bullets | Layout 1 | Key points, agenda |
| Two-Column | Layout 3 | Comparison, before/after |
| Image + Text | Layout 5 + textbox | Visual storytelling |
| Chart Slide | Layout 5 + chart | Data presentation |
| Table Slide | Layout 5 + table | Structured data |
| Quote Slide | Layout 6 + textbox | Attribution, emphasis |
| Closing | Layout 0 or 6 | Thank you, contact info |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

