social-media-content

---
name: social-media-content
description: >-
  Short-form social media content for LinkedIn, Twitter/X, and similar platforms. Use for LinkedIn post drafting, Twitter/X thread writing, hook-first content structures, platform-native tone calibration, hashtag strategy, and engagement-optimised formatting. Trigger phrases: "write a LinkedIn post", "draft a Twitter thread", "turn this into a thread", "write a social post about", "make this shareable". NOT for long-form blog articles or newsletters — use the storytelling or email-marketing skill for those. NOT for ad copy or paid social — those have conversion-optimisation constraints beyond organic content. NOT for content calendars or scheduling strategy — this skill writes the content, not the plan.
allowed-tools: Read,Write,Edit,Bash
---

# social-media-content

LinkedIn posts, Twitter/X threads, short-form social content, platform-native tone adaptation, and engagement-optimised formatting.

## When to use

- Write a LinkedIn post announcing our product launch
- Turn this blog post into a Twitter thread
- Draft a thought leadership post about AI replacing junior developers
- Write a hook for a LinkedIn post about our open-source library
- Make this technical announcement shareable on social media
- Write 5 hashtags for a post about remote work culture
- Draft a Twitter/X post celebrating our Series A funding
- Write a LinkedIn carousel outline about design systems

## When NOT to use

- Write a 2000-word blog post about distributed systems — Long-form blog — not short-form social
- Write an email newsletter for our customers — Email content — use email-marketing skill
- Plan our Q3 content calendar — Strategy/planning — not content creation
- Write a Google Ads headline for our SaaS tool — Paid ad copy — different constraints

## Anti-patterns

### Symptom
Invoking this skill for tasks outside its scope — e.g., infrastructure concerns when the request is about application code, or vice versa.

### Problem
Scope mismatch wastes context and produces advice tuned for the wrong domain. A database schema skill answering a connection-pooling question gives schema advice when the real problem is operational configuration.

### Solution
Read the NOT for clauses carefully. If the request matches an exclusion, identify the correct skill (check SkillStack for the right domain) rather than stretching this skill to cover adjacent ground.

• SKILL.md 2 KB
• evals/evals.json 2 KB
• evals/trigger-evals.json 2 KB