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

What 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 holds the product, the users and a metric dictionary that gives each metric an owner, a source, a base and a period. A slide design system turns your best decks or your brand guide into rules Claude Slides follows. A one-page brief names the audience, the decider, the one thing they must believe and the ask with a date. A ghost deck puts an action title on every slide and the evidence each title needs. 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 one- and two-slide executive summaries, the roadmap review with confidence labels and a costed no list, the strategy deck with its diagnosis and guiding policy, the QBR with commitments against actuals and RAG defined in writing, the business case with do-nothing as an option and kill criteria, the board pre-read — then 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 that traces every figure to a source, a base and a period; the build in your own design system; the restyle that cuts each slide back to one claim; and the read-cold pre-read slidedoc for the people who will not be in the room.

Each skill is one deck type or one deck method, with the inputs it needs, where it breaks, a fixed output template, a finish line and the next skill to run. Mechanically, each one is a folder with a SKILL.md file. The 32 are grouped into six stages, and each gives full value on its own: run one, run a stage, or work through the lot in the order a deck actually comes together.

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 are open on GitHub: polar-bear-org/claude-skills.

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

1. 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

2. 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

3. 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

4. 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

5. 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

6. 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

7. Executive Summary One-Pager

Use when: The exec reads one slide and decides from it

Output: One slide: bottom line, ask with a date, three reasons with one sourced number each

8. Executive Summary Two-Pager

Use when: One slide loses the story and ten is too many

Output: Key points and the ask on slide one, sourced insights worth knowing on slide two

9. 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

10. 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

11. 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

12. 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

13. 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

14. 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

15. 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

16. 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

17. 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

18. 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

19. 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

20. 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

21. 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

22. 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

23. 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

24. 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

25. 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

26. 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

27. 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

28. 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

29. 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

30. 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

31. 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

32. 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

How to use it

There is no compulsory sequence. You bring the deck you owe somebody — the roadmap review next week, the Friday stakeholder update, the twenty minutes with the CPO where you ask for two more engineers — and open the skill that matches it. The two set-up skills are worth running first all the same: deck-context-setup and deck-design-system are saved once to a Project, and they are what stop Claude guessing your metrics and inventing its own layouts in every deck after.

Most of them chain. deck-brief fixes the decider and the ask, deck-storyline turns that into action titles before anything is drawn, and deck-doc-to-deck does the same job when the PRD or the strategy doc already exists; deck-audience-cuts then splits one master deck per room with a single change log. The leadership set runs from deck-exec-one-pager and deck-exec-two-pager through deck-roadmap-review, deck-product-strategy, deck-qbr and deck-business-case up to deck-board-slides. deck-stakeholder-update, deck-all-hands, deck-research-readout and deck-onboarding carry the news outward; deck-sprint-review, deck-retrospective, deck-working-agreement, deck-okr-check-in, deck-kickoff and deck-offsite run the team's own rituals; and deck-launch-gtm, deck-case-study, deck-sales-demo, deck-advisory-board and deck-conference-talk face customers and the market. Whatever you drafted, deck-numbers-check traces every figure, deck-build-in-template lays it out in your own design system, deck-restyle cuts each slide to one claim, and deck-pre-read turns it into something that reads cold.

The sources behind each method are in resources/evidence-and-sources.md inside the pack.

Setup guide

1. Download the pack. One zip: an install folder with 32 ready-to-upload skill zips, a skills folder with the same 32 skills as readable SKILL.md files, and resources/evidence-and-sources.md, which names the source behind every method.
2. Install your skills. In Claude Code, add the marketplace and install slides-for-product-managers-pack, and all 32 load at once. In Claude, turn on code execution and file creation in Settings, Capabilities, then go to Customize, Skills and upload one zip per skill from the install folder. On Team and Enterprise plans an owner enables Skills and cloud code execution first. Prefer working from files? Add the SKILL.md files to your Project knowledge instead; it works, just less cleanly.
3. Set up once, then bring one deck. Start with deck-context-setup on your metrics doc and last quarter's QBR, and deck-design-system on your two or three best decks or your brand guide, both saved to a Project. After that every skill works from what you paste — the metrics export, the PRD, the discovery notes, the figures finance gave you — and drafts in Claude Slides with your layouts and your numbers.

Where to start

The quality bar

Every skill in the pack holds the same standard, the one we hold for the decks we make 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

Who made this

Polar Bear is a people ops consultancy for human-size teams (20 to 200 people). Built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. This pack is the free, self-serve version of how we work.

The pack carries one product desk's decks. When you want your whole team working this way, AI carrying the overhead so people do the part only people can do, across hiring, management and everyday operations, that's what we build with clients.

Meet Pauline. A deck that drifts from the brand, or numbers nobody can trace? Bring the deck and the decision the room has to make. Book a 30-minute call · Pauline on LinkedIn

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 and upload each skill from its install folder under Customize → Skills.