agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/amplifier-bundle-work/skills/presentations/SKILL.md

presentations

Skill0 starsChanged 27 days agoMITView on GitHub

Create or edit editable PowerPoint PPTX slides and Google Slides-bound decks. Use for presentations, slide layouts, speaker notes, and template-based decks.

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ${SKILL_DIR}/../_shared/artifacts.md.

    line 10
  2. Distinctive:

    Do not rebuild a complex deck through a library that cannot preserve its animations, media, SmartArt, or chart behavior.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Presentations

Read ${SKILL_DIR}/../_shared/artifacts.md. Use python-pptx for portable PPTX authoring. It is a different engine from OpenAI's private artifact-tool runtime; do not execute that runtime's examples as if the APIs were interchangeable.

  1. Define the audience, decision, story, slide count, and source material. Write an outline with one main claim per slide, supported by actual evidence.
  2. Inspect any existing deck's slide size, masters, layouts, fonts, objects, notes, charts, and embedded resources. Work on a copy. Retain native editable text, shapes, tables, and charts rather than rasterizing entire slides.
  3. Build a consistent grid, title hierarchy, restrained palette, and readable type scale. Keep all objects within the slide. Prefer charts and diagrams when they explain a comparison or relationship; label axes and cite data.
  4. For edits, change the requested objects while preserving unrelated content. Inspect effective typography at both paragraph-default and run levels; a run's unset font properties can inherit the reference's font, size, and color from its paragraph or theme. Prefer replacing text within existing runs. Assigning shape.text or clearing a text frame can discard paragraph defaults and silently flatten the hierarchy. If rebuilding is necessary, retain and restore paragraph properties (a:pPr) and run properties (a:rPr), including alignment, spacing, bullets, and color, then compare effective fonts against the reference after saving. Do not treat an unset run font as unformatted text. Do not rebuild a complex deck through a library that cannot preserve its animations, media, SmartArt, or chart behavior; use a capable native adapter or report the specific limitation before destructive conversion.
  5. Reopen the PPTX to verify slide count, text, notes, chart data, typography, and object bounds. Render every slide, inspect full-size images, fix overlap and clipping, and render affected slides again. XML bounds alone do not catch text overflow.
  6. Return the PPTX, plus a PDF only when requested. A Google Slides request needs a verified connector import; a local deck alone does not complete that step.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.

Check your setup, free