ericrisco/rsc-harness / skills/linkedin-content
linkedin-content
VerifiedUse when writing the actual words of one LinkedIn feed post — turning a raw idea, story or asset into ready-to-paste copy: a text post, a document/carousel cover with slide copy and caption, or a short native-video script. Covers fixing a weak hook, reformatting a wall of text for the mobile feed, and a CTA that provokes a real comment. NOT planning what or when to post (that is `linkedin-strategy`), NOT designing the carousel slides and PDF export (that is `linkedin-carousels`), NOT DM sequences (that is `linkedin-outreach`), NOT programmatic publishing (that is `linkedin-api`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.7 KB |
| evals/README.md | markdown | 950 B |
| evals/cases.yaml | config | 4.0 KB |
| references/hooks-and-formats.md | markdown | 5.3 KB |
| scripts/verify.shexecutable | script | 5.8 KB |
references/hooks-and-formats.md
View on GitHub# Hooks, format templates, and the 02-DOCS post log
Depth offloaded from `SKILL.md`. Use this when you need the full hook library, a
fill-in template for any of the three formats, or the schema for logging posts and
reading outcomes back. Every char budget and engagement figure traces to the keyed
sources `[S1]`–`[S4]` listed in `SKILL.md` ("Sources" section, all accessed
2026-06-02); the multipliers there are flagged as directional, not confirmed.
## Hook pattern library
The hook lives in the first ~150 characters — the visible zone before *see more*.
Pick the pattern that fits the idea; each one front-loads tension or specificity so
the eye keeps moving.
| # | Pattern | Shape | Bad | Good |
|---|---|---|---|---|
| 1 | Number-lead | A surprising metric first | "We grew a lot last year." | "We added $1.2M ARR with zero paid ads. Here's the only channel that worked." |
| 2 | False-start | Admit the thing people won't | "Some lessons on hiring." | "I hired for culture fit for 5 years. It was the most expensive mistake I made." |
| 3 | Contrarian | Reject the consensus | "Networking is important." | "Networking events are a waste of time. I closed our biggest deal in a DM." |
| 4 | Open-loop | Promise an answer, withhold it | "Here's how we handle churn." | "One churned customer's exit interview changed our whole roadmap. I almost deleted the email." |
| 5 | Named-stakes | Put a real cost on the line | "Thoughts on pricing." | "We raised prices 40% expecting churn. We lost 2 customers and gained $300k." |
| 6 | Before→after | Two states, sharp delta | "Onboarding improved." | "Onboarding took 3 weeks. Now it takes 3 days. The change was one deleted step." |
| 7 | Confession | A mistake you own | "Mistakes were made." | "I ghosted a candidate for 6 weeks. He's now a competitor's VP. Here's what I'd do differently." |
| 8 | Pattern-callout | Name a thing everyone does | "Meetings can be inefficient." | "Every 'quick sync' on your calendar is a decision someone was afraid to make alone." |
| 9 | Question-trap | A question the reader can't not answer | "Do you struggle with focus?" | "When did 'busy' become the answer to 'how are you?' I want to opt out." |
| 10 | Receipt | Lead with proof | "Our product helps teams." | "47 support tickets in one week, all the same complaint. We rebuilt the feature in a sprint." |
Rule across all ten: the first line must be readable and complete on its own line on
mobile — do not let a thought run past the truncation point mid-clause.
## Text post template (1,300–1,900 chars)
```text
[HOOK — ~150 chars, one of the 10 patterns. First line readable alone.]
[Second line escalates the hook.]
[TURN — ~300–400 chars. The pivot: the non-obvious thing.
1–2 sentence paragraphs, blank line between blocks.]
[PAYOFF — ~600–900 chars. The story/lesson/proof the hook promised.
One idea per line. Use → or ▸ as occasional bullets, not confetti.
Unicode emphasis on at most one or two phrases.]
[CTA — ~100–200 chars. A question only the reader can answer.
Never "thoughts?".]
[No link. No "link in comments". If a link is unavoidable, decide knowingly.]
```
## Document / PDF post template (3–10 slides)
```text
COVER (slide 1):
[Hook line, large, thumbnail-readable — does the see-more job here too.]
SLIDES 2–N (3–10 total):
Slide 2: [One idea. Ends pulling the swipe.]
Slide 3: [One idea.]
...
Slide N: [Payoff + the single takeaway.]
CAPTION (100–200 words):
[Frame the deck in the text-post arc, miniaturized.]
[End on a comment-earning CTA.]
```
Hand the slide *text* to `../linkedin-carousels/SKILL.md` for layout, visual system,
and PDF export. You write words; that skill renders pixels.
## Native-video template (30–90s)
```text
SCRIPT BEATS:
0–3s HOOK (visual + spoken; most viewers are muted, so the on-screen
text must carry it alone).
3–15s TURN — the non-obvious pivot.
15–75s PAYOFF — story/proof, escalating.
last SPOKEN CTA — one answerable question.
CAPTION (text-post arc in miniature):
[Hook line + 2–4 short lines + comment-CTA. No body link.]
```
Sub-60s short-form gets ~53% more engagement than longer; 30–90s is the band. For a
cross-platform vertical short (Reels/TikTok/Shorts), route to `../video-shorts/SKILL.md`.
## The 02-DOCS post log
Log every published post so the next draft can learn. One markdown file per post (or
a single appended log), front-matter first:
```yaml
---
date: 2026-06-02 # publish date
format: text # text | document | video
hook: "We almost shut the product down in March."
hook_pattern: confession # one of the 10 patterns above
cta_type: experience-ask # experience-ask | disagreement-ask | number-ask
char_count: 1640
# --- filled in later, once metrics land ---
impressions: 0
dwell_s: 0 # avg dwell in seconds (the currency)
comments: 0
saves: 0
---
[the full post body, for reference]
```
**Reading it back to bias drafts:** before writing, scan the log and sort by
`dwell_s` and `comments` (the weighted signals), not impressions. Note which
`hook_pattern`, `format`, and `cta_type` recur among the top performers *for this
account*, and lean the new draft toward them. A pattern that wins generically but
flops for this audience loses to one that wins here. After publishing, append the new
row; fill metrics in when they stabilize (~48–72h).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |