How to use the PPTX Visual Assets agent skill

What is an agent skill, and what does this one make the agent do?

An agent skill is a folder containing a SKILL.md file of instructions that an AI agent reads when a task matches the skill's description. This skill's description is: use when selecting and placing approved supporting icons, images, SVGs, diagrams, or infographics in an editable PPTX deck.

Once active, the agent is told to use a visual only when it improves comprehension, to confirm the local asset path, source, usage rights and concise alt text before placing it, and to keep the asset's bounding box, stacking order and aspect ratio under control.

• Choose an asset type only when it helps the slide: icon, image, SVG, diagram or infographic.
• Check the local file path, source, usage rights and alt text before placement.
• Keep essential text, labels, legends, values and process steps as native PowerPoint objects, not inside pictures.
• Leave the visual out and report the gap if rights, provenance or a suitable asset are missing.

Install the PPTX Visual Assets skill

Download the ZIP for this skill from this page. Then install it in one of two ways. For a personal setup, unzip it into ~/.claude/skills/. For a single project, unzip it into that project's .claude/skills/ folder. In the Claude apps you can instead upload the skill under Settings → Capabilities → Skills.

The skill's files are SKILL.md and references/asset-guidance.md. Keep the references folder alongside SKILL.md, because the main file points the agent to it for licensing, placement and SVG rules.

Set up what the skill needs

The skill does not build decks by itself. It needs a PPTX-generating environment or library that the agent uses to create the file; the source does not name a specific one, so you must provide it. It also needs local asset files and a source manifest where provenance records are kept.

The skill's instructions say to record provider or source details in that manifest. Before placing an external asset, the reference file asks for its local path, source URL or provider, usage rights and concise alt text.

• A PPTX-generating environment the agent can call.
• Local asset files that you already have approved for use.
• A source manifest to hold path, source, rights and alt text for each asset.

How to trigger the skill with natural requests

You do not need special syntax. Describe the deck and the visual need in plain words, and mention that the assets are local and approved. The agent will match the request to the skill's description when it fits.

Good requests name the deck, the slide purpose and the files. For example, you might ask the agent to add a simple icon with a text label to each feature slide, using only the approved icons in your assets folder and recording each source in the manifest.

• Add a labelled icon beside each of the three benefits on slide 4, using files in assets/icons.
• Put the architecture diagram on slide 7 as an editable object and keep all box labels as text.
• Place the approved photo on the title slide, cropped to fill, with its caption beside it rather than over it.

Safety notes: scripts and network access

This skill runs no scripts and uses no network access, according to its listing. It works with asset files you supply and does not, by its own instructions, request secrets in chat.

The skill does not find or download stock images from the web. It places only assets you already have approved.

• Runs scripts: no.
• Uses network: no.
• Never paste API keys or passwords into the chat as part of asset handling.

Tips for cleaner, editable slides

The skill's rules are practical. Use SVG only when the source is a clean vector; a raster image wrapped in SVG is not editable. Keep captions beside images, and keep any visual below overlapping readable text in stacking order.

If an asset leaves no room on the slide, the guidance says to omit it and repair the layout rather than squeeze it in.

• Use simple, legible icons next to text labels.
• Recreate charts' values and process steps as native objects so they can be edited.
• Review each asset's rights in the manifest before you publish the deck.