Slide deck builder

Skill yigityildiz0/universal-ai-skill-library/skills/common/slide-deck-builder

531 searchable AI Agent Skills for Claude Code, OpenAI Codex, and OpenCode — EN/TR catalog, platform and risk notes, direct ZIPs, and curated bundles.

Install

npx -y skills add yigityildiz0/universal-ai-skill-library --skill slide-deck-builder

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

18 days oldThe repository was created 18 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Presentation-structure skill. Use when Codex should turn notes, ideas, or documents into a coherent deck with slide-by-slide flow.

SKILL.md

0.6 KB, as published. Nobody here has run it

Slide Deck Builder

Use this skill when the user has a topic but not a usable presentation structure yet.

Workflow

Define audience and deck objective first.
Build the narrative arc before deciding slide count.
Keep one clear point per slide.

Deliverables

A slide-by-slide outline.
Optional speaker-note guidance.

Guardrails

Do not paste paragraphs onto slides.
Do not let style outrun the argument.

Gives 0 of the 12 instructions most slides presentations skills give

Counted across 568 of the 571 authors here whose files we hold, read 2026-08-06

include a visual element on every slidein 52 of 568, across 21 files
put one idea per slidein 50 of 568, across 42 files
state the design approach before writing codein 38 of 568, across 8 files
validate XML immediately after each editin 37 of 568, across 7 files
rasterize gradients and icons as PNG images before referencing themin 37 of 568, across 7 files
generate and inspect thumbnails to validate layoutin 37 of 568, across 7 files
commit to a single visual motif across every slidein 37 of 568, across 12 files
use web-safe fonts onlyin 36 of 568, across 7 files
keep 0.5 inch minimum marginsin 35 of 568, across 9 files
use two-column layout for slides with charts or tablesin 34 of 568, across 5 files
save a template inventory analysis to a filein 33 of 568, across 4 files
use subagents to visually inspect rendered slidesin 33 of 568, across 9 files

Said here and by no other author read

Define audience and deck objective first
Provide optional speaker-note guidance

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.