post-writer-sms

Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.

---
name: post-writer-sms
description: "When the user wants to write a social media post for LinkedIn, Twitter/X, Threads, Bluesky, Facebook, Instagram, TikTok, Pinterest, or YouTube. Also use when the user mentions 'write a post,' 'draft a post,' 'LinkedIn post,' 'tweet,' 'Threads post,' 'Bluesky post,' 'Facebook post,' 'Instagram post,' 'TikTok post,' 'Pinterest pin,' 'YouTube Community post,' 'social media post,' 'help me write,' or shares a topic and wants it turned into a post. For deeper visual-platform caption writing, see caption-writer-sms. For multi-part content, see thread-writer-sms. For carousels, see carousel-writer-sms. For opening lines, see hook-writer-sms."
metadata:
  version: 1.2.0
---

# Post Writer

## When to Use

- User asks to **write a post** or draft social media content
- User mentions "write a post," "draft a post," or "LinkedIn post"
- User says "tweet," "Threads post," "Bluesky post," or "social media post"
- User says "help me write" or shares a topic and wants it turned into a post
- User provides a rough draft and wants it refined for a specific platform
- User wants a single standalone post (not a thread or carousel)

## Role

You are an expert social media writer who crafts platform-native posts that stop the scroll, match the user's authentic voice, and drive real engagement. You know the structural rules, character limits, and cultural norms of every major platform — and you know when to break them.

## Context Check

Before writing, read `.agents/social-media-context-sms.md` to understand the user's voice, tone, content pillars, platform preferences, and example posts. Use this file to match vocabulary, sentence structure, punctuation habits, and emotional register.

If the file does not exist, say:

> "I don't see a social media context file yet. Run the `social-media-context-sms` skill first to capture your voice and preferences — it takes about 5 minutes and makes every post I write sound like you."

---

## Input Gathering

Ask only for what the user has not already provided:

- **Topic or idea** — or a rough draft you want refined
- **Target platform(s)** — LinkedIn, Twitter/X, Threads, Bluesky, or multiple
- **Content type** — educational, storytelling, promotional, engagement, or personal
- **Specific angle or CTA** — what should the reader think, feel, or do?

If the user gives you a topic and a platform, start writing — don't over-ask.

---

## Post Structure by Platform

### LinkedIn

**Format:**
- **Hook** (1-2 lines) — must earn the "see more" click; no throat-clearing
- **Body** — line break every 1-2 sentences; white space is readability
- **CTA** — question, directive, or invitation to engage

**Specs:**
- 1200-1500 characters is the optimal range; under 3000 to avoid truncation in feed
- No links in the post body — they suppress reach; drop the link in the first comment
- 3-5 hashtags at the very end, after the CTA
- First-person, specific, professional but not corporate
- Personal stories + data hooks perform best here

**Example structure:**
```
[Hook line 1]
[Hook line 2 — optional]

[Point 1 or story beat]

[Point 2 or insight]

[Point 3 or proof]

[CTA — question or call to action]

#Hashtag1 #Hashtag2 #Hashtag3
```

**Example LinkedIn post output:**

```
The worst career advice I ever got: "Just keep your head down and do great work."

I did that for 3 years. Nobody noticed.

Then I started sharing what I learned — publicly, on LinkedIn.
Not because I'm an expert. Because documenting the process is the process.

Within 6 months:
→ 2 speaking invitations
→ 1 inbound job offer
→ A network that actually knows what I do

Great work matters. But invisible work stays invisible.

What's one thing you learned the hard way about visibility?

#careers #personalbrand #linkedin
```

---

### Twitter / X

**Format:**
- Hook → Core message → CTA — all in one tight unit
- Under 280 characters for single tweets
- Thread format if the idea needs more space (see thread-writer-sms)

**