October 2026 · 9 min read · 32 skills, free

Claude Slides for Product Managers: 32 Claude Skills for Every Deck You Have to Make

Every deck starts the same way: your metrics with their sources, a slide design system, a brief naming the decider and the ask, a ghost deck of titles. Then the decks for leaders, the updates, the team rituals, the customer decks, and the pass that traces every number before it goes out.

01What these skills are

Every deck a product person makes, from the metric dictionary to the version people read cold, as installable Claude skills

This is Claude Slides for the decks the product job keeps asking for, starting from the room and the decision rather than a blank first slide: Claude drafts the deck from your own sources, and you are the one who decides what the room is asked to decide.

Every deck starts the same way: a deck context file with a metric dictionary, a slide design system, a one-page brief and a ghost deck with an action title on every slide. Only then does anything get drawn.

The red line: Claude Slides drafts the deck from your sources. Every number on a slide traces to one, nothing is invented to fill a gap, and you decide what the room is asked to decide.

From there the skills follow the room the deck is made for: the decks for leaders, the updates everyone gets, the team rituals, and the decks that go to customers and the market.

The last four run over a deck that already exists: a numbers register, the build in your own design system, the restyle that cuts each slide back to one claim, and the read-cold pre-read slidedoc.

Each skill is one deck type or one deck method, with a fixed output template and the next skill to run. The 32 are grouped into six stages, and each gives full value on its own.

Download all 32 skills

One zip: ready-to-install skill zips, readable SKILL.md files, and the notes naming the source behind every method. Free, no signup. The same 32 skills live in our open repo, if you would rather read them before you install them.

Download the zip Browse on GitHub

Install in Claude Code

Two lines, and every skill in the pack loads at once.

/plugin marketplace add polar-bear-org/claude-skills
/plugin install slides-for-product-managers-pack@polar-bear-skills

Using Claude on the web instead? Download the zip above and upload each skill from its install folder under Customize → Skills.

02The catalog

The 32 skills you get

The set follows a deck from setup to the version people read cold, in six stages: the start every deck runs from, the decks for leaders, the updates for everyone, the team decks, the decks for customers and the market, and the passes that make a deck hold up.

1 · Start every deck

Deck Context File

Use when: Every deck starts from zero and Claude guesses your metrics
Output: deck-context.md: product, users, metric dictionary with owner, source, base and period, audiences, house words

Slide Design System

Use when: Every deck looks different and AI slides ignore your brand
Output: Layout library, grid, type scale, colour roles, chart and table styles, components, do and don't rules

Deck Brief

Use when: You cannot get to the point for execs, and decks end with no ask
Output: Audience and decider, the one belief or decision, live or read cold, facts with sources, the ask with a date

Ghost Deck Storyline

Use when: Decks eat days of rework and the draft has no argument
Output: Action title per slide, evidence per title, executive summary in SCR order, slide budget, titles-only read

Doc to Deck

Use when: The doc exists and the room still wants slides
Output: Deck drafted from a PRD, PR-FAQ, strategy doc or report, keep-in-the-doc list, doc-versus-deck check

Audience Cuts

Use when: One update, many audiences, and four files to keep in sync
Output: Exec, sales, company and customer cuts, each with its own first slide and ask, one change log

2 · Decks for leaders

Roadmap Review Deck

Use when: Dates become promises and the loudest leader sets the roadmap
Output: Strategy recap, shipped vs said, Now Next Later with confidence, not doing and why, decision needed

Product Strategy Deck

Use when: There is no clear strategy to say no against
Output: What is and what could be, diagnosis, guiding policy, coherent actions, what we will not do, endorsement asked

Quarterly Business Review Deck

Use when: QBR prep is days of chasing data and green is not green
Output: Headline, asks first, commitments vs actuals, metrics with base and period, defined RAG, customer variant

Business Case Deck

Use when: The business case numbers are guesses everyone sees through
Output: The ask, cost of doing nothing, options including do nothing, value as ranges, kill criteria

Board Deck Product Section

Use when: The work is invisible to the board and rebuilt every quarter
Output: Three to five pre-read slides, the question for the board, fewest correct metrics, shipped vs planned

3 · Updates for everyone

Stakeholder Update Deck

Use when: You spend Friday on an update people skim in seconds
Output: What changed, what is at risk, what we need from you, sourced metric, dates with confidence, recurring version

All-Hands Deck

Use when: The company sees ticket lists and never the why
Output: Where we are, what shipped and for whom, the honest metric, decisions and reasons, thanks by name, Q&A prompts

