Builds the one case study slide for the firm's credentials deck, inside the firm's own deck template when provided, with the change in the title, three lines, one to three figures, and the logo if allowed, through code execution, part of the Case Study Factory Pack by Polar Bear. Use this whenever the user says "run credentials-slide-builder", "put this case in the creds deck", "a case slide", "one slide on the Acme project", "the pitch is Tuesday and this belongs in the deck", or when a cred...
Installs into .claude/skills of the current project.
Are you the author of Credentials Slide Builder?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/polar-bear-org-credentials-slide-builder)
---
name: credentials-slide-builder
description: Builds the one case study slide for the firm's credentials deck, inside the firm's own deck template when provided, with the change in the title, three lines, one to three figures, and the logo if allowed, through code execution, part of the Case Study Factory Pack by Polar Bear. Use this whenever the user says "run credentials-slide-builder", "put this case in the creds deck", "a case slide", "one slide on the Acme project", "the pitch is Tuesday and this belongs in the deck", or when a credentials deck needs a new case. Use it even for "make a slide of it".
---
# Credentials Slide Builder
A case slide is on screen for forty seconds while someone talks over it, and it is read in the first ten. Everything the deck-building world gets wrong about it comes from treating it as a page: six bullets, a paragraph of context, a logo wall, a chart with a legend. The slide that works has the change in the title, three lines a person can read while listening, one to three figures big enough to be read from the back of the room, and a logo if the client allows it. The presenter tells the story; the slide proves it. I build it inside your deck template when you give me one, so it looks like it was always there.
## How to work with me
Run me in the case's pinned chat in **Case Study HQ**, after `case-interviewer`, or on its own. Code execution on. Fifteen minutes, one round of corrections on the rendered slide. If you upload your credentials deck (pptx), I use its layouts and theme and hand back a one-slide file you drag in, or the deck with the slide inserted where you tell me.
## Before starting
I read `case-source-[slug].md` for the story and numbers, `case-web-[slug].md` or `case-onepager-[slug].pptx` if they exist for the agreed headline and figures, and `firm-context.md` for the deck template name, the layout used for case slides, colors, type, and the naming default. If the source file is missing, I run the ten-minute interview and note it in the reply. If there is no template, I build a clean 16:9 slide in your colors and say so.
I ask you two things: the pitch this slide is for (so the title mirrors that prospect's situation, at the naming level allowed), and whether the client's logo may appear on a slide shown to other clients, which is a permission of its own.
## The slide
- **Title**: the change, in the client's terms, under ten words. "A 60-person software firm whose site now explains itself" is the shape (an example of the form). Not the client name as a title, not "Case study: Acme".
- **Left, three lines**: what was wrong, what we did (the turn), what changed. Each under fifteen words. Read at 18 to 20 pt.
- **Right, the figures**: one to three defended numbers at 40 to 54 pt, a label under each with base and period at 12 to 14 pt. One figure if that is what the source has. None, and the right side becomes one sentence of change in the client's terms, at 24 pt; a slide without a number is honest, a slide with a padded number is a liability the presenter has to defend live.
- **Bottom**: the client logo at the naming level allowed and with logo permission, or the sector line. One real image of the work if the material list has one and the layout has room; never a stock photo, never a mockup that was not built.
- **Speaker notes**: the forty-second talk track from the source's moments (what was wrong, the turn, what changed), plus the one question this slide invites and the honest answer from the source. The presenter reads the notes once and never reads the slide.
## How I build it
With python-pptx. Given your deck, I open it, pick the layout you named (or the closest to a title-plus-content layout), place the elements into its placeholders where they exist and as positioned text boxes where they do not, keep the theme fonts and colors, and export a one-slide pptx plus a rendered preview. Without a deck, a 16:9 slide in your two colors on a system font. The script is saved so the next case slide takes five minutes and matches.
## Output
`case-slide-[slug].pptx` (one slide, with speaker notes), a preview image, and `case-slide-[slug].py`, saved to the project. If you asked for insertion, the deck returned with the slide at the position you named and nothing else touched. The reply lists each figure with its source row and states the naming and logo level used.
## MVP first, AI second
The manual version: duplicate your best existing case slide, replace the title with the change, the three lines, the one big number, the logo, and write the talk track in the notes. Fifteen minutes. The rules are the whole value: title as the change, three lines, figures readable from the back, notes for the presenter.
Run me for the template handling, the type sizes, the notes, and the script that keeps twenty case slides consistent across the deck. The cost: a slide inside someone else's template can land slightly off its grid, which is why I render it for you before you drag it in.
## Boundaries
- Every case starts with a real interview and every number is the client's number with a named person behind it. Figures on the slide come from defended rows only, with base and period, in the allowed phrasing, and I do not enlarge, round, or add one to balance the layout.
- The client's name and logo appear only at the recorded naming level and with logo permission for this use. Getting both is yours; I remind once and never mark the slide approved.
- I do not write a chart the source cannot feed. If the number is one figure, it is a figure, not a bar with an invented comparison.
- The talk track is built from the source's moments; it does not promise what the do-not-claim list forbids, and it names client people by role only.
- I do not redesign your deck. I use its layout and theme, and I say where I placed a text box outside a placeholder.
## About the makers
This pack is made by Polar Bear, a 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. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).