social-media-posts▌
jezweb/claude-skills · updated Apr 29, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Create platform-specific social media posts that respect each platform's conventions, character limits, and audience expectations. Produces copy-paste-ready content.
Social Media Post Generator
Create platform-specific social media posts that respect each platform's conventions, character limits, and audience expectations. Produces copy-paste-ready content.
Modes
From Scratch
User provides topic + key points. Generate posts for selected platforms.
From Content
User provides existing content (blog post, newsletter, announcement, press release). Repurpose into platform-appropriate posts.
Campaign
Generate a coordinated set of posts across all platforms for a single launch, announcement, or event. Includes posting sequence and timing suggestions.
Workflow
1. Gather Input
| Field | Required | Example |
|---|---|---|
| Topic or source content | Yes | "We just launched a new feature" or path to blog post |
| Target platforms | Yes | LinkedIn, Facebook, Instagram, Reddit |
| Tone | No | Professional, casual, enthusiastic, educational |
| CTA | No | "Try it free", "Read more", "Comment your thoughts" |
| Link to include | No | https://example.com/blog/new-feature |
| Image available? | No | Yes/no — affects post structure |
If the user provides a file path or URL to existing content, read it first and extract the key messages.
2. Generate Per-Platform Posts
Audience: Professionals, B2B, industry peers Tone: Authoritative but approachable, thought-leadership Optimal length: 1,200–1,500 characters (longer posts perform well)
Structure:
[Hook line — must grab attention before "see more" truncation]
[blank line]
[2-3 short paragraphs with line breaks between]
[blank line]
[CTA or question to drive comments]
[blank line]
[3-5 relevant hashtags]
Rules:
- Hook must work in first 2 lines (before "…see more" at ~210 chars)
- Use line breaks liberally — wall-of-text kills engagement
- Ask a question at the end to drive comments
- Hashtags: 3-5 max, mix broad (#Marketing) and niche (#CloudflareWorkers)
- Links in comments perform better than in post body (algorithm penalty)
- No emoji overload — 1-2 max, or none for serious topics
Image specs: 1200×627px (1.91:1) for link preview, or 1080×1080 (1:1) for standalone
Example:
We just shipped something we've been building for 6 months.
It started as a "wouldn't it be nice if…" conversation and turned
into our most requested feature. Here's what we learned:
→ Users don't want more features. They want fewer clicks.
→ The prototype we almost killed became the final product.
→ Shipping weekly forced us to cut scope ruthlessly.
The full story is in our latest blog post (link in comments).
What's the hardest product decision you've made this year?
#ProductDevelopment #StartupLife #BuildInPublic
Audience: Mixed — friends, family, community, local businesses Tone: Conversational, warm, community-focused Optimal length: 80–150 characters for engagement, up to 500 for storytelling
Structure:
[Opening hook — conversational, relatable]
[1-2 short paragraphs]
[Link (if applicable) — Facebook generates preview cards]
[Engagement prompt — question or poll]
Rules:
- Link posts: Facebook auto-generates a preview card — don't repeat the headline in your text
- Short posts (under 130 chars) get larger text rendering in feed
- Questions and polls drive highest engagement
- Tag relevant pages when mentioning partners/clients
- Hashtags: 1-3 or none — Facebook hashtags are less effective than other platforms
- Emojis are welcome but don't overdo (2-3 max)
Image specs: 1200×630px (1.91:1) for link preview, 1080×1080 (1:1) for photo posts
Example:
6 months ago we started building something our users kept asking for.
Today it's live. 🚀
We wrote up the full story — the pivots, the almost-killed prototype,
and why "fewer clicks" won over "more features."
[link]
What feature have you shipped that surprised you?
Audience: Visual-first, younger demographic, lifestyle/brand-focused Tone: Authentic, visual storytelling, personality-forward Optimal length: Key message in first 125 chars (truncation point), full caption up to 2,200
Structure:
[First line — must work as standalone (before "…more")]
[blank line]
[Story or detail — 2-4 short paragraphs]
[blank line]
[CTA — save, share, comment, link in bio]
.
.
.
[Hashtags — in first comment OR separated by dots]
Rules:
- First 125 characters must carry the message (everything after is hidden behind "…more")
- No clickable links in captions — direct to "link in bio"
- Hashtags: 20-30 in first comment (not in caption) for discoverability
- Mix hashtag sizes: 5 large (1M+ posts), 10 medium (100K-1M), 10 niche (<100K)
- Emojis are part of the language — use them naturally
- Carousel posts: include a swipe CTA ("Swipe for the full breakdown →")
- Stories: prompt action ("Reply with 🔥 if you relate")
Image specs: 1080×1080 (1:1) feed, 1080×1350 (4:5) portrait, 1080×1920 (9:16) stories/reels
Example:
We shipped our most requested feature today. Here's the story 👇
Six months ago, someone on our team said "wouldn't it be nice
if users could do this in one click instead of five?"
We almost killed the prototype twice. But our users kept asking
for it. So we shipped it.
The biggest lesson? Your users don't want more features.
They want fewer clicks.
Full story → link in bio
💬 What's one feature you wish was simpler in your favourite app?
First comment:
#ProductLaunch #StartupLife #BuildInPublic #TechStartup
#ProductDevelopment #UXDesign #SaaS #FeatureLaunch
[... 20-30 total hashtags]
Audience: Community-specific, values authenticity, allergic to marketing Tone: Genuine, value-first, conversational, never salesy Optimal length: Title 100-150 chars, body varies by subreddit
Structure:
Title: [Descriptive, value-focused — NOT clickbait]
Body:
[Context — why this matters to this community]
[The substance — what you learned, built, or discovered]
[Optional: link to more detail]
[Discussion prompt — genuine question]
Rules:
- Title is everything — Reddit lives and dies by titles
- NO self-promotion feel — lead with value, not product
- Each subreddit has different norms — check the rules before posting
- Don't use hashtags (not a Reddit convention)
- Don't use emojis in titles (feels out of place on most subreddits)
- Share the insight, not the product. "Here's what we learned" > "Check out our new feature"
- Cross-posting: adapt tone per subreddit (r/startups vs r/webdev vs r/smallbusiness)
Subreddit suggestions by topic:
| Topic | Subreddits |
|---|---|
| Product launch | r/SideProject, r/startups, r/indiehackers |
| Web dev | r/webdev, r/javascript, r/reactjs |
| Design | r/web_design, r/UI_Design |
| Business | r/smallbusiness, r/Entrepreneur |
| Tech | r/programming, r/technology |
Example:
Title: After 6 months of building, the biggest lesson was
"users want fewer clicks, not more features"
We built a feature our users kept requesting. Halfway through
we almost killed it because the prototype felt clunky.
What saved it: we stopped adding capabilities and started
removing steps. The final version does less than the prototype
but users complete the task in 1 click instead of 5.
Three things I'd tell past-me:
1. Prototype with your heaviest users, not your most vocal ones
2. "Ship weekly" forces you to cut scope — that's a feature
3. The thing users ask for and the thing they need are different
Anyone else had a similar experience where removing features
improved the product?
3. Image Recommendations
For each platform, suggest image requirements:
| Platform | Format | Dimensions | Notes |
|---|---|---|---|
| PNG/JPG | 1200×627 | Text overlay OK, keep key message in centre | |
| PNG/JPG | 1200×630 | Minimal text (old 20% rule still affects reach) | |
| PNG/JPG | 1080×1080 | Visual-first — image must work without caption | |
| PNG/JPG | Varies | Optional — text posts often perform better |
If the ai-image-generator skill is available, suggest using it to generate companion images with the right aspect ratios.
4. Output Format
Present each post in a clearly labelled block:
═══ LINKEDIN ═══
[post content]
═══ FACEBOOK ═══
[post content]
═══ INSTAGRAM (Caption) ═══
[caption content]
═══ INSTAGRAM (First Comment — Hashtags) ═══
[hashtags]
═══ REDDIT (r/subreddit) ═══
Title: [title]
Body: [body]
Save to .jez/artifacts/social-posts-[topic].md if the user wants to keep them for scheduling.
Campaign Mode
For launches or announcements, generate a posting sequence:
| Timing | Platform | Post type |
|---|---|---|
| Day -1 | Teaser / behind-the-scenes | |
| Day 0 (morning) | All platforms | Announcement post |
| Day 0 (afternoon) | Instagram Stories | Quick video/carousel |
| Day +1 | Value-focused discussion | |
| Day +3 | Results/learnings follow-up | |
| Day +7 | Customer reaction / testimonial |
Quality Rules
- Never copy-paste the same text across platforms — each platform has different conventions
- No corporate jargon — "leverage our synergies" belongs nowhere
- Front-load the value — every platform truncates. The first line must work standalone.
- Match the platform culture — LinkedIn is not Instagram is not Reddit
- Include a reason to engage — question, poll, or genuine discussion prompt
- Check character limits — LinkedIn (3,000), Facebook (63,206), Instagram caption (2,200), Reddit title (300)
- Never fake engagement — no "Drop a 🔥 if you agree" on LinkedIn, no hashtag spam on Reddit
How to use social-media-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 social-media-posts
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches social-media-posts from GitHub repository jezweb/claude-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 social-media-posts. Access the skill through slash commands (e.g., /social-media-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.4★★★★★64 reviews- ★★★★★Shikha Mishra· Dec 28, 2024
Registry listing for social-media-posts matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Noor Haddad· Dec 16, 2024
I recommend social-media-posts for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Olivia Agarwal· Dec 12, 2024
social-media-posts reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Hassan Diallo· Dec 8, 2024
Useful defaults in social-media-posts — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Yuki Srinivasan· Dec 4, 2024
social-media-posts is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Noor Khan· Nov 27, 2024
I recommend social-media-posts for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Camila Tandon· Nov 23, 2024
social-media-posts reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Hassan Abebe· Nov 7, 2024
Useful defaults in social-media-posts — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Diego Yang· Nov 3, 2024
social-media-posts is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Fatima Malhotra· Oct 26, 2024
social-media-posts is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 64