mcpbeat

Pptx Visual Assets

wshobson/pptx-visual-assets

Use when selecting and placing approved supporting icons, images, SVGs, diagrams, or infographics in an editable PPTX deck.

593 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
38452
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/wshobson/agents --skill pptx-visual-assets

The instruction itself

3 sections, as written by the author

PPTX Visual Assets

Use visual assets to support a slide's message, never to flatten or replace editable content.

Workflow

  • Select the asset type only when it improves comprehension: icon, image, SVG, diagram, or infographic.
  • Confirm the local asset path, source, usage rights, and concise alt text before placement.
  • Add the asset with a final inch bbox, deliberate z-index, and content or layout_design classification.
  • Preserve aspect ratio and check that no asset covers readable text or leaves essential information locked in an image.

Rules

  • Use simple, legible icons alongside text labels.
  • Place captions beside images rather than over them.
  • Use true SVG sources only when they are clean vectors; never wrap a raster image in SVG and call it editable.
  • Recreate essential labels, legends, values, and process steps with native PowerPoint objects.
  • If rights, provenance, or a suitable asset are unavailable, omit the asset and report the gap. Never add a placeholder as a finished visual.
  • Record provider or source details in the source manifest. Never request secrets in chat.

See references/asset-guidance.md for licensing, placement, and SVG constraints.

How to use it

Copy the folder

Take wshobson/pptx-visual-assets from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.