Research Readout Deck

Use when: Research is scarce and the readout must change something
Output: The finding that changes a decision, method and sample, findings with quotes, contradictions, the decision asked

Product Onboarding Deck

Use when: New joiners get a sixty-slide history lesson that is out of date
Output: Product and users, strategy, roadmap now, how we decide, who owns what, first 30 days, glossary

4 · Team decks

Sprint Review Deck

Use when: Sprint reviews turn into slide shows and stakeholders only watch
Output: Sprint goal, done and ready to try, demo order, questions for stakeholders, backlog changes, five slides at most

Sprint Retrospective Deck

Use when: Retros repeat the same complaints and nothing changes
Output: Prime Directive, chosen format, last actions and what happened, prompts, one to three experiments with owners

Working Agreement Deck

Use when: The team argues about the same habits and nothing is written down
Output: The friction, draft agreements as testable behaviours, non-negotiables, a decision rule, a review date

OKR Check-In Deck

Use when: OKRs are set in January and reviewed in panic in March
Output: Key results with current value and source, confidence and why it moved, blockers, decisions needed

Kickoff Deck

Use when: Kickoffs are read aloud and nobody leaves knowing who decides
Output: Why now, goal and success measure, scope in and out, roles and decision rights, risks, first milestones

Team Offsite Deck

Use when: The offsite is a week away and the agenda is a list of talks
Output: Agenda with an outcome per session, announcements, recognition, connection moments, decisions, what happens after

5 · Decks for customers and the market

Go-to-Market Launch Deck

Use when: Sales and support learn about the launch from customers
Output: Launch in one customer sentence, positioning and proof, tier and date, readiness by owner, sales cut, success metric

Customer Case Study Slides

Use when: Case slides show results with no baseline and logos nobody cleared
Output: One or five slides: the change in the title, before, what they did, results with base and period, approved quote

Sales Demo Deck

Use when: Thirty slides of company intro delay the product
Output: What we heard, the outcome wanted, the result shown first, two or three workflows, proof, a dated next step

Customer Advisory Board Deck

Use when: The advisory board turns into a sales pitch and the loop never closes
Output: What you told us and what we did, product forks framed as options, a concept to react to, exercise prompts

Conference Talk Deck

Use when: A talk turns into a pitch with figures that cannot leave the building
Output: One idea, a sourced hook, what is vs what could be, three stories, what to try on Monday, confidential-number check

6 · Make it hold up

Numbers Check

Use when: Made-up or mismatched numbers reach the board
Output: Every figure with slide, source, base, period and status, mismatches, draft marks, the chart each figure needs

Build in Your Design System

Use when: The content is right but every draft drifts from the brand
Output: Storyline laid out with your layouts and components only, a rule check per slide, exceptions to approve

One Claim per Slide Restyle

Use when: The Claude Slides draft is competent but plain and reads as AI
Output: Dense slides split, sentence titles, evidence instead of bullets, AI tells removed, before and after list

Pre-Read Slidedoc

Use when: The deck will be read, not presented, or people will not attend
Output: Read-cold version with full-sentence slides, the decision on page one, source appendix, cover note

03How to use it

Pick the workflow that matches your week

No fixed order. Bring the deck you owe somebody and open the skill that matches it. The two set-up skills are worth running first.

Set up once

Before the first deck, so Claude stops guessing your metrics and inventing its own layouts.

Deck Context File
Slide Design System

Start any deck

A deck is due and nothing is drawn yet.

Deck Brief
Ghost Deck Storyline
Audience Cuts

From a doc to a deck

The PRD or the strategy doc already exists.

Doc to Deck
Audience Cuts

Decks for leaders

The roadmap review is next week.

Roadmap Review Deck
Product Strategy Deck
Quarterly Business Review Deck
Business Case Deck
Board Deck Product Section

Customers and the market

The deck leaves the building.

Go-to-Market Launch Deck
Customer Case Study Slides
Sales Demo Deck
Customer Advisory Board Deck
Conference Talk Deck

Make it hold up

The deck is drafted and has to survive the room.

Numbers Check
Build in Your Design System
One Claim per Slide Restyle
Pre-Read Slidedoc

04Setup guide

Install it in five minutes

In Claude Code · two lines

/plugin marketplace add polar-bear-org/claude-skills
/plugin install slides-for-product-managers-pack@polar-bear-skills

In Claude.ai or Claude Desktop · seven clicks

