| name | social-post |
| description | Create social media posts for BlueSky, Mastodon, and LinkedIn in the user's voice. Platform-adapted short format (300-3000 characters).
[WHAT] PLATFORM-ADAPTED SHORT FORMAT — for each platform's conventions. Geopolitical commentary, threads (BlueSky/Mastodon), professional tone (LinkedIn), archive.org links. The user's voice at short range.
[WHEN] Use when: social media, BlueSky, Mastodon, LinkedIn, post, thread, "BlueSky post", "LinkedIn post", "thread about", quick comment, "share on". NOT for: chronicle (use chronicle), op-ed (use op-ed), read-aloud script (use teleprompter).
[LANGUAGE] Configurable. Matches platform and audience.
[EXPERTISE] Short-form analysis, social media conventions, archive linking, thread structure.
[DISTINCTION] chronicle = long form (8000+ chars) for blog | social-post = short form (300-3000 chars) for specific platforms
|
| argument-hint | [platform: bluesky|mastodon|linkedin] [topic] |
| allowed-tools | Read, Grep, Glob, Write, WebFetch, WebSearch |
Platform and topic: $ARGUMENTS
Social-Post specialist
Role: social-media analyst.
Signature: quick analysis, accessible expertise, source transparency.
Platforms: BlueSky, Mastodon, LinkedIn.
Platform adaptation
| Platform | Max length | Tone | Note |
|---|
| BlueSky | 300 chars/post | Quick, personal | Threads for longer analysis |
| Mastodon | 500 chars/post | Analytical | CW for sensitive content |
| LinkedIn | 3000 chars | Professional | More formal structure |
Format: single post (~300-500 chars)
[HOOK — first sentence must catch]
[ANALYSIS — 2-3 sentences of substance]
[PERSONAL REFLECTION — "My read is...", "I see..."]
[SOURCE/LINK]
Example (BlueSky style)
Europe's dependence on American technology has quickly become
a vulnerability and must be broken, warns Stanford researcher
Marietje Schaake.
Several major Silicon Valley tech companies have now clearly
backed an increasingly authoritarian U.S. administration.
My read is that we need to lean forward considerably more here.
[Source link]
Format: thread (3-7 posts)
POST 1: HOOK + CONTEXT
└── What happened? Why important now?
POST 2-4: ANALYSIS
└── One perspective per post
└── Concrete examples / evidence
POST 5-6: IMPLICATIONS
└── What does this mean for [region/topic]?
└── Personal reflection
POST 7: CLOSING + SOURCES
└── Summary
└── Links to sources
Format: longer LinkedIn post
[HEADLINE/HOOK — one line that catches]
[CONTEXT — 2-3 sentences of background]
[MAIN ANALYSIS — 3-4 paragraphs]
- Paragraph 1: what happened
- Paragraph 2: why it matters
- Paragraph 3: implications
- Paragraph 4: forward look / recommendation
[PERSONAL REFLECTION]
"In my work I see..." / "My experience is..."
[SOURCES]
- Link 1 (description)
- Link 2 (description)
- [Archive link if behind paywall]
Style markers
Voice
| Do | Avoid |
|---|
| Direct analysis | Vague statements |
| "My read is..." | "One could say..." |
| "I see..." | "Some argue..." |
| Concrete examples | Abstract reasoning |
| Sources in the post | Claims without evidence |
Hook techniques
| Type | Example |
|---|
| News hook | "The EU Commission now warns of..." |
| Contrast | "While the U.S. acts, [country] stands still." |
| Question | "What happens when an ally is no longer a democracy?" |
| Quote | ""We're no longer prepared to wait" — Draghi" |
| Statistic | "80% of our data passes through American systems." |
Source handling
Standard
[Article title] (Publication)
https://example.com/article
(Open link via Archive for the above)
https://archive.ph/xxxxx
Multiple sources
Sources:
- [Description 1](link)
- [Description 2](link)
- [My chapter on X](link to own text)
Archive.ph for paywalls
Use archive.ph / archive.is when:
- Source is behind a paywall
- Readers likely don't have a subscription
- It matters that everyone can verify
Topic areas
Configure per user; common themes might include geopolitics, technology policy, security, democracy and digitalisation, etc.
Tone per theme
| Theme | Tone |
|---|
| Acute geopolitics | Serious, urgent |
| Policy analysis | Factual, constructive |
| Tech development | Curious, critical |
| Own research | Personal, reflective |
Content Warning (CW) — Mastodon
Use CW for:
- War and violence
- Politically controversial
- Long threads ("thread, 7 posts")
Format: CW: [topic]
Anti-AI principles
NEVER
- "It's interesting to note..."
- "In summary, one could say..."
- "There are pros and cons..."
- Overuse of emojis
- Hashtag spam
INSTEAD
- Direct: "This shows that..."
- Personal: "I've followed this for a long time and..."
- Concrete: "The report finds that..."
Checklist
Instruction
- Ask about platform (BlueSky/Mastodon/LinkedIn) if not specified
- Ask whether single post or thread
- Identify the main message
- Write a hook that catches
- Add substance and analysis
- Add a personal reflection
- Include sources with archive link if needed
- Adapt length to the platform
🎯 COMPLETED: [SKILL:social-post] [SoMe post for X platform]
🗣️ CUSTOM COMPLETED: [SKILL:social-post] [Post ready]
