
Pptx Official
Install this when you need an agent to create, edit, or deeply analyze PowerPoint files including notes, layouts, and OOXML—not just skim slide text.
Overview
PPTX Official is an agent skill most often used in Build (also Validate landing, Launch distribution) that creates, edits, and analyzes .pptx files via markitdown and OOXML unpack workflows.
Install
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill pptx-officialWhat is this skill?
- Markdown text extraction via `python -m markitdown path-to-file.pptx` for fast content reads
- OOXML unpack workflow with `python ooxml/scripts/unpack.py` for notes, animations, and layout XML
- Maps key paths: `ppt/presentation.xml` and related PPTX ZIP structure
- Branches workflows: light reading versus raw XML for comments, speaker notes, and design elements
- Two workflow branches: markitdown text extract vs OOXML unpack for advanced features
Adoption & trust: 569 installs on skills.sh; 40.1k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need slide changes or forensics on a .pptx but the agent only guesses at file APIs and misses notes, layouts, and embedded XML structure.
Who is it for?
Solo founders maintaining pitch decks, launch slides, or workshop materials who want agents to follow real PPTX mechanics.
Skip if: Teams that only need Google Slides in the browser with no local .pptx pipeline, or purely visual design with no document structure changes.
When should I use this skill?
A user asks you to create, edit, or analyze the contents of a .pptx file
What do I get? / Deliverables
You get a chosen workflow—markdown extraction or unpacked XML editing—for accurate PowerPoint create/edit/analyze passes.
- Edited or new .pptx archive
- Markdown extraction of slide text
- Unpacked XML tree for advanced edits
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
First shelf is Build/docs because pitch decks, handoff decks, and product slides are authoring artifacts, though the same skill supports launch and validate storytelling. Docs subphase fits structured document deliverables (.pptx) that accompany specs, launches, and investor updates.
Where it fits
Agent drafts a product walkthrough deck and patches slide XML after unpack.
You extract markdown from an existing pitch deck to align landing page copy with slides.
Final launch deck gets speaker notes and layout fixes via raw XML access.
Webinar slide set is updated from customer FAQ markdown without manual click-editing every box.
How it compares
Document-structure skill with Python tooling, not a slide-design template pack or a cloud-only presentation SaaS integration.
Common Questions / FAQ
Who is pptx-official for?
Indie builders and consultants who ship .pptx files and want coding agents to read and modify them with markitdown or OOXML unpack steps.
When should I use pptx-official?
During Build/docs for deck authoring, Validate when refining pitch or scope slides, and Launch when preparing distribution-ready presentations.
Is pptx-official safe to install?
Community-sourced with unknown risk flag in metadata; review the Security Audits panel on this page and sandbox shell access to user files.
SKILL.md
READMESKILL.md - Pptx Official
# PPTX creation, editing, and analysis ## 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: ```bash # 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: 1. **Read theme file**: Check `ppt/theme/theme1.xml` for colors (`<a:clrScheme>`) and fonts (`<a:fontScheme>`) 2. **Sample slide content**: Examine `ppt/slides/slide1.xml` for actual font usage (`<a:rPr>`) and colors 3. **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: 1. **Consider the subject matter**: What is this presentation about? What tone, industry, or mood does it suggest? 2. **Check for branding**: If the user mentions a company/organization, consider their brand colors and identity 3. **Match palette to content**: Select colors that reflect the subject 4. **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 ha