linkedin-post
Skill0 starsChanged 31 days agoMITView on GitHub
Drafts LinkedIn posts in the person's own voice, learned from three to five of their past posts rather than a generic template, from a rough idea, a one-liner, notes or a longer article. Also cuts one article into two or three standalone posts. Use when someone says "write a LinkedIn post", "turn this into a LinkedIn post", "draft a post about", "make this sound like me on LinkedIn", "write a short thought", or pastes an idea and asks for a post.
44 other projects use a version of this.
Adopted by
Most recently taken up by
- Lindadao92/needle-content-skillstheir own version, first seen Nov 16, 2026
- aya-taleb/linkedin-boost-skillstheir own version, first seen Nov 16, 2026
- runehub-ai/rune-hubtheir own version, first seen Nov 15, 2026
- dmccreary/claude-skillstheir own version, first seen Nov 9, 2026
- dmccreary/ibook-skillstheir own version, first seen Nov 8, 2026
- olivMertens/copilot-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use youtube-upload, proposal-writer and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
BlackLotus1974Skillyoutube-upload
Upload videos to Atchalta's YouTube channel (office@atchalta.com). Use when the user asks to upload a video to YouTube, list YouTube videos, manage playlists, or update video metadata. Trigger phrases: 'upload to youtube', 'youtube video', 'publish video', 'post to youtube', 'list my videos', 'youtube playlists'.
Also in 3 projects that use this
ncklrsSkillproposal-writer
Expert sales proposal and pricing presentation strategist. Use when writing proposals, executive summaries, ROI business cases, pricing presentations, SOWs (Statement of Work), RFP responses, or competitive positioning documents. Covers proposal structure, terms positioning, design formatting, follow-up strategy, and win-rate optimization.
Also in 3 projects that use this
Microsoft AzureSkilllint
Run all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.
Also in 3 projects that use this
OpenAISkillbrainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Also in 3 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
Other versions44 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 44
- langchain-ai/langgraph-101★ 708same name
- hamzafarooq/claude-code-starter★ 145same name
- dmccreary/ibook-skills★ 112same name
- dmccreary/claude-skills★ 110same name
- kevinbadi/ai-os-skills★ 69same name
- publora/skills★ 68same name
- az9713/ai-co-writing-claude-skills★ 61same name
- JamsusMaximus/growth-agents★ 21same name
- langchain-ai/langgraph-101-ts★ 19same name
- duncan-buildroom/profit-room-skills★ 18same name
34 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- ai-search-visibilitySkill
- content-atomisationSkill
- keyword-researchSkill
- seo-schema-gateSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 13 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 38 edited versions we read keep these.
13
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Look for, in this order:
- Distinctive: line 24
If there is nothing, ask once: "Paste three to five posts you have written that sound like you, and I will match them." If they would …
- Distinctive: line 38
Every post makes one point.
- Distinctive: line 46
If the brief is vague, ask one question: "What is the single point, and is it a claim, a number or a story?"
- Distinctive: line 57
Default to the tier the person's own posts mostly use.
- Distinctive: line 82
No engagement bait ("Agree?", "Thoughts?", "What do you think?").
- Distinctive: line 83
No hashtags unless the person uses them.
- Distinctive: line 84
No emoji unless the person uses them.
- Very specific: line 86
Read references/hooks.md for opening patterns that work and ones to drop.
- Distinctive: line 103
If they ask for alternatives, give a second version with a different opening line only.
- Distinctive: line 107
When the input is an article or long piece and the person wants several posts:
- Distinctive: line 126
Ask for an explicit yes to that exact text.
- Distinctive: line 127
Only then post or schedule, and report back the link or scheduled time.
- Distinctive: line 129
Never publish on an ambiguous "post it" without that confirmation.
“Common” is measured: kept by at least 6 in 10 of the 38 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
LinkedIn post
Most AI-drafted LinkedIn posts sound the same: a one-word hook, a line break after every sentence, a lesson, a question at the end. People scroll past them because they recognise the shape.
This skill writes in the person's voice. It learns that voice from their own posts, records it as a short profile, and checks every draft against it.
Step 1: get the voice
Look for, in this order:
- A voice profile already in the conversation or project (from an earlier run).
- Three to five of their past LinkedIn posts, pasted or in a file. Ask for ones they are happy with, ideally a mix of short and long.
- Other writing of theirs: blog posts, newsletters, emails.
If there is nothing, ask once: "Paste three to five posts you have written that sound like you, and I will match them." If they would rather not, write in a plain, direct default (short sentences, concrete detail, no hype) and say that is what you did.
Build a voice profile from the samples. Read references/voice-profile.md for the
method and the template. It takes a minute and covers: typical length, how posts open, line
and paragraph rhythm, vocabulary and words they never use, how they handle numbers and
names, tone, how posts end, and formatting habits (emoji, hashtags, lists, dashes).
Show the profile in five to eight lines and offer to save it so the next run can skip this step. Never copy sentences from the samples into new drafts.
Step 2: find the one point
Every post makes one point. From the person's idea, notes or article, write down:
- The point, in one sentence.
- The proof: the number, story, example or before-and-after that makes it believable.
It must come from the person. Never invent a statistic, client, result or anecdote; if
the post needs one, ask, or leave
[ADD: ...]. - Who it is for, if it is not obvious.
If the brief is vague, ask one question: "What is the single point, and is it a claim, a number or a story?"
Step 3: pick a length
| Tier | Words | Use for |
| Short | 40 to 120 | One observation, one sharp line. A "thought". |
| Medium | 150 to 250 | A story or a take with one specific number. |
| Long | 300 to 450 | A real multi-step argument or how-to. |
Default to the tier the person's own posts mostly use. If they have no samples, default to short. LinkedIn shows roughly the first 200 characters before "see more", so whatever the length, the opening line has to earn the click.
Step 4: draft
Shape:
Opening line: the point, a specific number, or the most surprising detail.
One or two lines that set it up, only if needed.
The body: the proof, in their rhythm.
The landing: one line the reader could repeat.
Optional: one question or call to action, only if their posts usually have one.Apply the profile, then these defaults unless the profile says otherwise:
- The point in the first line. No warm-up.
- Concrete over abstract: names, numbers, places, prices.
- One idea. If two ideas compete, offer to split them into two posts.
- No engagement bait ("Agree?", "Thoughts?", "What do you think?").
- No hashtags unless the person uses them; if they do, three at most at the end.
- No emoji unless the person uses them.
Read references/hooks.md for opening patterns that work and ones to drop.
Step 5: check before showing
- Reads like their samples, not like a template. Read it against two of them.
- One point, stated in the opening line.
- Every fact, number and anecdote came from the person. Do not invent what customers
did or said ("most never opened it") to fill a gap; mark it
[ADD: ...]. - Within the chosen length.
- No phrase from the "drop" list in
references/hooks.md. - Spelling and punctuation follow their locale and habits.
Output
One draft, not three. Print it ready to paste. Under it, one line: tier, word count, and
anything marked [ADD: ...].
If they ask for alternatives, give a second version with a different opening line only.
Cut mode: one article, several posts
When the input is an article or long piece and the person wants several posts:
- Find the genuinely distinct points. Two or three is typical.
- Each post stands alone: no "part 1", no "link in comments for the rest", no teaser that holds back the payoff.
- Different angles, not the same point reworded. If the article has one real point, write one post and say so.
- Short or medium tier for each.
- Number them and suggest spacing them at least a few days apart.
The content-atomisation skill in this plugin plans the wider multi-channel version.
Publishing
This skill drafts. It does not post. If the person has a LinkedIn or social scheduling tool connected and asks to publish:
- Show the exact final text and the target (personal profile or company page). Ask which if they did not say.
- Ask for an explicit yes to that exact text.
- Only then post or schedule, and report back the link or scheduled time.
Never publish on an ambiguous "post it" without that confirmation.
Example
User: Post about how we stopped doing discovery calls for orders under 500 pounds. Here are three of my old posts: (pasted)
Claude: Your profile: short posts (80 to 120 words), open with a plain statement of what you did, no questions at the end, British spelling, numbers written as figures, occasional dry aside in brackets, never uses hashtags.
We stopped doing discovery calls for orders under £500.
They were taking 40 minutes each. Most ended with the client picking the package they had already looked at on the website.
Now small orders go straight to a short form and a booking link. Bigger jobs still get a call (those are the ones where the call changes the answer).
[ADD: what happened to conversion or time saved]
The call was for us, not for them.
Short tier, 78 words. Needs one result from you where marked.
Configuration
Two things vary per person:
- Their voice samples or saved profile. The skill is only as close to their voice as the samples it learned from.
- Locale. British or American spelling, currency and date format. Take it from their samples if not stated.
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.

