Skip to content

sergebulaev/linkedin-skills / .codex-marketplace/linkedin-skills/skills/linkedin-interviewer

linkedin-interviewer

Verified

Interview the user for the raw material their posts are made of. Builds a lasting Story Bank of roles, numbers, turning points, scars and positions, or runs a focused interview that turns one topic into a post spine. Use when a draft has nothing concrete to draw on, or the user says interview me. Not for learning how they write (use linkedin-humanizer --mode profile).

FileKindSize
SKILL.mdskill md8.1 KB
references/question-bank.mdmarkdown4.3 KB

references/question-bank.md

View on GitHub
# Question bank

Questions that reliably produce material a draft can use, and the ones that feel
productive and yield nothing. Grouped by the Story Bank section they fill.

The pattern that separates them: a good question asks about **one moment**. A bad
one asks about a **category**, and gets a summary back. Summaries cannot be
published.

---

## Opening (never a form)

- "What have you been working on that you cannot stop thinking about?"
- "What did you spend most of last week actually doing?"
- "If someone asked what you do, what do you say, and what do you leave out?"

Avoid: "Tell me about your career." It produces a CV read aloud.

## Timeline

- "What were you hired to do there, and what did you end up doing?"
- "What changed between when you joined and when you left?"
- "Which month did that start?" — ask whenever they say *recently* or *a while ago*

## Receipts

The hardest section to fill and the one drafts reach for most.

- "Put a number on that. Even a rough one, and say it is rough."
- "What was it before, and what was it after?"
- "How long did it take, and how many people?"
- "What did that cost, in money or in hours?"
- "How would you prove that to someone who doubted you?"

Avoid: "What were your key achievements?" It produces adjectives.

## Shipped

- "What exists now that would not exist if you had not been there?"
- "What is the thing you point at when someone asks what you have done?"
- "Which part of it was actually yours?" — prevents a post claiming a team's work

## Turning points

- "What did you believe a year ago that you no longer believe?"
- "What did you have to be talked out of?"
- "When did the plan change under you, and what did you do about it?"
- "What advice did you take that turned out to be wrong for you?"

## Scars

- "What is the most expensive mistake you have made professionally?"
- "What did you ship that you would not ship now?"
- "What do you check now that you never used to check?" — the scar is upstream
  of the habit, and this route gets there without asking them to confess

Do not press twice here. One question, accept what comes back.

## Positions

- "What do you think is true that most people in your field disagree with?"
- "What does holding that view cost you?" — no cost, no position
- "What advice does everyone give that you think is wrong?"
- "Who would argue with you about this, and what would they say?"

## Recurring stories

- "Which three stories do you already tell in person?"
- "What is the story you end up telling at every dinner?"
- "What do people ask you about more than once?"

## Naming and limits

Ask directly. Never infer.

- "Can I name that company in a post, or keep it anonymous?"
- "Who would be unhappy to see themselves mentioned?"
- "Is anything here under NDA or still in progress?"
- "What subjects do you want kept out of your posts entirely?"

---

## Post mode, in order

1. "When did this last actually happen to you?" — a scene, not a subject
2. "Walk me through it. What happened first?"
3. "What is the number in this story?"
4. "What did you get wrong at the time?"
5. "Who disagrees with your take on this?"
6. "What should someone reading this do differently tomorrow?"
7. Read the spine back in five lines and let them correct it.

The correction in step 7 is usually the best line in the eventual post. Keep it
verbatim.

---

## Questions that waste the session

| Question | What comes back | Why it fails |
|---|---|---|
| "Tell me about yourself" | a CV | no moment to anchor on |
| "What are your strengths?" | adjectives | unpublishable, and everyone claims them |
| "What are your content pillars?" | marketing vocabulary | asks them to do the strategy |
| "What makes you unique?" | a paragraph of hedging | invites performance |
| "Any other achievements?" | silence | closed, and puts the work on them |
| "Describe a challenge you overcame" | an interview answer | primes a rehearsed shape |

## Handling the three hard moments

**They go quiet.** Not resistance, usually retrieval. Wait. If it persists, drop
to something concrete: "What did you do on Tuesday?"

**They talk for ten minutes.** Let them. Follow-ups are cheaper than a fresh
subject, and the material is in the tangent more often than in the answer.

**They decline.** "I would rather not say" ends that line permanently. Record it
under Off limits so nothing asks again, and say that you have done so.
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