linkedin-posts▌
kostja94/marketing-skills · updated May 27, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Guides LinkedIn post copy creation and optimization. Use for generating publish-ready professional content. Suitable for copy agents and design agents (image specs).
Platforms: LinkedIn
Guides LinkedIn post copy creation and optimization. Use for generating publish-ready professional content. Suitable for copy agents and design agents (image specs).
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Output: Publish-Ready Copy
This skill enables agents to generate LinkedIn post copy optimized for engagement. Output includes character-counted text and structure for the "See more" threshold.
Character Limits
| Type | Limit | Notes |
|---|---|---|
| Post | 3,000 characters | Optimal: 1,300–1,600 |
| First line (critical) | 210–235 chars | Visible before "See more"; 60–80% decide here |
| Short posts | 100–200 chars | Polls, announcements, quotes |
Optimal Length by Content Type
| Type | Characters | Use |
|---|---|---|
| Short | 100–200 | Polls, announcements, quotes |
| Medium | 300–1,200 | Case studies, tips, BTS |
| Long | 1,200–2,000 | Thought leadership, analysis |
| Sweet spot | 1,300–1,600 | Highest engagement |
| Avoid | >2,000 | ~35% engagement drop |
First Line (Hook)
- Place key message in first 140 chars
- Strong openings: Specific results, pain points, bold claims, surprising stats
- Avoid: Vague teases, hashtag-first, generic greetings
Image Specs (for Design Agents)
| Format | Dimensions | Use |
|---|---|---|
| Single image | 1200×627 (1.91:1) | Feed; link previews |
| Square | 1200×1200 | Single image |
| Carousel | Up to 20 images | Multi-image post |
| File | ≤10 MB; JPG/PNG | Native uploads perform better |
| Vertical | Preferred | 88% browse on mobile |
Best Practices
- Mobile-first: 88% users on mobile
- Polls & PDFs: Highest reach
- Post frequency: Weekly minimum for companies
- Alt text: Add for accessibility
Output Format
When generating LinkedIn copy, provide:
- First line (≤210 chars; hook)
- Full post with character count
- Hashtags (3→; end of post)
- Image specs (if design agent needs dimensions)
Related Skills
- linkedin-ads: Paid promotion on LinkedIn; Sponsored Content, Lead Gen Forms; professional tone aligns with organic posts
- influencer-marketing: LinkedIn influencers for B2B
- about-page-generator: Professional brand alignment
- visual-content: Cross-channel visual planning; LinkedIn image specs in context
How to use linkedin-posts on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add linkedin-posts
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches linkedin-posts from GitHub repository kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate linkedin-posts. Access the skill through slash commands (e.g., /linkedin-posts) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ 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.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★31 reviews- ★★★★★Arjun Khanna· Dec 28, 2024
linkedin-posts reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Dhruvi Jain· Dec 16, 2024
We added linkedin-posts from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Arjun Malhotra· Dec 8, 2024
linkedin-posts has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Arya Srinivasan· Nov 27, 2024
Solid pick for teams standardizing on skills: linkedin-posts is focused, and the summary matches what you get after install.
- ★★★★★Evelyn Haddad· Nov 19, 2024
We added linkedin-posts from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Oshnikdeep· Nov 7, 2024
linkedin-posts reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ganesh Mohane· Oct 26, 2024
linkedin-posts is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Yuki Anderson· Oct 18, 2024
I recommend linkedin-posts for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Anika Shah· Oct 10, 2024
Keeps context tight: linkedin-posts is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Emma Gill· Sep 25, 2024
linkedin-posts reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 31