linkedin-hooks
Skill0 starsChanged 32 days agoMITView on GitHub
Writes LinkedIn post hooks (the first one or two lines) aimed at a specific buyer and offer. Two modes: build a hook library across hook types for an ICP, or write 10 hooks for one post you are about to publish and refine the pick. Uses real buyer language from call notes when available. Triggers: "LinkedIn hooks", "hook library", "generate hooks", "hook ideas", "hooks for this post", "opening line for", "first line for my post". Feeds the post skills in this plugin.
In this repository7 other files it gives its agents.
- linkedin-carouselsSkill
- linkedin-commentSkill
- linkedin-content-auditSkill
- linkedin-expert-postsSkill
- linkedin-personal-postsSkill
- linkedin-profileSkill
- linkedin-weekly-contentSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Write the first lines of LinkedIn posts.
- Very specific: line 17
Not for writing the full post.
- Distinctive: line 31
If the ICP is missing, ask for a one-line description of the buyer and their top 3 to 5 pains before writing.
- Distinctive: line 37
Use these as starting shapes, not fill-in templates.
- Distinctive: line 54
Gather context: Read the ICP, offer, voice and any call notes.
- Distinctive: line 68
Use specific numbers when you have real ones.
- Distinctive: line 69
Keep the first sentence short: 5 to 12 words.
- Very specific: line 71
Use the buyer's vocabulary from context/icp/ or call notes, not industry jargon.
- Distinctive: line 72
If a hook is a question, the answer must not be obvious.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
LinkedIn hooks
Write the first lines of LinkedIn posts. On LinkedIn the hook is the post: readers decide in the two lines before "see more" whether to keep going. A hook that names the reader's problem in their own words beats a clever one.
When to use it
- Library mode: you want a stock of hooks for an ICP to draw on for weeks.
- Single-post mode: you know what the post says and need the opening.
Not for writing the full post. Hand the chosen hook to /linkedin-expert-posts, /linkedin-personal-posts or /linkedin-carousels.
Inputs
| Input | Required? | Where it comes from |
| Who the buyer is, their pains and goals | Required | context/icp/ |
| The offer | Required | context/positioning/ or the user |
| Who is posting | Required | The user |
| Voice | Recommended | the tone-of-voice file in context/brand/ |
| Proof points | Recommended | context/expert-pov/, context/win-loss/ or the user |
| Call notes or transcripts | Optional | Real buyer phrasing beats anything you write |
| Audit findings | Optional | /linkedin-content-audit shows which hook types work for this audience |
If the ICP is missing, ask for a one-line description of the buyer and their top 3 to 5 pains before writing. Name what was missing in the output.
Agency users: swap context/ for clients/<client>/context/.
Hook types
Use these as starting shapes, not fill-in templates.
| Type | What it does |
| Pain mirror | Says the problem the way the buyer says it to themselves |
| Bold claim | States a position the reader may disagree with |
| Contrarian | Challenges something the audience takes for granted |
| Number or result | Leads with a specific, real figure |
| Mistake | Names a common error and its cost |
| Story opening | Drops the reader into a moment ("Last Tuesday a founder told me...") |
| Question | Asks the question the reader is already asking, where the answer is not obvious |
| List promise | Promises a short, specific set ("3 things I check before...") |
| Before and after | Shows the gap between where the reader is and where they want to be |
| Behind the scenes | Shows how something was actually done |
Steps: library mode
- Gather context. Read the ICP, offer, voice and any call notes. Produces: 3 to 5 buyer pains in the buyer's words, plus available proof.
- Score the hook types. Rate each type high, medium or low for this buyer and offer. Produces: a short scoring table.
- Write hooks. Two or three per high-scoring type, one per medium type, none for low. Produces: 20 to 40 hooks grouped by type.
- Rank. Pick the top 5 and say in one line why each works. Produces: the top-5 list.
Steps: single-post mode
- Name the one thing. What does the reader get from this post, in one line? Produces: the post's point.
- Fix the proof and the reader. One real proof point and the specific reader (role, stage, situation). Produces: the two anchors every hook carries.
- Write 10 hooks across at least five different types, each two lines at most, with a character count. Produces: 10 numbered hooks.
- The user picks one. Then write 3 variations of it: shorter, more energy, a different detail. Produces: the final hook.
Writing rules
- Use specific numbers when you have real ones. Never invent them.
- Keep the first sentence short: 5 to 12 words.
- Aim for one emotion: curiosity, worry, desire or surprise.
- Use the buyer's vocabulary from
context/icp/or call notes, not industry jargon. - If a hook is a question, the answer must not be obvious.
- No "link in the comments" or "link below" promises.
What good looks like
- Each hook could only have been written for this buyer.
- A reader in the ICP would recognise their own problem in the first line.
- Proof in the hook is real and traceable.
- The set covers several hook types, not ten versions of one.
Mistakes to avoid
- Generic openers that fit any post in any industry.
- "Most people think X, but actually Y" without anything specific in it.
- "It's not about X. It's about Y." false contrasts.
- Three short parallel sentences in a row.
- Engagement-bait ("Agree?", "Thoughts?") or emoji decoration.
- Invented stories. Mark
[needs real story]if none was given.
Output
Library mode: save to outputs/social/linkedin/MMYY-hook-library.md with the scoring table, hooks by type, and the top 5 with reasons.
Single-post mode: return the 10 hooks, the pick and its 3 variations in the chat, ready to paste into the post skill.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.