Skip to content

borghei/Claude-Skills / tools/linkedin/linkedin-post-writer

linkedin-post-writer

Verified

Drafts LinkedIn posts from a brief: picks an angle and opening pattern the author's real material supports, structures the body, and gates the draft before it is pasted. Use when writing a post, choosing a hook, or checking a draft before publishing.

references/opening-patterns.md

View on GitHub
# Opening Patterns

Fourteen ways to open a post, organised by the material each one requires.
`scripts/angle_picker.py` uses the same slugs.

A pattern here is a relationship between the author's material and the first
line: what goes first, what must be in it, and what the rest of the post then
owes the reader. It is not a fill-in sentence. Two openings built on the same
pattern should not sound alike.

All example lines are invented, about fictional people and companies. Goal-fit
notes are editorial heuristics. Where a platform behaviour is mentioned (the
truncation point, for instance) it is current as of writing and should be
verified in the product.

## Contents

1. What every opening has to do
2. The fourteen patterns
3. Four openings to avoid
4. Choosing between two patterns that both fit
5. Writing the line
6. Testing an opening

---

## 1. What every opening has to do

The feed shows the first line or two and cuts the rest behind an expand
control. Three things follow.

1. **The point goes in the first clause.** Not after a subordinate clause, not
   after "For three years I believed that". If the cut lands mid-sentence, the
   reader should already have the figure, the date or the claim.
2. **The line must be true on its own.** It will be read by many more people
   than read the post. Whatever it asserts, the author is asserting to all of
   them.
3. **It makes a promise the body keeps.** An opening about a mistake owes the
   reader the mistake. An opening with a number owes them how it was counted.

An opening does not need to be surprising. It needs to be specific enough that
the reader can tell whether the post is for them.

---

## 2. The fourteen patterns

Each entry: what the author must have, how to build the line, an example, what
the post then owes, and how the pattern usually fails.

### receipt — Receipt line

**Needs:** one precise figure and what it counts.

**Build:** figure first, referent immediately after, then the half of the story
the reader would not guess.

> 62 person-hours. That was the weekly cost of a meeting in which, on average,
> three questions were asked.

**The post owes:** how the figure was arrived at, over what period, and what
was done about it.

