Authentic LinkedIn posts that establish thought leadership through genuine insight, not engagement optimization.
Works with
Emphasizes authenticity over virality: real experiences, specific insights, and honest reflection resonate more than manufactured vulnerability or perfectly structured stories
Provides five post formats (story, list, contrarian, observation, and media-based) with templates and guardrails for each, plus guidance on hooks, body structure, and closings
Covers voice developmen
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionwriting-linkedin-postsExecute the skills CLI command in your project's root directory to begin installation:
Fetches writing-linkedin-posts from jamesgray007/hoai-course and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate writing-linkedin-posts. Access via /writing-linkedin-posts in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
3
total installs
3
this week
17
GitHub stars
0
upvotes
Run in your terminal
3
installs
3
this week
17
stars
Create engaging, authentic LinkedIn posts that drive meaningful engagement and establish thought leadership.
LinkedIn has matured. Readers can spot manufactured vulnerability and engagement bait instantly. The posts that resonate now are genuinely useful or genuinely human—not optimized for virality.
What works:
What doesn't:
The biggest mistake is cramming multiple tips, stories, or angles into one post. Focus on:
If you have five points, that's five posts.
Every post must educate, inspire, or entertain. Ask: "Would I find this valuable if a stranger posted it?" Not "Will this get engagement?"
Top Voices don't just post well—they're recognizable. Their perspective, style, and focus areas are consistent.
Answer these before writing:
Develop 2-3 recognizable elements:
Your LinkedIn voice should be:
The first 2-3 lines appear before "See more" and determine everything.
Modern hooks that work (avoid overused patterns):
| Type | Example | Why It Works |
|---|---|---|
| Honest admission | "I've been wrong about remote work." | Genuine, not performed |
| Specific observation | "I've noticed something in every founder who scaled past $10M." | Credibility + curiosity |
| Direct challenge | "Most career advice optimizes for the wrong thing." | Provokes thought |
| Unexpected angle | "The best hire I made had the worst resume." | Subverts expectations |
| Simple truth | "Nobody talks about how lonely leadership is." | Resonates emotionally |
Hooks to retire:
See references/hooks.md for comprehensive examples.
Structure for scannability:
Storytelling framework:
End with purpose, not desperation:
Good closes:
Avoid:
Authentic sharing builds connection. Performed vulnerability destroys trust.
Share when:
Don't share when:
Before posting something personal, ask:
Best for: Personal experiences, lessons learned, career moments
[Hook - honest admission or surprising outcome]
[One sentence of context]
[What happened - the tension or challenge]
[The turning point]
[What you learned]
[Question or reflection for reader]
Best for: Frameworks, actionable advice, curated insights
[Hook - clear value promise]
[Why this matters - one sentence]
1. [Point with brief context]
2. [Point with brief context]
3. [Point with brief context]
(3-7 items max)
[Closing insight or question]
Best for: Challenging conventional wisdom (with substance)
[Your contrarian position, stated directly]
[The common belief you're challenging]
[Your reasoning - why you see it differently]
[Evidence or experience]
[Nuanced conclusion - acknowledge complexity]
[Invite discussion]
Contrarian guardrails:
Best for: Industry insights, trends, patterns you've noticed
[What you've observed]
[Specific evidence or examples]
[Why it matters]
[Your interpretation]
[Question to test if others see it too]
Text-only posts aren't the only option. Different formats serve different purposes.
What happens after you post matters as much as what you post.
LinkedIn's algorithm weighs early engagement heavily:
Your comments on others' posts build your brand too:
Find your spot on each scale:
Corporate ←————————→ Casual
Reserved ←————————→ Vulnerable
Analytical ←————————→ Emotional
Serious ←————————→ Playful
Most Top Voices sit slightly right of center on each.
Content anti-patterns:
Engagement anti-patterns:
Format anti-patterns:
references/hooks.md - Complete hook patterns with examplesreferences/examples.md - Full post examples demonstrating best practicesMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
davila7/claude-code-templates
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
I recommend writing-linkedin-posts for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: writing-linkedin-posts is focused, and the summary matches what you get after install.
We added writing-linkedin-posts from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
writing-linkedin-posts fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
writing-linkedin-posts has been reliable in day-to-day use. Documentation quality is above average for community skills.
writing-linkedin-posts reduced setup friction for our internal harness; good balance of opinion and flexibility.
writing-linkedin-posts is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: writing-linkedin-posts is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend writing-linkedin-posts for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
writing-linkedin-posts is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 25