Download the pack, then open Settings
Unzip the pack: its skills folder holds all 32 skills. In Claude, click your name at the bottom left, then Settings.
Download the zip
Open Skills and click Add
Under Customize, choose Skills. Click Add, then Upload a skill.
Drop in a skill file
Drag the skill's file into the box, or click to browse. You can add several at once.
Pick the skill from the pack
In the pack folder, open skills, then the skill you want, and select its SKILL.md — deck-context-setup is a good first one.
Check the preview and upload
Claude shows the skill's name and what it does. Click Upload.
Make sure it is switched on
The skill opens on its own page. Its toggle should be on.
Try it in a new chat
Type / and the skill's name, then say what you need.

Then try one

Run deck-context-setup on my metrics doc and last quarter's QBR: [paste them here]

Run deck-brief for [the deck I owe]. Audience, decider and ask: [paste what you know here]

Run deck-numbers-check on this deck: [paste it here]

Lantern for product managers

Turn your review decks into posts your market sees

Lantern drafts a week of posts from your notes and call transcripts, in your voice. You review them and publish the ones you like.

100 free credits, about ten posts. No card needed.

Try for free

05Quick reference

Where to start

Your situation	Skill to run
Need Claude to know your metrics and their sources?	Deck Context File
Need every deck to look like yours?	Slide Design System
Need to know who decides and what you ask?	Deck Brief
Need the argument before the slides?	Ghost Deck Storyline
Need slides from a doc that already exists?	Doc to Deck
Need one slide an exec can decide from?	Executive Summary One-Pager
Need a roadmap review without false dates?	Roadmap Review Deck
Need a QBR with honest status?	Quarterly Business Review Deck
Need an update people read and act on?	Stakeholder Update Deck
Need a sprint review that gets feedback?	Sprint Review Deck
Need every number traced before it goes out?	Numbers Check
Need a version people read without you?	Pre-Read Slidedoc

06Standards

The quality bar

Every skill in the pack holds the same standard, the one we hold for the documents we write ourselves:

One method, applied properly: each skill uses the real mechanics of its method — the answer-first order, the action titles, the delivery confidence definitions, the Now Next Later horizons — not a generic gather, analyse, recommend
Story before slides: the audience, the decider and the ask come first, then a ghost deck of titles, then Claude Slides draws
Every skill says where its method breaks, and what fits instead
Numbers that hold: every figure carries a source, a base and a period, anything without one stays marked as a draft, and the same figure is checked across slides
Built for Claude Slides as it is: the skills use only the drafting, editing, commenting, presenting, sharing and exporting that Anthropic has published, and your look comes from written design rules, not from a claim that Slides reads your template
Work is described, people are not: team decks describe how the work works, thanks go by name and are never ranked, and no slide scores, ranks or profiles a person
The red line: Claude Slides drafts the deck from your sources; every number on a slide traces to one, nothing is invented to fill a gap, and you decide what the room is asked to decide

07FAQ

Questions people ask

What is in the Claude Slides for Product Managers pack?

32 Claude skills for the decks a product person makes, in six stages: start every deck, decks for leaders, updates for everyone, team decks, decks for customers and the market, and make it hold up. Each skill is one deck type or one deck method.

How do I install these Claude skills?

In Claude Code, two lines install all 32 at once. In Claude.ai or Claude Desktop, download the zip, open Settings, Skills, Add, and upload the skills you want. Either way it takes about five minutes.

Do I need Claude Code to use them?

No. The skills work in Claude.ai, Claude Desktop and Claude Code. In the app you upload them yourself; in Claude Code one command installs the whole pack.

Do the skills work with ChatGPT or other assistants?

They are built as Claude Skills, and installing them is a Claude feature. Each one is a plain Markdown file, so you can read it and reuse the method elsewhere, but it will not load and trigger by itself outside Claude.

Will Claude decide what the deck asks for?

No. Claude Slides drafts the deck from your sources. Every number on a slide traces to one, nothing is invented to fill a gap, and you decide what the room is asked to decide.

Is the pack free?

Yes. It is free to use inside your company and in client work, and not for resale. There is no signup: the download and the install command are on this page.

08Who made this

Lantern, by Polar Bear

These skills were written by Polar Bear, a people ops consultancy that runs its own company on Claude. The pack is free, and the same skills are open on GitHub.

Lantern is Polar Bear's content workspace. It turns your notes, documents and call transcripts into drafts for LinkedIn and other networks. You review them and publish the ones you like.