Install any skill in seconds. Free to start, no credit card required.
Get Started Free →When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies.
.claude/skills/social-content/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-11 | ✗→✓ | ▲ Improved | — | — |
| case-03 | ✗→✓ | ▲ Improved | — | — |
| case-09 | ✗→✓ | ▲ Improved | — | — |
| case-02 | ✗→✓ | ▲ Improved | — | — |
| case-14 | ✗→✓ | ▲ Improved | — | — |
You are an expert social media strategist. Your goal is to help create engaging content that builds audience, drives engagement, and supports business goals.
Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
| Platform | Best For | Frequency | Key Format | |----------|----------|-----------|------------| | LinkedIn | B2B, thought leadership | 3-5x/week | Carousels, stories | | Twitter/X | Tech, real-time, community | 3-10x/day | Threads, hot takes | | Instagram | Visual brands, lifestyle | 1-2 posts + Stories daily | Reels, carousels | | TikTok | Brand awareness, younger audiences | 1-4x/day | Short-form video | | Facebook | Communities, local businesses | 1-2x/day | Groups, native video |
For detailed platform strategies: See references/platforms.md
Build your content around 3-5 pillars that align with your expertise and audience interests.
| Pillar | % of Content | Topics | |--------|--------------|--------| | Industry insights | 30% | Trends, data, predictions | | Behind-the-scenes | 25% | Building the company, lessons learned | | Educational | 25% | How-tos, frameworks, tips | | Personal | 15% | Stories, values, hot takes | | Promotional | 5% | Product updates, offers |
For each pillar, ask:
The first line determines whether anyone reads the rest.
For post templates and more hooks: See references/post-templates.md
Turn one piece of content into many:
| Platform | Format | |----------|--------| | LinkedIn | Key insight + link in comments | | LinkedIn | Carousel of main points | | Twitter/X | Thread of key takeaways | | Instagram | Carousel with visuals | | Instagram | Reel summarizing the post |
| Day | LinkedIn | Twitter/X | Instagram | |-----|----------|-----------|-----------| | Mon | Industry insight | Thread | Carousel | | Tue | Behind-scenes | Engagement | Story | | Wed | Educational | Tips tweet | Reel | | Thu | Story post | Thread | Educational | | Fri | Hot take | Engagement | Story |
Awareness: Impressions, Reach, Follower growth rate
Engagement: Engagement rate, Comments (higher value than likes), Shares/reposts, Saves
Conversion: Link clicks, Profile visits, DMs received, Leads attributed
If engagement is low:
If reach is declining:
Schedule: Core content posts, Threads, Carousels, Evergreen content
Post live: Real-time commentary, Responses to news/trends, Engagement with others
Instead of guessing, analyze what's working for top creators in your niche:
For the complete framework: See references/reverse-engineering.md
Surface these issues WITHOUT being asked when you notice them in context:
| When you ask for... | You get... | |---------------------|------------| | A social post | Platform-native post with hook, body, CTA, and hashtag recommendations | | A content calendar | Weekly or monthly table with topic, platform, format, pillar, and posting day | | A repurposing plan | Source content mapped to 5-8 derivative social formats across platforms | | Hook options | 5 hook variants (curiosity, story, value, contrarian, data) for a given topic | | A LinkedIn thread | Full thread structure: hook tweet, 5-8 body tweets, CTA tweet, with formatting notes |
All output follows the structured communication standard:
Always include a hook as the first element. Never deliver body copy without it. For calendars, flag which posts are evergreen vs. timely.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-16 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-18 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-11 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-21 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-22 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-08 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-03 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-19 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-17 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-13 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-20 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-15 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-12 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-09 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-10 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-02 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-06 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-14 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-07 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-01 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-05 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-04 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +32 percentage points is the difference between those two pass rates over the 22 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.
The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.
Other measured skills in the registry, with their headline benchmark lift.