Slides
Gio's personal agent skills for coding agents — small, composable, installable via npx skills@latest add gio-del/skills
npx -y skills add gio-del/skills --skill slidesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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
Generate or extend a reveal.js slide deck from a description of what to show, rendered against a design system bootstrapped by /design-system. Manual invocation only.
SKILL.md
1.8 KB, 373 tokens by cl100k_base, as published. Nobody here has run it
Slides
Turn a description of a talk into a reveal.js deck, rendered against one of the repo's design systems.
1. Pick a design system
If a design system name was passed as an argument, use it. Otherwise, glob design-systems/*/brand-guidelines.md:
- None found: tell the user to run
/design-systemfirst. - Exactly one: warn the user only one design system exists (name it) and confirm before proceeding.
- Multiple: read each
brand-guidelines.md'sdescription:frontmatter and offer a picker showing name + description.
2. Get the description of what to show
Accept whatever the user hands over: inline text, or a path to a file. If it's too thin to imply a rough structure (slide count, throughline), ask one clarifying question before generating — don't silently guess, but don't run a full /grilling interview either.
3. Pick a deck name
If a deck with this name already exists under slides/<deck-name>/, this is an edit — extend/modify its existing slides rather than regenerating the deck from scratch (see docs/adr/0004-slides-edits-in-place.md). Otherwise this is a new deck.
4. Generate or edit the deck
Write slides/<deck-name>/ as a small local reveal.js project (index.html + assets), referencing the chosen design system's theme.css and layouts/ by relative path rather than copying them. Compose slides out of the design system's named layouts — don't invent one-off slide markup that bypasses them.
Out of scope
Bootstrapping a design system — that's /design-system, which this skill only consumes.
Gives 0 of the 12 instructions most slides presentations skills give in 373 tokens
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
- use the passed design system name
- glob for available design systems if none is passed
- tell the user to run design-system if none are found
- confirm before proceeding if only one design system exists
- offer a picker if multiple design systems exist
- accept inline text or a file path as input
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.