# Linkedin Interviewer

Interview the user for the raw material their posts are made of.

- Repository: https://github.com/sergebulaev/linkedin-skills (5474 stars)
- Category: Writing
- License: MIT
- Last updated: 2026-10-27
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add sergebulaev/linkedin-skills --skill linkedin-interviewer -g -a claude-code -y`
Codex: `npx skills add sergebulaev/linkedin-skills --skill linkedin-interviewer -g -a codex -y`
Cursor: `npx skills add sergebulaev/linkedin-skills --skill linkedin-interviewer -g -a cursor -y`
Gemini CLI: `npx skills add sergebulaev/linkedin-skills --skill linkedin-interviewer -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add sergebulaev/linkedin-skills`

## Description

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).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# LinkedIn Interviewer

Every writing skill here demands specifics: one odd-precision number with a named
referent, a dated moment, a position someone would argue with. When the input has
none, the rule is to ask the user rather than invent. That ask happens on every
request, unstructured, and the answers are thrown away when the session ends.

This skill does the asking properly, once, and keeps the answers.

## The two things it fills

| | `references/voice-profile.md` | `references/story-bank.md` |
|---|---|---|
| Holds | how you sound | what you have to say |
| Built from | 3-6 posts you already wrote | an interview |
| Built by | `linkedin-humanizer --mode profile` | this skill |

They are independent. Someone with no LinkedIn history cannot fill the first, but
can always fill the second, which is the usual reason drafts come out generic.

## When to use

- "Interview me", "ask me questions", "help me work out what to post about"
- A writing skill found the Story Bank empty and had to ask for a number mid-draft
- The user is new to posting: no archive to analyse, but a career to draw on
- Before setting up any unattended or scheduled drafting, which has no human
  present to answer a mid-draft question
- The bank exists but has gone stale: a new role, a shipped project, a changed mind

Not for learning someone's writing style from their posts, which is
`linkedin-humanizer --mode profile`. Run both; they answer different questions.

## Modes

### `--mode bank` (default)

A broad interview that fills `../../references/story-bank.md` and keeps it.
Budget 20 to 40 minutes. It can be resumed: the file records which sections are
thin, so a second session picks up there.

### `--mode post`

A focused interview on one topic, 5 to 8 questions, ending in a post spine handed
to `linkedin-post-writer`. Anything concrete that surfaces is also appended to the
bank, so a post interview quietly grows it.

## Steps, bank mode

The rest: https://github.com/sergebulaev/linkedin-skills/blob/HEAD/.codex-marketplace/linkedin-skills/skills/linkedin-interviewer/SKILL.md