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.
- Installs
- 723
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/product-on-purpose/pm-skills --skill utility-slideshow-creator- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads utility-slideshow-creator automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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 |
FAQ
What does the utility-slideshow-creator skill do?
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.
How do I install utility-slideshow-creator?
Run npx skills add https://github.com/product-on-purpose/pm-skills --skill utility-slideshow-creator in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/utility-slideshow-creator/ (personal) or .claude/skills/utility-slideshow-creator/ (project).
Which AI agents can use utility-slideshow-creator?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is utility-slideshow-creator safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains utility-slideshow-creator?
It is published by product-on-purpose in product-on-purpose/pm-skills. It has 723 recorded installs.
More from product-on-purpose/pm-skills
deliver-acceptance-criteria
product-on-purpose/pm-skills
Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-edge-cases; to write the stories themselves, use deliver-user-stories.
deliver-prd
product-on-purpose/pm-skills
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.
deliver-user-stories
product-on-purpose/pm-skills
Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions. Use when breaking a feature into stories for sprint planning, writing tickets, or communicating scope to engineering. For testable Given/When/Then acceptance criteria on a story, use deliver-acceptance-criteria; for boundary and failure scenarios, use deliver-edge-cases.
deliver-edge-cases
product-on-purpose/pm-skills
Documents edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature - the systematic catalog of what can go wrong and the failure modes to design for. Use during specification to map the failure surface and ensure comprehensive coverage, or during QA planning to identify boundary and limit scenarios to test. Distinct from deliver-acceptance-criteria, which writes story-level Given/When/Then checks; this skill produces the whole-feature edge-case catalog.
discover-competitive-analysis
product-on-purpose/pm-skills
Creates a structured competitive analysis comparing features, pricing, and positioning across 3-5 direct and indirect competitors, with a 2x2 map and actionable strategic recommendations. Use before entering a market, planning differentiation, or after losing deals. For market size rather than competitor positioning, use discover-market-sizing instead.
define-problem-statement
product-on-purpose/pm-skills
Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.