**Fails when:** the figure is round and unreferenced ("We saved thousands of
hours"). Precision is the pattern; without it this is an intensifier.

### dated-error — Dated mistake

**Needs:** a date and a decision that went wrong, with a cost.

**Build:** when, what the author did, what it cost. First person, past tense,
no softening adverbs.

> On 9 June I cancelled our all-hands with two days' notice and nothing to
> replace it. It took a fortnight and one unhappy client to see why that was
> backwards.

**The post owes:** why the decision looked right at the time, and what the
author does differently now.

**Fails when:** the mistake is a disguised boast ("My mistake was caring too
much") or has no cost attached.

### cold-scene — Cold scene

**Needs:** a moment the author was present for.

**Build:** start inside it. A time or place, a person, something said or seen.
No sentence of setup before the scene.

> Twenty past four on a Friday, and the only person left in the warehouse
> office was the one printing every label by hand.

**The post owes:** what the author understood afterwards, and a practical
consequence. A scene with no consequence is a diary entry.

**Fails when:** the scene is generic ("I was sitting at my desk when it hit
me") or runs for three paragraphs before the point appears.

### belief-flip — Changed mind

**Needs:** something the author believed and no longer does, plus what ended it.

**Build:** state the old belief fairly, in terms its holders would accept, then
name the event or evidence.

> I defended our weekly all-hands for three years. Then Ines in finance told me
> she had never once asked a question in it.

**The post owes:** why the old belief was reasonable, and where it still holds.

**Fails when:** the old belief is a straw position nobody held, which turns the
pattern into a contrast frame.

### counter-position — Counter-position

**Needs:** a disagreement with a common practice, the case it applies to, and
evidence.

**Build:** name the practice, make the claim flat, limit it to a case.

> Weekly status meetings make small teams slower. I can only speak for teams
> under seventy people, but I have the before and after.

**The post owes:** the strongest form of the usual view, the evidence, and the
boundary where the usual view is right.

**Fails when:** there is no evidence or no boundary. Then it is provocation,
and the replies will say so. The picker attaches a caution in this case.

### gap — Measured gap

**Needs:** a before figure, an after figure, and the time between them, all
measured the same way.

**Build:** both numbers in the first clause, then the time span, then the cause
if it is unexpected.

> Open questions went from 3 a week to 19 in a month. All we changed was where
> people could ask them.

**The post owes:** the method, the changes in order of effect, and what was
tried that did nothing.

**Fails when:** one of the two numbers is missing or vague ("from almost none
to 19"), or the units differ.

### borrowed-line — Borrowed line

**Needs:** someone's exact words, and permission or anonymity.

**Build:** identify the speaker by role or name, then the words, unimproved.

> "I have never once asked a question in that meeting and I have asked four
> this week." Ines, who runs our finance team, in a thread on a Tuesday.

**The post owes:** the situation and what the author changed because of it.

**Fails when:** the quote is from a famous person (it is then a quotation, not
a story) or has been polished until nobody would have said it.

### house-rule — House rule

**Needs:** a rule the author or team keeps, and the incident that created it.

**Build:** the rule as a rule, short enough to repeat, then a pointer to the
incident.

> Our rule: no meeting recurs for more than eight weeks without someone arguing
> for it. It dates from the Monday we counted the hours.

**The post owes:** the incident, how the rule works day to day, and what it
costs.

**Fails when:** the rule is an aspiration ("We always put the customer first").
A rule can be broken on a specific day; a value cannot.

### field-count — Field count

**Needs:** a number of things examined, and a pattern among them.

**Build:** what was examined, how many, and the count inside the count.

> I read every question asked in our all-hands for a year. There were 148.
> Four people asked 131 of them.

**The post owes:** how the sample was chosen and where it is weak.

**Fails when:** the sample is asserted, not counted ("I've seen hundreds of
teams").

### asked-question — Reported question

**Needs:** a question the author was really asked.

**Build:** who asked, by role, and the question in their words. The line is a
statement that contains a question, which is different from asking the reader.

> A new team lead asked me last week how she was supposed to know what the
> other teams were doing now that the Monday meeting is gone.

**The post owes:** the answer, and how the author's answer has changed.

**Fails when:** the question is invented to set up a prepared answer. Readers
can usually tell, because nobody asks questions that neatly.

### credit — Named credit

**Needs:** a person and the specific thing they did.

**Build:** the name, the act, what it made possible. One person, one act.

> Maren Okafor listened to sixty onboarding calls in February and wrote down
> the minute each customer went quiet. Everything we fixed this quarter came
> from that list.

**The post owes:** the situation before, the act in detail, the result.

**Fails when:** it becomes a roll-call of tagged names, or the praise is
general ("an amazing colleague").

### plain-definition — Plain definition

**Needs:** a term the audience uses without being able to define.

**Build:** the term, then the everyday version in one sentence.

> "Alignment" in a sixty-person company means: can any two people describe this
> week's priority the same way without checking?

**The post owes:** a worked example, the common misuse, and when the term is
not worth using.

**Fails when:** the definition is another abstraction, or the tone talks down
to people who use the word professionally.

### dated-bet — Dated bet

**Needs:** an expectation, a date, and what would prove it wrong.

**Build:** the claim and the date in one sentence. The falsifier can follow.

> By next summer I expect we will have no recurring company-wide meetings at
> all. If written questions drop below ten a week, I'm wrong.

**The post owes:** the evidence so far and the best reason it might not happen.

**Fails when:** there is no date or no way to be wrong. "The future of work is
asynchronous" is not a bet.

### list-promise — Counted list

**Needs:** three or more real steps, checks or items the author actually uses.

**Build:** the count, the kind of thing, and the context that makes it worth
reading.

> Three things replaced our Monday all-hands. The third is the only one that
> involves a call.

**The post owes:** one line per item, each with its own detail, and honesty
about the weakest one.

**Fails when:** the items are interchangeable advice. If an item could appear in
anyone's list, cut it and lower the count.

---

## 3. Four openings to avoid

The picker never offers these, and `scripts/post_gate.py` flags or blocks them.

| Opening | Example | Problem | Replace with |
|---------|---------|---------|--------------|
| Question to the reader | "Ever feel like your meetings could be an email?" | Asks for agreement before offering anything; the honest answer is usually "yes, and?" | The fact that prompted the question |
| Announcement of a feeling | "I'm thrilled to share…" | The feeling is not the news | The news, in the first clause |
| Teaser | "This changed everything." | Withholds the subject, so the reader cannot tell if the post is for them | The thing that changed, named |
| Command | "Stop holding weekly all-hands." | An instruction before a reason | The reason; let the reader draw the instruction |

Each has a legitimate cousin among the fourteen. A question becomes a reported
question. An announcement becomes a receipt line or a dated bet. A teaser
becomes a cold scene. A command becomes a house rule or a counter-position.
The difference in every case is that the legitimate version contains a fact.

---

## 4. Choosing between two patterns that both fit

The picker will often rank several patterns equally. Break the tie in this
order.

1. **Which material is the author most willing to stand behind in public?** A
   dated mistake outranks a receipt line on paper for conversation, but not if
   the author will flinch at the replies.
2. **Which opening needs the least setup?** If one option requires a sentence
   of context before it makes sense, prefer the other.
3. **Which has the author not used recently?** Three measured-gap posts in a
   row turn a pattern into a tic.
4. **Which leaves the best material for the body?** Opening on the strongest
   fact can leave nothing to reveal. Sometimes the second-strongest fact opens
   and the strongest lands in paragraph three.

Material from the patterns that lose the tie is not wasted. In the sample brief
the figure, the quote and the before-and-after all appear in the body of a post
that opens on the dated mistake.

---

## 5. Writing the line

- **Front-load.** Put the figure, date or name in the first six words where
  the sentence allows it.
- **Use the author's own noun.** "All-hands", not "synchronous alignment
  ritual".
- **Past tense for things that happened.** Present tense for rules and
  definitions.
- **No preface.** Delete "So,", "Quick story:", "A thought:", "Let me tell you
  about".
- **No adjectives doing the work of facts.** "A painful lesson" tells the
  reader how to feel; "it cost us a client" lets them.
- **One sentence or two.** If two, the second must fit before the cut as well,
  or be worth expanding for.
- **Sentence case.** Capitals for emphasis read as shouting and the gate
  blocks an all-capitals opening.

Draft at least three versions of the opening from the chosen pattern, varying
which element comes first. Offer the author two.

---

## 6. Testing an opening

Before settling on a line, check it against these.

- [ ] Covered at the truncation point, does what remains still contain the
      figure, date, name or claim?
- [ ] Could a reader decide from this line alone whether the post concerns them?
- [ ] Is every word in it true and checkable against the brief?
- [ ] Could it be moved to the top of a different author's post unchanged? If
      yes, it is not specific enough.
- [ ] Does the body deliver what the line promises, within three paragraphs?
- [ ] Would the author say it aloud to a colleague without embarrassment?
- [ ] Does `post_gate.py` pass the opening checks (PG-01 to PG-05)?
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