Utility slideshow creator
Skill product-on-purpose/pm-skills/skills/utility-slideshow-creator
Generates professional presentations from a JSON deck specification using 18 slide types with dark/light variants, content-to-layout decision logic, and calibrated character limits. Ships with a default professional theme.From its SKILL.md
npx -y skills add product-on-purpose/pm-skills --skill utility-slideshow-creatorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
6.4 KB, ~1.5k tokens by cl100k_base, as published. Nobody here has run it
Slideshow Creator
Generate professional presentations (.pptx and .pdf) from a JSON deck specification. Zero design decisions at generation time - Claude selects slide types and fills content slots; all visual properties are pre-decided by the theme.
When to Use
- Creating slide decks for stakeholder updates, product reviews, team presentations
- Generating professional .pptx files from content briefs
- Producing consistent presentations without manual formatting
- Exporting presentations to PDF for sharing or archiving
When NOT to Use
- Creating complex data visualizations (use dedicated charting tools)
- Building interactive web presentations (this produces .pptx, not HTML)
- Editing existing PowerPoint files (this creates new decks from scratch)
How It Works
Two-phase architecture:
- Spec phase (Claude) - Read the content brief, select slide types using decision logic, write a JSON deck specification. Content slots have character limits calibrated to prevent overflow. This is the only phase that costs tokens.
- Generation phase (Local script) - Run
node scripts/generate-deck.js deck-spec.jsonto produce .pptx. Optionally runnode scripts/export-pdf.mjs deck-spec.jsonfor PDF. Deterministic rendering, zero token cost.
Both outputs come from the same JSON spec, so .pptx and .pdf always match.
18 Slide Types
| # | Type Key | Purpose | Default Variant |
|---|---|---|---|
| 1 | title_dark | Opening slide (bold) | dark only |
| 2 | title_light | Opening slide (internal/lighter) | light only |
| 3 | section | Section divider | dark |
| 4 | content | Paragraph explanation | light |
| 5 | bullets | 3-6 key points | light |
| 6 | two_col | Side-by-side comparison | light |
| 7 | stat | Single key metric | light |
| 8 | dual_stat | Two metrics compared | dark |
| 9 | quote | Testimonial or pull quote | dark |
| 10 | three_card | Three parallel concepts | dark |
| 11 | four_grid | Four concepts in 2x2 grid | dark |
| 12 | timeline | Dates or milestones (max 6) | light |
| 13 | process_flow | Sequential workflow (max 5) | light |
| 14 | agenda | Meeting agenda (max 7) | light |
| 15 | highlight | Key finding or executive summary | light |
| 16 | table | Tabular data | light |
| 17 | icon_rows | Feature list with markers (max 4) | light |
| 18 | closing | End slide | dark only |
Full slot definitions and character limits: references/slide-types.md
Decision Logic (Quick Reference)
| Content Pattern | Use |
|---|---|
| Opening the deck (bold) | title_dark |
| Opening the deck (internal) | title_light |
| Transitioning between topics | section |
| Paragraph explanation | content |
| List of 3-6 points | bullets |
| Side-by-side comparison | two_col |
| Single key metric | stat |
| Two metrics compared | dual_stat |
| Testimonial or pull quote | quote |
| Three parallel concepts | three_card |
| Four concepts in a grid | four_grid |
| Dates or milestones | timeline |
| Sequential workflow | process_flow |
| Meeting agenda | agenda |
| Key finding or summary | highlight |
| Tabular data | table |
| Feature list with markers | icon_rows |
| Ending the deck | closing |
Full decision logic with variant strategy: references/decision-logic.md
JSON Deck Spec Format
{
"title": "Q3 Product Update",
"author": "Product Team",
"footerText": "Internal . Q3 Review",
"slides": [
{ "type": "title_dark", "title": "Q3 Product Update", "subtitle": "October 2026" },
{ "type": "stat", "stat": "94%", "label": "Customer satisfaction score", "accentColor": "secondary" },
{ "type": "bullets", "title": "What Shipped", "bullets": ["Feature A", "Feature B", "Feature C"] },
{ "type": "closing" }
]
}
Colors accept theme token names ("accent", "secondary", "tertiary", "warm") or 6-character hex strings ("2563EB").
Full schema and workflow: references/TEMPLATE.md and references/platform-rules.md
Instructions
- Read the content brief - Understand topic, audience, length, specific requirements
- Plan the deck - Select slide types using the decision logic table. Assign dark/light variants for visual rhythm (alternate to avoid monotony).
- Write the JSON deck specification - Fill content slots, respecting character limits from
references/slide-types.md - Run the generation script -
node scripts/generate-deck.js deck-spec.json - Optionally export PDF -
node scripts/export-pdf.mjs deck-spec.json output.pdf - Report the output - Tell the user where the file(s) are
Output Contract
- Planning artifact: JSON deck specification (the file Claude writes)
- Final output: .pptx file (+ optional .pdf), generated locally from the spec
- Quality gate: All items in the quality checklist pass
Quality Checklist
- Every slide has a valid type key (one of the 18 defined types)
- All content slots respect character limits from
references/slide-types.md - Dark/light variants alternate for visual rhythm (no 3+ consecutive same-variant slides)
- Deck has a title slide (first) and a closing slide (last)
- Section dividers separate distinct topics in decks > 6 slides
- Speaker notes included for key slides (stats, highlights, transitions)
- JSON is valid (no trailing commas, proper quoting, correct nesting)
- Color values are valid theme tokens or 6-character hex strings (no
#prefix)
References
| File | Purpose |
|---|---|
references/TEMPLATE.md | JSON deck specification template with field documentation |
references/EXAMPLE.md | Worked example: Q3 Product Update deck (9 slides) |
references/slide-types.md | All 18 slide types: content slots, character limits, variants |
references/decision-logic.md | Content pattern → slide type mapping, variant strategy, deck sizing |
references/platform-rules.md | pptxgenjs requirements, Google Slides compatibility, output format |
What ships with it: 6 files
23.7 KB alongside SKILL.md
references/
- decision-logic.md3.4 KB
- EXAMPLE.md6.4 KB
- platform-rules.md2.9 KB
- slide-types.md7.8 KB
- TEMPLATE.md2.5 KB
- HISTORY.md796 B
Gives 0 of the 12 instructions most slides presentations skills give in ~1.5k tokens
Counted across 547 of the 547 authors here whose files we hold, read 2026-09-06
- Ensure every slide fits inside one viewportin 31 of 547, across 18 files
- Keep one idea per slidein 27 of 547, across 24 files
- Default to one self-contained HTML filein 24 of 547, across 16 files
- Check for product marketing context firstin 21 of 547, across 7 files
- Read STYLE_PRESETS.md before generatingin 21 of 547, across 12 files
- Involve reps in creationin 20 of 547, across 6 files
- Tailor to persona and deal stagein 20 of 547, across 6 files
- Generate three single-slide preview filesin 17 of 547, across 11 files
- Delete temporary preview files at handoffin 16 of 547, across 8 files
- Support keyboard and touch navigationin 16 of 547, across 7 files
- Keep one-pagers to a single pagein 15 of 547, across 5 files
- Use bold headers and short bulletsin 14 of 547, across 4 files
Said here and by no other author read
- Read the content brief
- Plan the deck
- Optionally export PDF
- Report the output
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.