pptx-visual-assets
Use when selecting and placing approved supporting icons, images, SVGs, diagrams, or infographics in an editable PPTX deck.
Profile →npx skills add wshobson/agents --skill pptx-visual-assets --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PPTX Visual Assets Use visual assets to support a slide's message, never to flatten or replace editable content. ## Workflow 1. Select the asset type only when it improves comprehension: icon, image, SVG, diagram, or infographic. 2. Confirm the local asset path, source, usage rights, and concise alt text before placement. 3. Add the asset with a final inch bbox, deliberate z-index, and `content` or `layout_design` classification. 4. 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.
- Workflow
- Rules
What does the pptx-visual-assets skill do?
Use when selecting and placing approved supporting icons, images, SVGs, diagrams, or infographics in an editable PPTX deck.
How do I install it?
Run `npx skills add wshobson/agents --skill pptx-visual-assets --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From wshobson/agents, a repository with 38,479 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.