10 Claude Skills That Turn One Interview Into Every Case Study

What these skills are

Every format of one case, written from one honest source. A firm's best project is usually an anecdote three people can tell. It was delivered, it worked, and six months later the lead has moved on, the client contact has changed jobs, and the only records left are the proposal and the invoice — which between them prove that something was sold and something was paid for.

One line holds the whole pack together: every case starts with a real interview, and Claude writes every format — it never supplies the experience.

So the pack starts with thirty minutes. case-interviewer sits with the person who ran the project, asks one question at a time, and writes the source file: the story in order, every number with its base, its period, its source and a named person who will defend it, the client's lines as they were said, what must not be claimed, and how the client may be named. Every other skill writes from that one file and from nothing else.

What none of them will do is fill a gap. If the interview did not produce the number, the quote or the scene, the case says less. And getting the client's permission to publish stays your relationship: the pack reminds you once, drafts nothing to the client, and never marks a case as approved.

Mechanically, each skill is one folder with a SKILL.md file. One gets the story down, two write it, three build it as real PowerPoint files through code execution, and four put it to work where a case earns its keep. They run from one Claude Project with a pinned chat per case, and each reads what the ones before it wrote, by file name — so what accumulates over a year is the firm's proof: every case, in every format, from one honest source each.

Download all 10 skills. One zip: ready-to-install skill zips, readable SKILL.md files, and the two templates the pack runs on — the firm context and the blank case source. Free, no signup. The same 10 skills are open on GitHub: polar-bear-org/claude-skills.

The 10 skills you get

One skill gets the story down, two write it, three build it as files you can send, and four put it to work.

1 · Get the story down

1. Case Interviewer

Use when: The project just wrapped and you want the story down before the team rolls off

Output: The source file every other skill reads: the story in order, the numbers with their source and a named defender, the client's lines as they were said, what must not be claimed, and how the client may be named

2 · Write the case

2. Website Case Writer

Use when: You need this on the work page by Friday

Output: The short web case, 400 to 700 words: the snapshot, the honest before, what was done, what changed with its base and period, one quote, one takeaway

3. Long-Read Case Writer

Use when: The buyers you want read the long ones, and you want them to see how you think

Output: The long read, 1,500 to 2,500 words, in magazine shape: the decisions, the missteps, the thing a reader can learn, with an image list and captions

3 · Build the documents

4. Case One-Pager Builder

Use when: The prospect asked for something they can forward

Output: The A4 leave-behind as a real PowerPoint file, and a PDF when it can export one, in your colors and type, built through code execution

5. Case Two-Pager Builder

Use when: One page is too thin for this buyer and the deck is too much

Output: The two-page version as a real PowerPoint file: page one the story, readable alone, page two the approach, the results, the quote and the next step

6. Credentials Slide Builder

Use when: You pitch Tuesday and this case belongs in the deck

Output: The one slide, built inside your own deck template when you give it one: the change in the title, three lines, one to three figures, the logo if the client allows it

4 · Put it to work

7. LinkedIn Case Post Writer

Use when: You want to tell people about this one without sounding like everyone else

Output: The post from the firm and the post from the lead, in the lead's own voice, plus a carousel outline — with the anti-slop rules built in and nothing the source file does not contain

8. Award Entry Writer

Use when: The deadline is in two weeks and you are wondering whether you can enter this

Output: The category recommended first, in the category's own words, then the entry written for a jury reader inside the form's word counts, with results only from the source file

9. Proposal Case Paragraph Writer

Use when: The proposal needs proof and the full case is too long

Output: The 120 to 180 word case paragraph matched to this prospect's situation, plus a 40-word version — mirroring by selection, never by alteration

10. Case Video Script Writer

Use when: Marketing wants a short video and nobody wants to sound scripted

Output: A 60 to 90 second script for the lead or the client to say on camera, built from lines that were actually said, with a shot list a phone can shoot and the lower thirds

How a case runs through the pack

