Skip to content
Back to skills

Flink Founder Interview

ASecurity

Interviews you about your week one question at a time and produces Founder Interview Notes with your answers word for word and the two ideas worth a post. Use for "run flink-founder-interview", "interview me about my week", "I have nothing to post", "find me a post idea from this week", "ask me questions so I can write", "what should I post about", "help me find something to say", part of the Claude Playbook for Authentic LinkedIn Presence Pack by Polar Bear.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 5, 2026
ai-agentsgo

Works with

  • cli

Security analysis

A100/100

Scanned October 5, 2026

npx -y skills add polar-bear-org/claude-skills --skill flink-founder-interview --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Flink Founder Interview?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Flink Founder Interview
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/polar-bear-org-flink-founder-interview/badge)](https://www.skillsdirectory.com/skills/polar-bear-org-flink-founder-interview)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: flink-founder-interview
description: Interviews you about your week one question at a time and produces Founder Interview Notes with your answers word for word and the two ideas worth a post. Use for "run flink-founder-interview", "interview me about my week", "I have nothing to post", "find me a post idea from this week", "ask me questions so I can write", "what should I post about", "help me find something to say", part of the Claude Playbook for Authentic LinkedIn Presence Pack by Polar Bear.
---

# Founder Interview

## When To Use
You sit down to post and have nothing to say, though your week was full of calls, decisions and small fights. This skill asks you about what actually happened, writes down your answers as you said them, and answers one question: which two things from this week are worth a post?

## When Not To Use
If you want to work from what clients asked across the month, run Client Questions Log instead. If you already recorded yourself talking through an idea, Voice Memo to Post is the shorter road.

## Inputs
- Twenty minutes and your memory of the last seven days; your calendar open helps.
- Your Buying Situations Map, if you have one, to judge which ideas a buyer would care about.
If you have none of this, I start from the first question and mark the two ideas as a first draft to check against your buying situations later.

## Approach
Questions about past behaviour, not opinions, are standard customer interview practice: "what happened last time" gets a real moment, "what do you think about" gets a speech. Here they are turned on your own week, in six moments adapted from the case interview: a client question, a disagreement, a surprise, a mistake, a number you saw, a decision. The failure it prevents is the post that starts "Here are five things I believe about leadership" because nobody asked what happened on Tuesday. I ask; I never fill a gap with something you did not say. Works in any chat; with memory and its Topics list on, your past interviews stay to hand.

## Workflow
1. Ask up to three things first: how long you have today, whether you have a Buying Situations Map to share, and which clients must stay out of anything written down. Then start.
2. Ask the six moments in order, one question at a time, waiting for each answer: what a client asked you this week, what you disagreed with, what surprised you, the mistake, a number you saw, a decision you made. Always "this week" or "last time", never "what do you think about".
3. Give each answer exactly one follow-up that goes underneath it: "what exactly did they say?", "what did you do next?", "how did you know?". If an answer is thin, the follow-up goes to the room, the sentence, the screen; I do not offer a better answer.
4. Record every answer word for word, hesitations cut, wording untouched. Clients and colleagues appear by role only ("a past client", "the finance lead"). A moment with nothing this week is recorded as "nothing this week" and skipped, never filled.
5. Read the notes back and test each moment: it happened, it is specific, and a buyer in one of your buying situations would care. Propose the two that pass best, quoting your own sentence that carries each, with the buying situation it serves.
6. You confirm, swap or drop the two. Any number or client line in them is flagged for the Claim and Permission Check before it goes near a draft.

## Output Format
```markdown
# Founder Interview Notes
Week of [date]. Clients named by role only.
## Your answers
| Moment | Question asked | Your answer, word for word | Follow-up answer |
|---|---|---|---|
| Client question | [question] | [answer] | [answer] |
| Disagreement | [question] | [answer] | [answer] |
| Surprise | [question] | [answer] | [answer] |
| Mistake | [question] | [answer] | [answer] |
| Number you saw | [question] | [answer] | [answer] |
| Decision | [question] | [answer] | [answer] |
## Two ideas worth a post
| Idea in one line | Your sentence that carries it | Buying situation | Needs a claim check? |
|---|---|---|---|
| [idea] | "[quote from above]" | [situation] | [yes or no, and why] |
| [idea] | "[quote from above]" | [situation] | [yes or no, and why] |
## Decision
[You decide which of the two goes into the Idea Bank and which you draft first, by [date].]
```

## Done When
- All six moments were asked, one at a time, each with one follow-up or marked "nothing this week".
- Every answer is in your words; nothing was tidied, added or guessed.
- Clients and colleagues appear by role only.
- The two ideas each quote a sentence you said and name a buying situation, and you confirmed them.

## Quality Bar
- One question per message; the interview stops when you say so.
- Questions ask about what happened, never for opinions in the abstract.
- An empty moment stays empty; Claude never suggests what you might have meant.
- A number is recorded exactly as you said it, with "about" if you said "about".
- Your answers are kept word for word; Claude asks, never fills a gap.

## Next
Run flink-client-questions-log (Client Questions Log) to add what clients asked across the month.

## About the makers

This pack is made by Polar Bear, a consultancy 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).

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…