---
name: twitter-threads
description: "Transform research reports into engaging Twitter/X threads. Triggers on: twitter threads, create threads, threads from research, repurpose research to twitter."
version: 1.0.0
author: Xavier Caffrey
license: MIT
---

# Twitter Threads from Research

Transform research reports into engaging Twitter/X threads that drive engagement and build authority.

## Setup

Place this file in `~/.claude/skills/twitter-threads/SKILL.md` to use it with Claude Code.

---

## Workflow

### Step 1: Read Research

1. Ask the user which file or folder contains the research
2. Read all markdown files in the selected location

### Step 2: Analyze Thread Potential

Scan the research for thread-worthy content:
- **Statistics/data points** — Numbers that surprise or validate
- **Contrarian takes** — Goes against common belief
- **How-to sequences** — Step-by-step processes
- **Story hooks** — Personal anecdotes or case studies
- **Myth busters** — "Most people think X, but actually Y"

Report to user:
```
Found [N] potential threads:
1. [Hook summary] - [type: stat/contrarian/how-to/story/myth]
2. ...
```

### Step 3: Draft Threads

For each approved thread concept, create:
- **Hook tweet** (first tweet) — Must stop the scroll
- **Body tweets** (2-8 tweets) — One idea per tweet
- **CTA tweet** (final) — What should reader do next

Save to `threads_draft.json` in the project folder using this structure:
```json
{
  "threads": [
    {
      "id": "thread_1",
      "hook_summary": "LinkedIn stats that will change your approach",
      "tweets": [
        "Most people send 100 connection requests hoping for 5 meetings.\n\nHere's the math that changed how I do LinkedIn outbound:",
        "Tweet 2 content...",
        "Final tweet with CTA"
      ],
      "status": "draft"
    }
  ]
}
```

### Step 4: User Review

Display each thread formatted for easy review:
```
---
THREAD 1: [hook_summary]
---
1/ [first tweet]

2/ [second tweet]

...
---
```

Ask user: "Approve, edit, or skip each thread?"

### Step 5: Save Approved Threads

Save approved threads to `threads_draft.json` with updated statuses. Display copy-ready output for manual posting or scheduling.

---

## Writing Rules

### DO:
- Start with data or bold claim
- Use short sentences
- Include specific numbers
- End with actionable takeaway
- Write like you're texting a smart friend

### DON'T:
- Use rhetorical questions as hooks ("Want to know...?")
- Add emojis unless they add meaning
- Use corporate speak or buzzwords
- Write walls of text
- Start with "I"

### Tweet Length
- Aim for 200-250 characters per tweet
- Never exceed 280 characters
- Leave room for engagement (likes don't need full tweets)

## Thread Formulas That Work

**The Stat Opener:**
```
[Surprising statistic].

Here's what that means for [audience]:
```

**The Contrarian:**
```
Everyone says [common advice].

I did the opposite. Here's what happened:
```

**The Story:**
```
[Year], I [situation].

[Unexpected outcome]. Here's the lesson:
```

**The Framework:**
```
The [X]-step process I use for [outcome]:

(Thread)
```

---

## Output Format

All approved threads saved as `threads_draft.json` with status tracking:
- `"draft"` — Written, not yet reviewed
- `"approved"` — User approved, ready to post
- `"posted"` — Published to Twitter/X
- `"scheduled"` — Scheduled for future posting