social-media-posts

Files (1)

• SKILL.md

SKILL.md (first lines)

# 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

---

#### LinkedIn

**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
```

---

#### Facebook

**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?
```

---

From Infrasity-Labs/dev-gtm-claude-skills, MIT.

More from Infrasity-Labs/dev-gtm-claude-skills