borghei/Claude-Skills / tools/linkedin/linkedin-story-interviewer
linkedin-story-interviewer
VerifiedInterviews 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.1 KB |
| assets/draft_seed_template.md | markdown | 2.7 KB |
| assets/interview_session_template.md | markdown | 2.9 KB |
| assets/sample_story_bank.json | config | 5.8 KB |
| assets/story_bank_template.json | config | 1.8 KB |
| references/interview-method.md | markdown | 10.2 KB |
| references/question-sets.md | markdown | 9.3 KB |
| references/story-bank-format.md | markdown | 10.0 KB |
| scripts/story_bank_audit.py | script | 14.7 KB |
| scripts/story_bank_rules.py | script | 9.1 KB |
assets/draft_seed_template.md
View on GitHub# Draft Seed
The output of a single-post session. Six slots, each holding only what the
person said. A slot with nothing real in it reads `not gathered` and stays
that way: whoever drafts from this must be able to tell material from absence.
| Field | Value |
|-------|-------|
| Person | |
| Date gathered | |
| Topic in their words | |
| Pillar | |
| Bank entries drawn on (ids) | |
| Naming for this post | clear / ask (who?) / anonymise |
| No-go subjects that sit near this topic | |
## 1. What happened
The occasion: a day, a place, who was there, what was done. One short
paragraph of facts.
>
Date of the event:
## 2. What it cost or earned
One figure, what it counts, how it is known. If there is no figure, write
`not gathered`.
- Figure:
- Counts:
- Known from:
## 3. What I thought before
The belief held going in, as one sentence in the person's voice.
>
## 4. What I think now
The belief held coming out, and the thing that caused the change.
>
Cause of the change:
## 5. Who this is for
- The reader who needs it:
- The reader who would disagree, and what they would say:
## 6. What to try
One thing the reader could do differently next week. Not a list.
>
## Their wording
Lines recorded verbatim that the draft should try to keep.
-
-
## Read-back
- [ ] Seed read back to the person
- [ ] Their corrections applied above
- [ ] Empty slots confirmed as empty, not skipped
- [ ] New concrete material added to the story bank
Slots left `not gathered`, and why:
-
## Example of a filled seed (fictional)
| Field | Value |
|-------|-------|
| Person | Odalys Venter |
| Topic in their words | "Why I stopped asking for a route optimiser" |
| Pillar | ops-craft |
| Bank entries drawn on | S-004, S-002 |
| Naming for this post | clear |
1. **What happened.** In January 2022 she spent a week riding in truck 22
from the Tilbrook depot. The truck was on the road on time every day and
late out of the yard every day.
2. **What it cost or earned.** 37 spoilage claims in the first half of 2024,
11 in the second half, after door-open time was capped at 6 minutes per
load. Counts customer claims across three depots; known from the finance
claims ledger.
3. **What I thought before.** "The route is where the minutes are lost."
4. **What I think now.** "The dock is where the minutes are lost; the route
only shows it." Cause: seeing the same driver wait at the same door five
mornings running.
5. **Who this is for.** Operations leads about to buy planning software.
Disagreeing reader: anyone who sells or champions route optimisation, who
would say both problems are real.
6. **What to try.** Time one dock door for one week before buying anything.
Their wording: "I had been optimising the part I could see on a map."
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| 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: 194k | Updated | Claude CodeCodex | Verified | Install |