Skip to content

borghei/Claude-Skills / tools/linkedin/linkedin-story-interviewer

linkedin-story-interviewer

Verified

Interviews a person to surface what they actually have to say, and keeps the answers in a local story bank file that later LinkedIn drafts draw on. Use when someone has never posted, when drafts keep coming out generic, or when the story bank is thin or stale.

references/question-sets.md

View on GitHub
# Question Sets

Questions grouped by the kind of entry they tend to produce. They are prompts
to choose from, not a script: pick the one that fits what the person has just
said, and change the nouns to theirs. Each set ends with the follow-up that
turns a first answer into a usable entry.

All of these are working heuristics from interviewing practice. None is
guaranteed to land with a given person; if a question produces a shrug, drop
it and try a more physical one.

## Contents

1. What makes a question work
2. Openers
3. Role
4. Figure
5. Build
6. Reversal
7. Cost
8. Stance
9. Anecdote
10. Pillar-specific prompts
11. Boundary questions
12. Questions that reliably produce nothing

## 1. What makes a question work

| Property | Why it matters | Weak | Stronger |
|----------|----------------|------|----------|
| Asks about an occasion | Memory is stored as events, not as lessons | "What have you learned about hiring?" | "Tell me about the last offer you made that was turned down." |
| Has one clause | Compound questions get half-answered | "When and why did you move teams?" | "When did you move teams?" |
| Uses their noun | Saves them translating | "your tracking system" | "the board" |
| Cannot be answered with a title | Titles are already on the profile | "What do you do?" | "What lands on your desk that nobody else wants?" |
| Leaves the judgement to them | Leading questions return your opinion | "That must have been frustrating?" | "What happened next?" |

## 2. Openers

Use one. Then follow.

- "What has been taking more of your attention than it should lately?"
- "If a new colleague shadowed you tomorrow, what would surprise them by lunchtime?"
- "What is the question people in your field keep asking you?"
- "What are you tired of watching other teams get wrong?"
- "What did you finish most recently that you were relieved to finish?"

While they answer, write down every thing mentioned in passing. Those are the
threads for the next half hour.

## 3. Role

Purpose: one or two entries that establish where the person has stood and what
they were answerable for. Keep this short; roles are context, not content.

- "Which job taught you the most, and what were you on the hook for there?"
- "When something broke at that place, what kind of problem was brought to you?"
- "How big was it: people, budget, sites, customers? Whichever you counted."
- "What was the job before you arrived, and what was it when you left?"
- "What did you do there that was not in the job description?"

Follow-up: "Which year did that start and end?"

## 4. Figure

Purpose: numbers the person can say without looking anything up. These are the
most reused entries in the bank.

- "What is one number from your work you could state right now from memory?"
- "What do you measure every week that most people in your role do not?"
- "What was it before you changed it, and what was it after?"
- "What did that cost, all in?"
- "How long did it take, compared with how long you said it would take?"
- "How many times have you done this? An honest count."

Follow-up, always both parts: "What exactly does that number count?" and "How
do you know: a report, a ledger, your own tally?"

If the person is unsure, do not help. Mark it soft and ask them to check.

## 5. Build

Purpose: things that exist because of them. Not only products: a process, a
team habit, a document everyone still uses, a hire.

- "What is still in use today that you started?"
- "What would stop working at your last company if your contribution were removed?"
- "What did you make that was meant to be temporary?"
- "What did you build that nobody asked for?"
- "Which hire are you proudest of, and what did they go on to do?"
- "What did you remove that people expected to miss and did not?"

Follow-up: "What was your part in it specifically, as opposed to the team's?"

## 6. Reversal

Purpose: a belief held and then dropped. These carry posts well because they
contain a before, an after and a reason.

- "What did you argue for a few years ago that you would argue against today?"
- "What advice did you used to give that you have stopped giving?"
- "When were you most confident and most wrong?"
- "What practice did you copy from a previous employer and later abandon?"
- "What did a junior colleague turn out to be right about?"
- "What tool or method were you sceptical of that you now rely on?"

Follow-ups: "What would you have said about it back then, in one sentence?"
then "What was the day you noticed you no longer believed it?"

## 7. Cost

