# Social Clip Writer

> Extract episode highlights and format them as social media clips for Twitter/X, LinkedIn, Instagram, and TikTok

- Skill: `uitbreidenos/social-clip-writer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add uitbreidenos/social-clip-writer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/uitbreidenos/social-clip-writer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: UitbreidenOS (https://skillmd.com/u/uitbreidenos)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/uitbreidenos/social-clip-writer

---


## When to activate

- Creating social media posts from podcast episodes
- Writing thread content for Twitter/X
- Generating LinkedIn posts with episode insights
- Creating Instagram/TikTok caption scripts
- Building a content calendar from episode backlog

## When NOT to use

- For paid social advertising copy
- For email newsletter content
- For blog post repurposing

## Instructions

1. **Identify highlights.** Pick 5-7 quotable moments, surprising stats, or actionable tips from the episode.
2. **Write Twitter/X thread.** 5-8 tweet thread: hook tweet → key points → CTA to listen. Include episode link.
3. **Create LinkedIn post.** 150-200 word post: insight + personal reflection + question for engagement + episode link.
4. **Draft Instagram caption.** Short punchy caption (1-2 sentences) + relevant hashtags (15-20).
5. **Write TikTok/Reels script.** 30-60 second hook: "Did you know [surprising fact from episode]?" + key insight.
6. **Create audiogram text.** Short quote (under 20 words) for audiogram overlay with episode branding.
7. **Schedule and track.** Plan posts across 7 days post-episode; track engagement and click-through to episode.

## Example

```
Twitter Thread (Ep 42):
1/ "We were handling 10M requests/day and the database was on fire. Literally." 🧵

Dr. Sarah Chen shares the 3AM outage that changed how she thinks about scaling →

2/ The mistake? "We optimized for the happy path. Every single component assumed everything upstream was working."

3/ The fix: "Design for failure first. If your system can't handle a component going down gracefully, it's not ready for scale."

Listen to the full episode → [link]
```