When should you use it?
- AI drafts of your posts keep coming out generic
- You are new to posting and have no archive for an AI to learn your voice from
- Before you schedule any unattended drafting, so the drafts have real material
Not for: Learning your writing style from past posts; the same repository has a separate skill for that; Publishing automatically without reading the draft
What do you need, and what do you get?
You need
- Claude Code or Codex with the linkedin-skills repository installed
- Twenty to forty minutes for the first interview
- Your rules on which clients, employers and topics can appear in public
You get
- A story bank file with roles, figures, turning points and positions in your words
- A list of subjects that are off limits
- For a single topic, a five-line post outline handed to the writing skill
How does it work, step by step?
- Install the repositoryAdd the linkedin-skills plugin to Claude Code or Codex and open the folder where your story file will live.
- Do the long interview onceAsk the agent to interview you and answer out loud or in rough notes; it follows what you talk about rather than a form.
- Set the limitsSay clearly which names and subjects must never appear, so later drafts respect them.
- Use topic mode before each postRun a short interview on one topic, check the five-line outline and pass it to the writing skill.
- Keep the file privateExclude the story file from shared or public repositories.
The prompt
Our adapted version, written to work in Claude Code and Claude Cowork. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Use the linkedin-interviewer skill in post mode. The topic is {topic}. Ask me one question at a time and wait for each answer. If I am vague, ask once for a specific number or date, then move on. Do not fill any gap yourself; leave that line empty and say so. Before you finish, confirm with me which people or companies may be named: {naming_rules}.
The original skill is published by sergebulaev on GitHub. Open it there to install or import it; the prompt above is our own adaptation.
What can go wrong?
- The file collects personal and client details; keep it out of any public repo.
- If you give vague answers, the bank stays thin; the skill marks empty sections rather than filling them.
- Check every figure in a finished post against your own records before publishing.
- Interviews only help if you are candid about what went wrong; polished answers produce polished, forgettable posts.
Our take
The common complaint about AI-written LinkedIn posts is that they sound like everyone else, and the usual fix is more style instructions. This skill fixes the input instead. It interviews you for things only you know, such as the month something happened, the number and how it was measured, the belief you dropped and the people who would disagree with you, and it refuses to fill a gap with a guess. That rule is the one that protects your credibility. We exercised it with our own invocation prompt, playing a fictional operations consultant. In a short topic interview about cutting month-end close time, the agent asked one question at a time, pressed 'a lot faster' once and got 'from nine working days to five, over two quarters', asked what the consultant used to believe about automation, and asked which client could be named (none). The outline had five labeled lines and left the opposition line marked empty when we had nothing to offer, instead of inventing a critic. Setup is the hurdle: it lives in a coding-agent plugin, so it suits people comfortable installing one. The repository's popularity suggests plenty are.
Where the time goes back: One interview gives every future draft concrete material, so you stop rewriting generic AI posts or answering the same questions each time you write.
FAQ
Does it write the post?
Why does it ask what I got wrong?
Is it free?
Source and credit
This playbook is based on work by sergebulaev. We summarize it and link to it and write our own adapted prompt.
- Original
- linkedin-interviewer skill (sergebulaev/linkedin-skills)
- Creator
- sergebulaev
- Published on
- GitHub
- Original date
- Sep 13, 2026
- License
- MIT
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. No figures invented; skill exercised via our invocation prompt.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
The original is licensed under the MIT License (Copyright (c) 2026 Sergey Bulaev). Modified: our adapted prompt and summary are our own wording; the original is unchanged at the source link.
Are you the creator? Claim or correct this page.