borghei/Claude-Skills / tools/linkedin/linkedin-post-writer
linkedin-post-writer
VerifiedDrafts 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.3 KB |
| assets/post_brief_template.md | markdown | 4.2 KB |
| assets/sample_brief.json | config | 1.3 KB |
| assets/sample_draft.txt | markdown | 1.2 KB |
| assets/sample_draft_revised.txt | markdown | 1.1 KB |
| references/opening-patterns.md | markdown | 12.8 KB |
| references/post-structures.md | markdown | 11.4 KB |
| references/pre-publish-gate.md | markdown | 10.2 KB |
| scripts/angle_picker.py | script | 13.1 KB |
| scripts/post_gate.py | script | 12.7 KB |
references/post-structures.md
View on GitHub# Post Structures
What comes after the opening: the second line, the body beats for each
pattern, the close, length and layout. Ends with a full worked draft from
`assets/sample_brief.json`.
Length bands and goal mappings are editorial heuristics. Platform limits are
current as of writing; verify in the product. Examples are invented.
## Contents
1. The anatomy of a post
2. The second line
3. Body beats by pattern
4. The part that did not work
5. Closes by goal
6. Length
7. Layout
8. Worked draft
9. Variations for common situations
---
## 1. The anatomy of a post
| Part | Job | Typical size |
|------|-----|--------------|
| Opening | State the most specific true thing; let the reader self-select | 1 or 2 sentences |
| Second line | Add the stake, so that expanding feels worthwhile | 1 sentence |
| Body | Deliver what the opening promised, one beat per paragraph | 3 to 6 short paragraphs |
| Turn | The cost, exception or unsolved part | 1 paragraph |
| Close | A specific question, the last fact, or nothing | 1 line |
| Labels | Zero to three hashtags, if any | Last line |
A beat is one thing the reader learns. Each beat needs a fact from the brief.
A paragraph with no fact is restating a previous one and can go.
---
## 2. The second line
If the opening is one line, the second line is often the last thing visible
before the cut. It has one job: make the reader want the rest. Three ways to do
that honestly.
| Move | Example after "On 9 June we cancelled our weekly all-hands with two days' notice and nothing to replace it." |
|------|-------------|
| Name the stake | "The second half of that sentence was the mistake." |
| Add the number | "It had been costing us 62 person-hours a week." |
| Add the consequence | "Twelve days later two teams shipped conflicting changes to the same page." |
Three things the second line must not do:
- **Restate the opening** in other words.
- **Withhold** ("Here's what happened next"). The opening already earned
attention; teasing spends it.
- **Generalise** ("Communication is hard"). The post just got specific; stay
there.
---
## 3. Body beats by pattern
The picker prints these in order. They are a default sequence; drop any beat
the author has no fact for, and never pad one to keep the count.
| Pattern | Beat 1 | Beat 2 | Beat 3 | Beat 4 |
|---------|--------|--------|--------|--------|
| receipt | What the figure counts, and over what period | The one change behind it | What did not move | What is unsolved |
| dated-error | The decision as it looked then | The moment it showed | What changed, and when | What the author would do first now |
| cold-scene | Two more beats of the scene | What was understood afterwards | The practical change | |
| belief-flip | Why the old belief was reasonable | The evidence that broke it | The new working rule | Where the old belief still holds |
| counter-position | The strongest version of the usual view | The evidence against | The boundary | What to do instead |
| gap | How it was measured | The changes, in order of effect | What was tried and did nothing | The cost of getting there |
| borrowed-line | The situation in which it was said | Why it landed | What changed because of it | |
| house-rule | The incident | How the rule works day to day | The exception allowed | What it costs to keep |
| field-count | How the sample was chosen, and its limits | The pattern, with its count | The surprising exception | What the author now recommends |
| asked-question | The short answer | The reasoning | What the author got wrong when first answering | |
| credit | The situation before | Exactly what the person did | The result | |
| plain-definition | The everyday version | One worked example with real numbers | The common misuse | When the term is not worth using |
| dated-bet | The evidence so far | The strongest reason it might not happen | What the author is doing differently | |
| list-promise | One line per item, each with its own detail | The item most people skip | The item the author is least sure of | |
### Writing a beat
1. Start the paragraph with the fact.
2. Add at most one sentence of explanation or reaction.
3. Stop. Do not write a sentence that summarises the paragraph.
If a beat needs a list (the three replacement steps, the two changes), use a
plain numbered list with full sentences. Keep lists to the items that are
really parallel.
---
## 4. The part that did not work
Every pattern above has at least one beat that is a cost, a limit or an open
question: "what did not move", "where the old belief still holds", "what it
costs to keep". These are the beats authors most often cut, and the ones that
make the rest believable.
Rules for the turn:
- **Same precision as the wins.** "Two teams shipped conflicting changes to the
pricing page" matches "19 questions a week". "There were some teething
problems" does not.
- **Stated, not performed.** No "I'll be honest" in front of it. The fact is
the candour.
- **Not resolved for the sake of a tidy ending.** If accounts with a second
warehouse still stall and nobody knows why, the post can say so and stop.
- **Never someone else's failure.** If the cost fell on a colleague or a
client, describe it by role, or leave it out.
If the author cannot name anything that went wrong, ask once more with a
narrower question ("what would you warn someone about before they copied
this?"). If the answer is still nothing, write the post without a turn and
keep it short.
---
## 5. Closes by goal
The close is chosen by the goal in the brief.
| Goal | Close | Example | Avoid |
|------|-------|---------|-------|
| Conversation | A question only someone who has done the thing can answer | "If you've replaced a standing meeting with writing, what broke in the first two weeks?" | "What do you think?" |
| Saves | The most reusable line, stated plainly, or the list's last item | "The template is three headings: shipped, blocked, need from others." | "Save this for later" |
| Reshares | End on the person credited or the claim, with no ask | "That list was Maren's." | "Repost if you agree" |
| Inbound | One sentence on what the author is working on next, no pitch | "Next we're trying the same thing with the quarterly review." | "DM me to learn more" |
A postscript is a legitimate close when there is a real afterthought: a
correction, a thank-you, a pointer to where the template lives. One line. It is
not a second call to action.
When in doubt, end on the last fact. A post is allowed to stop.
---
## 6. Length
| Band | Characters | Use for |
|------|-----------|---------|
| Short | 250 to 600 | A single fact and its consequence; a credit; an announcement |
| Standard | 600 to 1,400 | Most posts: an opening, three or four beats, a turn, a close |
| Long | 1,400 to 2,600 | A counted list with detail on each item; a case with method and numbers |
The platform limit is 3,000 characters as of writing. The bands stop well short
of it because a post that needs the full allowance is usually an article.
Length follows facts. To check whether a draft is the right length, delete each
paragraph in turn and ask whether a reader would miss anything they did not
already know. If not, it stays deleted.
Do not pad a short post to reach a band, and do not cut facts from a long one
to fit. If the author asked for a length, their request wins over the default.
---
## 7. Layout
- **One idea per paragraph, blank line between paragraphs.** This is how the
feed is read on a phone. It is layout, not a writing style: the sentences
inside can be as long as they need to be.
- **No paragraph over about 70 words.** The gate warns above that.
- **No runs of one-line paragraphs for effect.** Three in a row reads as
staged. Two-sentence paragraphs are the workhorse.
- **Plain text only.** As of writing the composer shows markdown characters
literally. No asterisks, no pound-sign headings.
- **Numbers as numerals** when they are data (19 questions, 62 hours); words
when they are prose (three years, two teams). Be consistent within a post.
- **Emoji only where the author uses them.** Never as bullets or headings.
- **Hashtags last**, on their own line, at most three.
- **Names:** full name on first mention if the person has agreed to be named;
role only if not.
---
## 8. Worked draft
Brief: `assets/sample_brief.json`. Author: a fictional COO. Goal: conversation.
### 8.1 What the picker returned
Three options tied at the top: dated mistake, changed mind, borrowed line.
Tie-break (opening-patterns §4): the author was willing to own the mistake, it
needs no setup, and it leaves the quote and both figures for the body. Dated
mistake opens.
### 8.2 First draft and what the gate said
`assets/sample_draft.txt` is a plausible first attempt. The gate fails it:
| Finding | Why it happened |
|---------|-----------------|
| Opening runs to 202 characters | It starts with the belief ("For three years I believed that…") and the date arrives in paragraph two |
| One paragraph of 106 words | Method, failure and replacement all in one block |
| `[link]` left in | Placeholder from the outline |
| "What do you think?" | No specific question had been written |
| Six hashtags | Added out of habit |
### 8.3 Revision
`assets/sample_draft_revised.txt`, beat by beat:
| Lines | Part | Source in the brief |
|-------|------|---------------------|
| "On 9 June we cancelled…nothing to replace it." | Opening: dated mistake | `dated_event` |
| "The second half of that sentence was the mistake." | Second line: names the stake | — |
| "I'd defended that meeting for three years…same four people." | Beat 1: the decision as it looked then | `changed_belief`, `figure` |
| "The first fortnight without it was worse…" | Beat 2: the moment it showed; also the turn | `must_include` |
| Numbered list of three | Beat 3: what changed | `steps` |
| "…from about 3 a week to 19." | Result | `before_after` |
| Ines's sentence | Evidence in someone else's words | `quote` |
| "I'd assumed the meeting was where alignment happened. It was where four people talked." | What the author now thinks | `changed_belief` |
| Closing question | Close for conversation | — |
The client who noticed the conflicting changes is described by role only,
because the brief lists the client's name under `must_avoid`. The revised draft
is 1,129 characters, inside the standard band, and passes the gate with no
findings.
One thing to notice: the last prose paragraph has the form "I'd assumed X. It
was Y." That is a contrast, used once, where the first half is a belief the
author really held. One is fine. A second would be a habit.
---
## 9. Variations for common situations
| Situation | Adjustment |
|-----------|------------|
| Announcement (new job, launch, funding) | Receipt line or dated bet as the opening, with the news in the first clause. Body: what it is, why now, what happens next. No story needed. Short band |
| Hiring post | Open on the work, not the vacancy: a receipt line or cold scene from the team's week. The role appears in the third paragraph. Close with how to apply, in plain words |
| Company-page post | No "I". Use field-count, gap or plain-definition, which work in the first-person plural. Named credit works well here |
| Author with one fact and little time | Short band. Opening, one beat, stop |
| Sensitive subject (redundancies, an incident) | Dated mistake or cold scene only if the author was responsible or present. No lesson-drawing in the first week. Have someone else read it first |
| Sequel to an earlier post | Open with what has changed since, as a gap or receipt line. One clause of recap at most |
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 |