Build and edit PowerPoint slides with AI

Deckary's PowerPoint AI agent can create one native slide at a time, patch an existing slide, or replace a slide when a full redesign is needed. The agent chooses the content and layout; the add-in validates the complete slide plan, commits it to PowerPoint, reads it back, and reviews the rendered result.

Create a new slide#

Describe the decision the slide should support, the intended audience, and the evidence to use. If the presentation already has a suitable layout, Deckary can use its native placeholders and theme. A concrete prompt produces a more useful first draft than a request such as “make a good slide.”

Add a market-entry recommendation after the current slide. Use the attached
research, lead with the recommendation, compare the three options, and cite
the sources in a compact footer.

New slides can contain text, shapes, connectors, tables, media, and supported native charts. Deckary uses one complete slide-authoring transaction so invalid content or geometry can be rejected before any part of the slide is written.

Edit an existing slide#

For a targeted revision, identify the slide and the outcome rather than describing mouse actions. Deckary first reads the current slide, then uses current object handles to update, add, or remove the required elements.

Examples:

• “Shorten the title and make the recommendation explicit.”
• “Update this chart from the latest values and keep its position.”
• “Replace the right-hand text with three evidence-backed implications.”
• “Fix the overlap without changing the slide's content.”

If PowerPoint changes after the agent reads it, Deckary requires fresh state before applying the write. That prevents an edit planned for one version from landing on another.

Build several slides#

For a multi-slide request, Deckary authors slides sequentially. Each slide is committed and reviewed before work moves to the next slide. The agent can reuse the same approved sources across the run while still reading the current presentation state between changes.

This sequence matters because PowerPoint assigns live slide and shape identities during a commit. The next step works from those actual identities rather than assumptions made before the file changed.

Use sources and citations#

Attached documents and current-run web research form the source authority for factual claims. A web citation must match a source observed during the active run; the authoring layer will not accept an invented URL. Source references can be rendered as a footer when the slide needs visible attribution.

What the agent verifies#

After a successful write, Deckary reads the committed slide state and uses PowerPoint's renderer to inspect the output. Structural checks cover the objects that were created or changed. Visual review checks the actual slide pixels for issues such as clipping, overlap, poor hierarchy, or unreadable density.

The result remains a PowerPoint slide. You can continue editing it manually after the agent finishes.

See Native PowerPoint charts for chart behavior or MCP documentation if the reasoning agent should run in an external MCP client.