One Case Study HQ project holds the firm. The filled firm-context.md sits in its files — the tone, the words you never use, the colors, the type and the logo, how you usually name clients, who confirms a number — and every skill reads it before writing. Then one pinned chat per case, named "Case: [slug]".

The chat opens with case-interviewer, which writes case-source-[slug].md. website-case-writer usually takes it first, because the headline and the figures it settles with you become the phrasing every other format inherits; long-read-case-writer works from the same file for the buyers who want to watch you think. case-one-pager-builder and case-two-pager-builder build the leave-behinds as real PowerPoint files and keep one grid between them, and credentials-slide-builder drops the single slide into your own deck template.

From there the case goes to work. linkedin-case-post-writer writes the firm's post and the lead's, in the lead's own voice. award-entry-writer reads the category descriptions before it writes a word, and says so if the source cannot carry the category you wanted. proposal-case-paragraph-writer leads with the part of the story that mirrors the prospect in front of you. case-video-script-writer arranges lines that were actually said into ninety seconds a phone can shoot.

It stops where your relationships start. The pack does not get the client's permission, run a publishing rhythm or a backlog, audit what has gone stale, design the web page, or promote the finished case once it is out. And it writes the video script; it does not film it.

Setup guide

1. Download the pack. One zip: an install folder with 10 ready-to-upload skill zips, a skills folder with the same skills as readable files, and the two templates the pack runs on — firm-context.md and case-source.md.
2. Install your skills. In Claude Code, add the marketplace and install case-study-factory-pack, and all 10 load at once. In Claude, turn on code execution in Settings, Capabilities — without it the pagers and the slide cannot be built — then go to Customize, Skills and upload one zip per skill from the install folder. Prefer working from files? Add the SKILL.md files to your Project knowledge instead; it works, just less cleanly.
3. Create your Case Study HQ. Make one Project per firm and call it Case Study HQ. Fill firm-context.md once — who you are, the work you want more of, your tone and the words you never use, your colors, type and logo, how you usually name clients, and who confirms a number — and upload it. Every skill reads it before writing a word.
4. Open one chat per case, and run the interview. Pin a chat named "Case: [slug]" for the project you are proudest of this year, and write "run case-interviewer". Thirty minutes later case-source-[slug].md is in the Project, and every writer reads it by that name, saving alongside it: case-web-[slug].md, case-longread-[slug].md, case-onepager-[slug].pptx, case-slide-[slug].pptx, and the rest. Every skill also runs alone: without the source file it does a ten-minute interview first and marks its output accordingly.

Where to start

The quality bar

Every skill in the pack holds the same standard, the one we hold when we write up our own work:

• Every case starts with a real interview: Claude writes every format, it never supplies the experience
• No gap is filled with a plausible number, quote or scene — if the interview did not produce it, the case says less
• Every number is the client's number, with its base, its period, its source and a named person who will defend it; a figure with no defender is used in no version
• The client's lines are quoted as they were said, never tidied into something better
• Getting the client's permission is yours: the pack reminds you once, drafts nothing to the client, and never marks a case as approved
• The naming level is set once in the source file — named, sector-only or blind — and every format obeys it; a logo on a slide shown to other clients is a separate yes from the website
• Written from a short interview is said out loud: a case written without the source file is marked as such, and a long read from one is called thin
• The interview is a conversation, not a form: one question at a time, thirty minutes, and what you said is written down before anyone improves it
• The web case opens with the client's situation, not the firm — a buyer reading on a phone is looking for whether this is them
• The proposal paragraph mirrors the prospect by selection, never by alteration: it chooses which true part to lead with, and says the rest less

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 turns one delivered project into every format your firm sends out. When you want your whole team working this way, AI carrying the overhead so people do the thinking, across business development, delivery, and everyday work, that's what we build with clients.

Meet Pauline. Sitting on a project worth telling and no time to write it up? Bring the story — we'll get it down. Book a 30-minute call · Pauline on LinkedIn