Purpose: what went wrong and what it took. A cost differs from a reversal: the
person may still hold the same view, but they paid for something.

- "Tell me about a week that went badly because of a decision that was yours."
- "What is the most expensive shortcut you have taken?"
- "Which customer, project or hire did you lose that you still think about?"
- "What did you postpone that came back larger?"
- "When did you last have to apologise on behalf of your work?"
- "What did you ship or sign off knowing it was not ready?"

Follow-up: "What did it cost: money, weeks, a relationship, someone leaving?"
then "What do you do differently now, concretely?"

Go gently. If the person hesitates, offer the exit: "We can leave this one
out." If they take it, record the subject under no-go.

## 8. Stance

Purpose: an opinion with opponents. Without someone who disagrees, it is a
platitude.

- "What does your field treat as settled that you think is wrong?"
- "What do you refuse to do that most of your peers do routinely?"
- "What popular advice in your area would you tell a friend to ignore?"
- "What do you insist on that colleagues find excessive?"
- "Where do you side with the unfashionable view?"
- "What would you change about how your profession trains newcomers?"

Follow-ups: "Who specifically would argue with you?" and "What has holding
that view cost you: a deal, an argument, a reputation for being difficult?"

If there is no opponent and no cost, the entry stays soft.

## 9. Anecdote

Purpose: stories the person already tells in person. They are pre-tested; the
person knows where listeners laugh or go quiet.

- "Which story do colleagues ask you to tell again?"
- "What do you tell new starters in their first week?"
- "What happened once that you still cannot quite believe?"
- "Who is the most memorable person you have worked with, and what did they do?"
- "What is the strangest reason a project of yours was delayed?"

Follow-up: "Tell it the way you tell it at the table, including the ending."
Record a line or two verbatim in `words`.

## 10. Pillar-specific prompts

When the audit reports a thin pillar, aim questions at it directly.

| Pillar type | Prompt |
|-------------|--------|
| Teaching how the work is done | "What is the first thing you check when you inherit someone else's work?" |
| Teaching how the work is done | "What takes you ten minutes that takes a newcomer a day, and what are you doing differently?" |
| First-person episodes | "What was the most recent day that did not go to plan? Start from the morning." |
| People and teams | "Who taught you something without meaning to?" |
| People and teams | "What did you change about how you run meetings, handovers or reviews, and what triggered it?" |
| Customers and the market | "What did a customer say recently that you wrote down?" |
| Customers and the market | "Which request do you keep refusing, and why?" |
| What you sell or offer | "Who is it not for? Describe the person you would turn away." |
| What you sell or offer | "What did the last person who said yes ask about just before they decided?" |
| Decisions and trade-offs | "What were the two options you did not take, and what would each have cost?" |

## 11. Boundary questions

Ask these directly near the end of every session. Do not infer the answers.

- "Is there anyone who has come up today that I should never name?"
- "Is there anyone I should check with you about each time?"
- "Is there any subject you want kept out of posts entirely, however good the story?"
- "Is any of this covered by an agreement, a live dispute or an announcement that has not been made?"
- "Are any of these figures ones your employer would not want public?"

## 12. Questions that reliably produce nothing

Avoid these. Each has a replacement that asks about an occasion instead of an
abstraction.

| Avoid | Why it fails | Ask instead |
|-------|--------------|-------------|
| "What are your key achievements?" | Triggers CV language | "What are you still pleased about from the last two years?" |
| "What is your leadership philosophy?" | Invites slogans | "What did you do the last time two people on your team disagreed?" |
| "What makes you unique?" | Nobody can answer this about themselves | "What do people come to you for instead of going to someone else?" |
| "What are your values?" | Returns a list of nouns | "What have you turned down because it did not sit right?" |
| "What lessons have you learned?" | Lessons arrive pre-polished and generic | "What happened?" and derive the lesson later |
| "What is your story?" | Too large to start | "Where were you working five years ago this month?" |
| "Can you give me some statistics?" | Sounds like an audit | "Roughly how many, if you had to count?" then ask how they know |
| "Why should people follow you?" | Produces self-promotion or embarrassment | "Who wrote to you after something you said or wrote, and what did they ask?" |
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall