Powerpoint / PPTX

• Building or editing a .pptx file — the primary artifact is a PowerPoint presentation and layout, template, or visual quality matters.
• Template-driven work — you need to reuse an existing deck's masters, layouts, and placeholders while replacing content accurately.
• Content extraction or inspection — you need to read slide text, notes, comments, chart data, or media inventory from an existing deck before making changes.
• Visual QA before delivery — you need to verify that text doesn't overflow, shapes aren't clipped, contrast is sufficient, and placeholder junk hasn't survived the edit.

• PDF or image-only output is sufficient — if the final artifact doesn't need to be an editable .pptx file, a simpler document or export skill may be more appropriate.
• Plain document or report creation — if the content is narrative prose without slide structure, a word-processing or document skill is a better fit.

Before any content replacement, the skill counts real placeholders, layout indexes, notes, comments, and media across the deck. This prevents silent misplacement caused by assuming placeholder or layout indexes are portable across templates.

Content is matched to the actual placeholders a layout exposes — not assumed. The skill enforces counting content pieces before choosing a layout, so you avoid empty placeholders, forced columns, and broken chart series.

Edits respect the deck's existing theme, master, fonts, spacing, and aspect ratio. The skill explicitly discourages improvising a second visual language, ensuring combined or edited slides stay consistent with the source deck.

Content QA (missing text, broken notes, leftover placeholder labels) and visual QA (overflow, clipping, contrast, alignment) are run as separate passes. The skill treats the first render as likely wrong and requires at least one fix-and-verify cycle.

Flags risks from complex effects, font substitution, master overrides, and linked media that look fine in code but break on screen or across PowerPoint, LibreOffice, and conversion pipelines.

An agent inventories an existing branded .pptx template, maps its real layouts and placeholder indexes, then populates it with new content — preserving fonts, colors, and visual hierarchy without drifting from the brand system.

An agent reads all slide text, speaker notes, comments, chart data, and media references from a deck before any edits are made, producing a reliable inventory for human review or downstream content workflows.

An agent updates slide content, then runs both content and visual QA passes — checking for overflow, clipped shapes, leftover sample text, and broken chart categories — before delivering the final deck.

An agent combines slides from different source decks, then normalizes masters, themes, and alignment to eliminate the subtle per-slide inconsistency that results from incompatible templates.