Create platform-specific social media posts that respect each platform's conventions, character limits, and audience expectations. Produces copy-paste-ready content.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsocial-media-postsExecute the skills CLI command in your project's root directory to begin installation:
Fetches social-media-posts from jezweb/claude-skills 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 social-media-posts. Access via /social-media-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
2
total installs
2
this week
697
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
697
stars
Create platform-specific social media posts that respect each platform's conventions, character limits, and audience expectations. Produces copy-paste-ready content.
User provides topic + key points. Generate posts for selected platforms.
User provides existing content (blog post, newsletter, announcement, press release). Repurpose into platform-appropriate posts.
Generate a coordinated set of posts across all platforms for a single launch, announcement, or event. Includes posting sequence and timing suggestions.
| 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.
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:
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:
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:
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:
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?
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.
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.
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 |
Make 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.
jezweb/claude-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Registry listing for social-media-posts matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend social-media-posts for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
social-media-posts reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in social-media-posts — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
social-media-posts is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend social-media-posts for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
social-media-posts reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in social-media-posts — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
social-media-posts is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
social-media-posts is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 64