---
name: thread-writer
description: Write viral X/Twitter threads from any topic, URL, or notes. Structures content with hooks, value delivery, and CTAs using proven engagement patterns.
metadata: {"openclaw": {"emoji": "🧵", "homepage": "https://github.com/jarvisonclaw/thread-writer"}}
---

# Thread Writer 🧵

Write high-engagement X/Twitter threads from a topic, URL, article, or raw notes.

## When to use

Use this skill when the user wants to:
- Create an X/Twitter thread from a topic or idea
- Turn a blog post or article URL into a thread
- Repurpose long-form content into a thread format
- Write a build-in-public update thread
- Create educational/informational threads

## How to invoke

The user says something like:
- "Write a thread about [topic]"
- "Turn this article into a thread: [URL]"
- "Thread this: [notes/ideas]"
- `/thread-writer [topic or URL]`

## Thread Structure

Follow this proven structure for maximum engagement:

### 1. Hook (Tweet 1)
The most important tweet. Must stop the scroll.
- Use pattern interruption (counterintuitive claim, surprising stat, bold statement)
- Create curiosity gap — reader MUST click to see more
- Keep it under 200 characters if possible
- No hashtags in the hook

### 2. Context (Tweet 2)
- Establish credibility or relevance
- "Here's why this matters..." or "I spent X doing Y, here's what I learned"
- Bridge from hook to value

### 3. Value Tweets (Tweets 3-8)
- One clear idea per tweet
- Use numbered lists or bullet points for scannability
- Include specific examples, numbers, or stories
- Each tweet should stand alone AND flow in sequence
- Aim for 5-7 value tweets (sweet spot for engagement)

### 4. Summary/Takeaway (Second-to-last tweet)
- Distill the key insight into one memorable line
- "The bottom line:" or "TL;DR:"

### 5. CTA (Final tweet)
- Ask for engagement: "Follow for more [topic]" or "Repost if this helped"
- Optional: link to related resource
- Keep it natural, not desperate

## Formatting Rules

- NO hashtags (they reduce reach on X in 2025+)
- Use line breaks for readability
- Emoji sparingly — 1-2 per tweet max, not every line
- Numbers and specifics > vague claims
- Short paragraphs (2-3 lines max per block)
- Use "→" for lists instead of bullet points (renders better on X)

## Thread Length

- Optimal: 7-10 tweets (including hook and CTA)
- Minimum: 5 tweets
- Maximum: 15 tweets (longer threads lose readers)
- If content requires more, split into a series

## If Given a URL

1. Fetch the URL content using web_fetch
2. Extract the key insights, data points, and arguments
3. Restructure into thread format (don't just summarize — add perspective)
4. Credit the original source in one tweet

## Output Format

Present the thread as:

```
🧵 THREAD DRAFT (X tweets)

1/ [Hook tweet]

2/ [Context tweet]

3/ [Value tweet]
...

N/ [CTA tweet]
```

Then ask: "Ready to post, or want me to adjust anything?"

## Quality Checklist

Before presenting the thread, verify:
- [ ] Hook creates genuine curiosity (would YOU click?)
- [ ] Each tweet adds new value (no filler)
- [ ] Thread has a clear narrative arc
- [ ] Specific examples/numbers included
- [ ] No hashtags
- [ ] Under 280 chars per tweet
- [ ] CTA feels natural
- [ ] Would perform well if any single tweet went viral alone