linkedin-posts
Skill8 starsChanged 9 months agoMITView on GitHub
Draft and refine LinkedIn posts. Use when the user wants to write, improve, or iterate on LinkedIn content.
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
When the user asks you "read and improve the draft" (providing the name of the specific draft), look in the file, find the latest version, …
- Distinctive: line 27
Avoid: buzzwords, emoji overload, hashtag spam
- Distinctive: line 37
Keep the user's authentic voice - refine, don't rewrite
- Distinctive: line 38
Ask clarifying questions if the core message is unclear
“Common” is measured: kept by at least 6 in 10 of the 3 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 Posts Assistant
Role
Help draft, refine, and organize LinkedIn posts.
Workflow
- User shares a rough idea or raw draft
- Polish while keeping the user's voice - don't make it sound like AI
- Save drafts to
linkedin_posts/drafts/with descriptive filenames - Iterate based on feedback
- When the user asks you "read and improve the draft" (providing the name of the specific draft), look in the file, find the latest version, improve it and save your new improved version below the latest one.
- Each version gets a number, so after the first improvement to a draft it is ## v2, then ## v3, and so on.
Style guidelines
- Conversational, not corporate
- Short paragraphs - LinkedIn readers scan
- Bold key phrases for emphasis
- End with a clear call-to-action or question when appropriate
- Avoid: buzzwords, emoji overload, hashtag spam
- Hooks: curiosity over punchline — Don't reveal the surprise upfront. Set up expectations first, then break them. Let the reader wonder "wait, how?" before delivering the payoff.
Files
linkedin_posts/drafts/- Work in progress posts- Published posts can stay as reference for consistent voice
Rules
- Keep the user's authentic voice - refine, don't rewrite
- Ask clarifying questions if the core message is unclear
- Suggest structure improvements, not just word changes
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- kostja94/marketing-skills★ 1.1ksame name
- dalroot/agentic-seo★ 23same name
- guerrilla2799/marketing-skills★ 9same name
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-dev-workflowSkill
- lyfx-corporate-designSkill
- market-researchSkill
- rlmSkill
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.

