Creates viral-format Twitter/X threads with numbered hooks, engagement bait, and a pinned summary tweet. Use when you need to break down ideas into a compelling multi-tweet thread.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add SkyyRoseLLC/DevSkyy --skill twitter-thread --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Twitter Thread?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/skyyrosellc-twitter-thread-devskyy)More formats (shields.io, HTML) on the badges page.
---
name: twitter-thread
description: "Creates viral-format Twitter/X threads with numbered hooks, engagement bait, and a pinned summary tweet. Use when you need to break down ideas into a compelling multi-tweet thread."
allowed-tools: Read Write Glob
metadata:
author: matthewhitcham
version: "1.0"
---
# Twitter Thread
## When to Use This Skill
Use this skill when you need to:
- Write a multi-tweet thread that breaks down a concept, story, or framework
- Create a thread designed for high engagement and retweets on X/Twitter
- Repurpose long-form content into a thread format
- Build authority on X/Twitter through educational or storytelling threads
**DO NOT** use this skill for single tweets, Twitter ad copy, or DM templates. This is for threads of 5-20 tweets.
---
## Core Principle
EVERY TWEET IN A THREAD MUST DELIVER VALUE ON ITS OWN — IF A READER STOPS AT ANY TWEET, THEY SHOULD HAVE LEARNED SOMETHING.
---
## Phase 1: Brief
### Required Inputs
| Input | What to Ask | Default |
|-------|------------|---------|
| **Topic** | "What is this thread about?" | No default — must be provided |
| **Thread type** | "Story, framework, listicle, myth-busting, or how-to?" | Framework |
| **Target audience** | "Who should share this?" | Entrepreneurs and business-minded professionals |
| **Thread length** | "How many tweets? (5-20)" | 10 tweets |
| **CTA** | "What should people do at the end? Follow, visit link, reply?" | Follow for more |
| **Source material** | "Do you have a blog post, notes, or outline to base this on?" | None — write from scratch |
**GATE: Confirm brief before proceeding.**
---
## Phase 2: Outline
### Thread Architecture
Every thread follows this structure:
1. **Hook tweet** — the first tweet that stops the scroll
2. **Context tweet** — why this matters (tweet 2)
3. **Body tweets** — the meat of the thread (tweets 3 through N-2)
4. **Summary tweet** — recap the key points (second-to-last)
5. **CTA tweet** — tell them what to do (final tweet)
### Outline Format
```
**Hook:** [First tweet — must stop the scroll]
**Context:** [Why this matters — tweet 2]
**Body tweets:**
- Tweet 3: [Point 1]
- Tweet 4: [Point 2]
- Tweet 5: [Point 3]
...
**Summary:** [Recap key points]
**CTA:** [Follow / link / reply prompt]
```
**GATE: Wait for approval before writing full tweets.**
---
## Phase 3: Write
### Tweet-by-Tweet Rules
**Hook Tweet (Tweet 1)**
- Must be under 280 characters — no exceptions
- Use one of these proven formats:
- "I [did X thing] in [time period]. Here's what I learned:"
- "[Bold claim or surprising stat]. A thread on [topic]:"
- "[Number] [things] about [topic] I wish I knew [time] ago:"
- End with a thread indicator: "(thread)" or "A thread:"
**Context Tweet (Tweet 2)**
- Explain why the reader should care
- Add credibility: personal experience, data, or stakes
- Keep under 280 characters
**Body Tweets (Tweets 3 to N-2)**
- One idea per tweet — never two
- Start each tweet with a number or bold opening
- Use line breaks for readability
- Include at least one tweet with a concrete example or mini-story
- Vary format: some tweets are lists, some are statements, some are questions
**Summary Tweet (Second-to-Last)**
- "TL;DR:" or "To recap:" followed by the key points
- Designed to be screenshotted and shared
**CTA Tweet (Final)**
- Single clear action
- If asking for a follow: "Follow @handle for more [topic] breakdowns"
- If linking: put the link here (not mid-thread — kills engagement)
- Ask for a retweet of the first tweet to boost reach
### Formatting Rules
| Rule | Detail |
|------|--------|
| **Character limit** | Every tweet must be under 280 characters |
| **Numbering** | Number body tweets: "3/ Point here" |
| **Line breaks** | Use blank lines between ideas within a tweet |
| **Emojis** | Use sparingly — 0-1 per tweet as visual markers, not decoration |
| **Hashtags** | Zero in the thread body. Add 1-2 to the final tweet only |
| **Links** | Only in the final tweet unless the thread is specifically about a resource |
---
## Phase 4: Polish
### 1. Thread Quality Checklist
```
## Thread Checklist
- [ ] Hook tweet stops the scroll (would you click "show this thread"?)
- [ ] Every tweet is under 280 characters
- [ ] Each tweet delivers one clear idea
- [ ] Body tweets are numbered consistently
- [ ] At least one tweet contains a specific example or story
- [ ] Summary tweet works as a standalone screenshot
- [ ] CTA tweet has a single clear action
- [ ] No links mid-thread (only in final tweet if needed)
- [ ] Thread reads well as a continuous narrative
- [ ] No tweet requires reading the previous tweet to make sense
```
### 2. Pinned Tweet Suggestion
Write an alternative version of the hook tweet optimized as a pinned tweet on the author's profile.
### 3. Posting Notes
- Best times: 8-10 AM or 5-7 PM in target audience's timezone
- Post tweet 1, then remaining tweets 1-2 minutes apart
- Reply to the hook tweet with the thread to keep it connected
- Quote-tweet the hook 6-8 hours later with a single key insight to resurface
---
## Example: "7 Pricing Mistakes That Cost Me $100K" (10-tweet thread)
```
1/ I've made every pricing mistake in the book.
Over 5 years, these 7 errors cost me at least $100K.
Here's what I'd do differently (thread):
2/ First, some context:
I run a service business. Started at $50/hr.
Now our minimum project is $10K.
Every mistake below happened because I didn't understand value.
3/ Mistake 1: Pricing by the hour
Hourly rates punish efficiency.
The faster you get, the less you earn.
Fix: Price by the outcome, not the clock.
4/ Mistake 2: Not raising prices annually
...
```
---
## Anti-Patterns
- **Tweet 1 is boring** — if the hook does not create curiosity or tension, the thread dies immediately. Rewrite until it passes the "would I click?" test.
- **Wall-of-text tweets** — a 280-character block of text is unreadable. Use line breaks.
- **Links in the middle** — mid-thread links kill engagement. Twitter suppresses them and readers bounce.
- **No numbering** — unnumbered threads feel disorganized and are hard to reference.
- **Repeating the same format** — if every body tweet is "Lesson N: [statement]" it gets monotonous. Mix formats.
- **Thread over 20 tweets** — attention drops sharply after tweet 15. Cut or split into two threads.
---
## Recovery
- **No hook ideas:** Generate 5 hook variants using different formats (story, stat, bold claim, question, list). Let the user pick.
- **Thread too long:** Cut body tweets that overlap or combine two related points into one tweet.
- **Topic too broad:** Narrow to a specific angle. "Marketing tips" becomes "7 email subject line formulas that doubled my open rate."
- **No personal experience:** Frame as curated wisdom: "I studied 50 viral threads. Here are the 7 patterns they all share."
- **Character count issues:** Rewrite long tweets by cutting filler words, using shorter synonyms, or splitting into two tweets.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!