← Back to list
linkedin-interviewer Checked
Interview the user for the raw material their posts are made of. Builds a lasting Story Bank of r…
9.4Overall rating
Installation
🤖 Install via AI
Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.
Install the "linkedin-interviewer" skill by following the instructions at https://skill123.me/install/linkedin-interviewer.
⌨️ Command line install
Run in your terminal — downloads and installs to ~/.claude/skills/.
curl -fsSL https://skill123.me/install/linkedin-interviewer.sh | bash
📦 Download ZIP
Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.
⬇ Download v1.0.0 · 6 KBAbout this skill
Overview
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).
Source
- Repo: https://github.com/sergebulaev/linkedin-skills
- Path: skills/linkedin-interviewer
Score breakdown
Trigger
9.0
Clear What/When plus explicit Not-For versus humanizer profile mode; trigger phrases a bit narrow.
Structure
9.3
145-line SKILL.md plus one focused question bank; clean and minimal.
Workflow
9.2
Two modes, resume support, press-once soft-answer technique, off-limits persistence, read-back verification, refusal anti-patterns.
Content
10.0
Exceptional interview craft writing; concrete good-vs-bad question examples.
Engineering
9.0
Correct frontmatter; writes to bundle-root story-bank.md with tracked-file warning; no scripts.
Security
10.0
No network or credentials; strong privacy defaults (naming limits, off-limits list, gitignore notice).
Conversational Story Bank builder with two modes (broad bank, focused post spine), resumable thin-section tracking, one-question-at-a-time discipline, explicit off-limits memory, and hard never-invent rules. No scripts, no network; even warns that the personal bank file should be gitignored.