linkedin-post
Skill0 starsChanged 3 months agoMITView on GitHub
Writes LinkedIn posts optimized for engagement, saves, and dwell time. Use when the user runs /linkedin-post, asks for help writing a LinkedIn post, or wants to share something on LinkedIn. Applies humanizer rules to all prose.
41 other projects use a version of this.
Adopted by
Most recently taken up by
- dmccreary/claude-skillstheir own version, first seen Nov 9, 2026
- dmccreary/ibook-skillstheir own version, first seen Nov 8, 2026
- kristian-presso/claude-marketing-skillstheir own version, first seen Nov 8, 2026
- olivMertens/copilot-skillstheir own version, first seen Nov 8, 2026
- markbaindesign/bain-studiotheir own version, first seen Nov 1, 2026
- sophonfinance-wq/finance-automation-portfoliotheir own version, first seen Nov 1, 2026
Used with
Projects with it also use proposal-writer, brainstorming and 1 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.
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
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 versions41 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 41
- langchain-ai/langgraph-101★ 708same name
- hamzafarooq/claude-code-starter★ 145same name
- dmccreary/claude-skills★ 110same name
- dmccreary/ibook-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
31 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 repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- remotion-best-practicesSkill
- add-inspirationSkill
- brandSkill
- craft-contentSkill
- draft-articleSkill
- draft-carouselSkill
- draft-diagramSkill
- draft-imagesSkill
- draft-videoSkill
- heygen-avatarSkill
- heygen-videoSkill
- humanizerSkill
- ingestSkill
- initSkill
- lintSkill
- listenSkill
- meetingSkill
- voiceSkill
- wikiSkill
- youtube-descriptionSkill
- youtube-shortSkill
- youtube-uploadSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 0 are common, 18 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 36 edited versions we read keep these.
18
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 10
Write a LinkedIn post that sounds like a person talking, not a brand broadcasting.
- Distinctive: line 19
If the user provides a story, article, video, or existing content, use that as source material instead of asking.
- Distinctive: line 21
Read Voice.md from the vault if it exists.
- Distinctive: line 31
Must do one of three things: create curiosity, promise a specific outcome, or challenge a belief
- Distinctive: line 120
Before presenting the final post, check for and remove:
- Distinctive: line 131
Read each paragraph out loud.
- Distinctive: line 143
If sharing a link, put it in the first comment
- Distinctive: line 152
Write the companion post text using the same rules above
- Distinctive: line 163
Never put links in the post body (first comment only)
- Distinctive: line 164
Never use engagement bait ("Comment YES if you agree!")
- Distinctive: line 165
Never use more than 5 hashtags
- Distinctive: line 166
Never tag more than 2-3 people, and only if genuinely relevant
- Distinctive: line 167
Never post and ghost. Engage with commenters in the first hour.
- Distinctive: line 168
Never sell in every post. 80% value, 20% promotional.
- Distinctive: line 169
Never write a wall of text with no line breaks
- Distinctive: line 170
Never start with "I'm excited to share..." unless it's genuinely newsworthy
- Distinctive: line 171
Never use engagement pod tactics
- Distinctive: line 172
Never write something that could be written by anyone about anything.
“Common” is measured: kept by at least 6 in 10 of the 36 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
Instructions
Write a LinkedIn post that sounds like a person talking, not a brand broadcasting. LinkedIn rewards saves, dwell time, and substantive comments. Write for those signals.
Step 0: Gather Context
Ask the user:
- What do you want to say? (the idea, story, lesson, or take)
- What format? Text post, carousel outline, or video caption
- What do you want people to do after reading? (comment, visit a link, save it, DM you)
If the user provides a story, article, video, or existing content, use that as source material instead of asking.
Read Voice.md from the vault if it exists. Match the creator's tone.
Step 1: Write the Hook
The hook decides whether anyone reads the rest. 60-70% of potential readers are lost at the "see more" button.
Rules:
- Under 110 characters (safe for mobile truncation)
- One line, two max
- Blank line after the hook. Always.
- Must do one of three things: create curiosity, promise a specific outcome, or challenge a belief
Hook types that work:
- Open loop: "I got fired on a Tuesday. By Thursday, I had the best job of my career."
- Bold claim: "Most networking advice is backwards."
- Specific number: "5 things I learned from 200 failed cold emails."
- Direct question: "What's the one skill nobody taught you that changed everything?"
- Reframe: "What if the thing holding you back is the same thing that got you here?"
Hooks that don't work:
- "In today's fast-paced world..."
- "I'm excited to announce..."
- "Thoughts?" as the entire hook
- Anything that could be written by anyone about anything
Present 2-3 hook options to the user. Let them pick.
Step 2: Write the Full Post
Pick the structure that fits the content:
Story Post (highest engagement for personal brand):
[Hook]
[Setup: 2-3 short lines of context]
[Tension: what went wrong or was hard]
[Turn: the moment things changed]
[Lesson: the specific takeaway]
[CTA: question inviting their story]Listicle / Value Post:
[Hook: "X things I learned from..."]
[Brief context: 1-2 lines]
1. Point
2. Point
3. Point
[Closing insight]
[CTA: "What would you add?"]Contrarian Take:
[Hook: bold statement]
[Why most people believe the conventional thing]
[What you've seen that contradicts it]
[Your alternative]
[CTA: "Am I wrong?"]Before/After:
[Hook: the result]
[Where you started]
[What changed]
[The outcome with data]
[CTA]Rules:
- 1,200-1,800 characters total (200-300 words)
- 1-2 line paragraphs max. Never a wall of text.
- Blank lines between every paragraph
- Conversational tone, not corporate
- 0-3 emojis max, only as visual anchors, never as decoration
- Links go in the first comment, never in the post body (60% reach penalty)
- End with a specific question or low-barrier CTA, not "Thoughts?"
- 3-5 hashtags at the end: 1 broad, 2 mid-tier, 1-2 niche
Step 3: Apply Humanizer Rules
Before presenting the final post, check for and remove:
- AI vocabulary (delve, landscape, crucial, leverage, robust, innovative, tapestry, multifaceted, holistic, comprehensive, pivotal, groundbreaking, paradigm, foster, encompasses)
- Significance inflation ("stands as a testament to", "a powerful reminder that")
- Filler phrases ("It's worth noting", "Interestingly", "In today's X landscape")
- Em dash overuse. Use commas, colons, or periods.
- Rule of three ("informative, engaging, and transformative")
- Negative parallelisms ("It's not just X; it's Y")
- Sycophantic language
- Corporate polish / press release tone
- Generic conclusions ("The future of X is Y")
Read each paragraph out loud. If it sounds assembled, rewrite it.
Step 4: Present and Revise
Show the post formatted exactly as it would appear on LinkedIn (with line breaks and spacing). Include:
- The post text
- First comment text (with any links)
- Suggested hashtags
Tell the user:
- Best posting times: Tuesday-Thursday, 8-10 AM or 12-2 PM local time
- Reply to every comment in the first 60 minutes
- If sharing a link, put it in the first comment
Format-Specific Notes
For Carousels:
- 5-10 slides
- One key idea per slide
- Cover slide is the hook (treat it like a thumbnail)
- CTA on the final slide
- Write the companion post text using the same rules above
For Video Captions:
- Under 90 seconds of video performs best
- Captions are required (85% watch without sound)
- Hook in first 5 seconds of video
- Native upload only (never a YouTube link)
- The post text is shorter: hook + 2-3 lines of context + CTA
What NOT to Do
- Never put links in the post body (first comment only)
- Never use engagement bait ("Comment YES if you agree!")
- Never use more than 5 hashtags
- Never tag more than 2-3 people, and only if genuinely relevant
- Never post and ghost. Engage with commenters in the first hour.
- Never sell in every post. 80% value, 20% promotional.
- Never write a wall of text with no line breaks
- Never start with "I'm excited to share..." unless it's genuinely newsworthy
- Never use engagement pod tactics
- Never write something that could be written by anyone about anything. Be specific. Have opinions. Sound like you.
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.

