mcpbeat Sign in

Utility Slideshow Creator Skill for Claude

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.

8k tokens
context cost
the whole folder, loaded on every use
7
files
instructions only
0
copies elsewhere
how many repositories repackaged it
516
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/product-on-purpose/pm-skills --skill utility-slideshow-creator

The instruction itself

11 sections, as written by the author

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

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.json to produce .pptx. Optionally run node scripts/export-pdf.mjs deck-spec.json for 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 |

Other skills for the same job

different authors, same section of the catalogue
Mobile Design
by ComeOnOliver
×2

Mobile-first design and engineering doctrine for iOS and Android apps. Covers touch interaction, performance, platform conventions, offline behavior, and mobile-specific decision-making. Teaches principles and constraints, not fixed layouts. Use for React Native, Flutter, or native mobile apps.

72k tokens scripts
Experimental Design
by K-Dense-AI
×1

Design experiments and studies BEFORE data is collected — choosing a design, randomizing, blocking, and laying out treatment combinations so results are interpretable. Use whenever someone is planning a study, asks how to assign subjects/samples to groups, mentions randomization, blocking, stratification, controls, factorial or fractional-factorial designs, design of experiments (DOE), screening many factors, response-surface optimization, crossover or repeated-measures or split-plot designs, cluster/group randomization, Latin squares, plate layouts, batch/run-order effects, replication vs. pseudoreplication, or sequential/adaptive/group-sequential designs. Trigger even for informal phrasings like "how should I set up this experiment", "how do I avoid confounding", "what's the best way to test these 6 factors", or "assign these mice to conditions". For computing the sample size or power once the design is chosen, use statistical-power; for analyzing data already collected, use statistical-analysis.

14k tokens scripts
Architect
by ComeOnOliver
×1

Design systems, plan implementations, review architecture decisions - Use when you need to plan a complex feature, design system architecture, or make high-level technical decisions.

2k tokens
Analyze Feature Requests
by phuryn

Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.

568 tokens
Gke Networking
by google
vendor

>- Plans, configures, and manages core GKE cluster networking. Covers private clusters, VPC-native configurations, DNS, node egress, Dataplane V2, and IP planning. Use when designing GKE networking layouts, configuring private clusters, setting up Dataplane V2, planning GKE IP ranges, or managing VPC- native cluster modes. Don't use for application ingress, load balancing, or service networking (use gke-service-networking instead).

1k tokens
Azldev Add Component
by microsoft
vendor

Read this before adding or importing a component; follow the workflow instead of guessing. Explains how to add a new component to an azldev distro, covering inspecting the upstream spec, the inline-versus-dedicated-file decision, and validating with render, diff-sources, and build. Triggers include add component, new package, import package, create comp.toml, new component.

998 tokens
Open Knowledge Pack Plain Notes
by inkeep

How to work in a Plain Notes project (the `plain-notes` starter pack): a flat notes/ folder plus a daily/ journal. The 'I just want to write' layout. Read when the project has these folders, OR when asked to jot a note, capture a quick thought, or write today's journal entry. Carries the linking habit and daily-entry behavior so templates and folder descriptions stay minimal. Complements the platform `open-knowledge` skill; does not replace it.

498 tokens
Open Knowledge Pack Worldbuilding
by inkeep

How to work in a Worldbuilding project (the `worldbuilding` starter pack): a fiction encyclopedia of characters, settings, themes, factions, and lore. Read when the project has these folders, OR when asked to add a character, setting, faction, or piece of lore, or to check the world for internal consistency. Carries the auto-stub and consistency behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.

758 tokens

How to use it

Copy the folder

Take product-on-purpose/utility-slideshow-creator 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.