Skip to main content
Version History
v2.0.0
Latest
Breaking
No changelog provided
Jul 20, 2026
363 downloads100/100
v1.0.0
No changelog provided
Mar 7, 2026
363 downloads100/100
Compare Versions
View differences between any two versions of this skill.
From:
→To:
+207
-23
SKILL.md
| 1 | 1 | --- | |
| 2 | 2 | name: creating-twitter-threads | |
| 3 | - | description: Writes educational Twitter/X threads that get shared. Use when you need assistance with creating twitter threads. | |
| 3 | + | version: 2.0.0 | |
| 4 | + | description: Write an educational X/Twitter thread engineered for shares and bookmarks. Use when turning an idea, framework, or lesson into a multi-tweet thread that spreads. | |
| 5 | + | category: marketing | |
| 6 | + | license: MIT | |
| 4 | 7 | --- | |
| 5 | 8 | ||
| 6 | - | # Creating Twitter Threads | |
| 9 | + | # Creating Twitter (X) Threads | |
| 7 | 10 | ||
| 8 | - | Writes educational Twitter/X threads that get shared | |
| 11 | + | A thread lives or dies on the first tweet. If the hook does not stop the scroll, tweets 2–10 are never seen — the algorithm only pushes a thread that earns dwell time, bookmarks, and reposts on the hook. Optimize the hook first, then build a spine where every tweet is one self-contained idea. | |
| 9 | 12 | ||
| 10 | - | ## Viral Potential: ⭐⭐⭐⭐⭐ | |
| 13 | + | ## The One Rule Everything Serves | |
| 11 | 14 | ||
| 12 | - | **⭐ FEATURED SKILL** - Top 10 in ${category.name} | |
| 15 | + | **The hook tweet is ~90% of performance.** You can write nine perfect body tweets, but if the hook gets 200 impressions, nothing downstream matters. Spend half your effort on tweet 1. Write 10 hook variants and keep the best one. | |
| 13 | 16 | ||
| 14 | - | ## When to Use | |
| 17 | + | ## Hook Formulas (write 3–5, pick 1) | |
| 15 | 18 | ||
| 16 | - | - Writes educational Twitter/X threads that get shared | |
| 19 | + | Each hook must promise a specific payoff and open a loop. No hashtags, no links, no @mentions in the hook — they suppress reach and give the eye an exit. | |
| 17 | - | - Working on related social media tasks | |
| 18 | - | - Need expert guidance on creating twitter threads | |
| 19 | 20 | ||
| 20 | - | ## Instructions | |
| 21 | + | 1. **Number-driven / listicle** | |
| 22 | + | `I analyzed 500 viral threads. 7 patterns showed up every single time:` | |
| 23 | + | Specific number > round number. "47 tools" beats "many tools." | |
| 21 | 24 | ||
| 22 | - | 1. Understand the context and requirements | |
| 25 | + | 2. **Curiosity gap** (withhold the mechanism) | |
| 23 | - | 2. Apply best practices for creating twitter threads | |
| 26 | + | `Most founders write threads that flop. The fix takes 4 words and almost nobody uses it.` | |
| 24 | - | 3. Provide actionable recommendations | |
| 25 | - | 4. Iterate based on feedback | |
| 26 | 27 | ||
| 27 | - | ## Examples | |
| 28 | + | 3. **Contrarian / pattern interrupt** (attack accepted wisdom) | |
| 29 | + | `"Post daily to grow." Terrible advice. Here's what actually took my account from 800 to 60k:` | |
| 28 | 30 | ||
| 29 | - | ### Example: Basic Request | |
| 31 | + | 4. **Transformation / before→after** (proof of outcome) | |
| 30 | - | User: "Help me with creating twitter threads" | |
| 32 | + | `18 months ago: 300 followers, zero leads. Today my threads drive $40k/mo. The exact system:` | |
| 31 | - | Response: Provide tailored assistance based on the specific need. | |
| 32 | 33 | ||
| 33 | - | ## Guidelines | |
| 34 | + | 5. **"Steal this"** (generosity framing — high bookmark rate) | |
| 35 | + | `Steal my 6-part thread template. It's written 40+ threads that cleared 100k views:` | |
| 34 | 36 | ||
| 35 | - | - Follow industry best practices | |
| 37 | + | 6. **How-to / mistake** (name the pain) | |
| 36 | - | - Provide actionable, specific advice | |
| 38 | + | `You're not bad at writing threads. You're burying the hook in tweet 3. Fix it in 60 seconds:` | |
| 37 | - | - Consider the target audience | |
| 38 | - | - Iterate and refine based on feedback | |
| 39 | 39 | ||
| 40 | + | Levers that stack on any formula: | |
| 41 | + | ||
| 42 | + | - **Timeframe specificity**: "in 30 days", "by Friday", "in 4 words". | |
| 43 | + | - **End on a colon** so the reader knows a list/payoff follows. | |
| 44 | + | - **First line before "Show more"**: the punch must land in the first ~1 line; assume the rest is clipped on mobile. | |
| 45 | + | ||
| 46 | + | ## The 280-Character Constraint | |
| 47 | + | ||
| 48 | + | Every tweet caps at 280 characters (premium accounts get more, but write for 280 — clipped previews and quote-reposts still truncate). Treat the limit as a feature: it forces one idea per tweet. | |
| 49 | + | ||
| 50 | + | - **Self-contained beats**: each tweet must make sense if screenshotted alone. Reposters share single tweets, not whole threads. No "as I said above" or "and then" that depends on the previous tweet. | |
| 51 | + | - **Count characters, don't guess.** Aim for 200–260 so the tweet breathes and survives a quote-repost wrapper. | |
| 52 | + | - **Front-load the point.** First 5–7 words carry the idea; supporting detail follows. | |
| 53 | + | ||
| 54 | + | ## Thread Architecture | |
| 55 | + | ||
| 56 | + | ``` | |
| 57 | + | Tweet 1 → HOOK (stop the scroll; promise a payoff) | |
| 58 | + | Tweet 2 → PROMISE/SETUP (what they'll get + why you're credible, 1 line) | |
| 59 | + | Tweet 3–9 → VALUE (one idea per tweet, each a standalone beat) | |
| 60 | + | Final → RECAP + CTA (compress the thread, then ask for ONE action) | |
| 61 | + | ``` | |
| 62 | + | ||
| 63 | + | - **5–9 value tweets** is the sweet spot. Fewer feels thin; more loses completion. If you have 15 points, you have two threads. | |
| 64 | + | - **One idea per tweet.** If a tweet holds two ideas, split it. Density kills scannability. | |
| 65 | + | - **The recap tweet** restates the list in one glance — this is the tweet people bookmark and repost. Then a single CTA (follow, reply, or link-in-reply). Never stack three asks. | |
| 66 | + | ||
| 67 | + | ## Links Kill Reach — Put Them Last | |
| 68 | + | ||
| 69 | + | X suppresses distribution of posts with external links because it wants users to stay on-platform. Therefore: | |
| 70 | + | ||
| 71 | + | - **Zero links in tweets 1 through N-1.** A link mid-thread caps the whole thread's reach. | |
| 72 | + | - Put the link in the **final tweet OR (better) the first reply** to your own thread. Point to it: "Full guide 👇 (link in reply)". | |
| 73 | + | - Same logic applies to the hook: no link, no hashtag — the hook must be pure momentum. | |
| 74 | + | ||
| 75 | + | ## Formatting for Skim | |
| 76 | + | ||
| 77 | + | - **Line breaks over walls.** 1–3 short lines per tweet with blank lines between. Mobile readers skim; a dense block gets skipped. | |
| 78 | + | - **No hashtags in the hook** (and at most 0–1 anywhere; they read as spam and rarely aid discovery on X). | |
| 79 | + | - **One concept per tweet**, one visual per tweet max. A chart, screenshot, or GIF on your best 1–2 tweets lifts dwell time. | |
| 80 | + | - **Arrows, colons, and numbered beats** ("1/", "2/" or "→") give the eye rhythm and set a completion expectation. | |
| 81 | + | - **Emoji sparingly** as bullets or signposts, not decoration. | |
| 82 | + | ||
| 83 | + | ## Make It Bookmarkable | |
| 84 | + | ||
| 85 | + | Bookmarks are now a top-weighted signal — people bookmark what they intend to _use later_. Build tweets someone would save: | |
| 86 | + | ||
| 87 | + | - Templates, checklists, exact scripts, numbered steps, swipe copy. | |
| 88 | + | - A single "recap" tweet that holds the whole framework in one screen. | |
| 89 | + | - Specifics over vibes: "post 8:30am ET, Tue–Thu" beats "post consistently." | |
| 90 | + | ||
| 91 | + | ## Turn a Thread Into a Single Long Post | |
| 92 | + | ||
| 93 | + | Long-form posts (premium) often out-distribute threads now: they keep all dwell time on one post and dodge the reply drop-off. To convert: | |
| 94 | + | ||
| 95 | + | - Keep the **same hook** as line 1 — it still does 90% of the work. | |
| 96 | + | - Replace tweet breaks with **line breaks + subheads**; each former "tweet" becomes a short paragraph or bullet. | |
| 97 | + | - Move the link to the **end** or a reply (same link rule applies). | |
| 98 | + | - Keep it scannable: whitespace, short lines, one idea per block. | |
| 99 | + | - Rule of thumb: **thread** = you want reposts of individual beats; **long post** = you want max dwell + bookmarks and a cleaner read. | |
| 100 | + | ||
| 101 | + | ## Fully-Written Example Thread | |
| 102 | + | ||
| 103 | + | **Tweet 1 — Hook (number + steal-this)** — 88 chars | |
| 104 | + | ||
| 105 | + | ``` | |
| 106 | + | I've written 200+ threads. | |
| 107 | + | ||
| 108 | + | The ones that hit 100k+ views all follow the same 6-part skeleton. | |
| 109 | + | ||
| 110 | + | Steal it 👇 | |
| 111 | + | ``` | |
| 112 | + | ||
| 113 | + | **Tweet 2 — Promise / credibility** — 156 chars | |
| 114 | + | ||
| 115 | + | ``` | |
| 116 | + | No "growth hacks." No buying followers. | |
| 117 | + | ||
| 118 | + | Just structure — the reason most threads die is the shape, not the topic. | |
| 119 | + | ||
| 120 | + | Here's the shape: | |
| 121 | + | ``` | |
| 122 | + | ||
| 123 | + | **Tweet 3 — Value: the hook is everything** — 143 chars | |
| 124 | + | ||
| 125 | + | ``` | |
| 126 | + | 1. The hook is 90% of the result. | |
| 127 | + | ||
| 128 | + | If tweet 1 flops, tweets 2–10 don't exist. The algorithm never shows them. | |
| 129 | + | ||
| 130 | + | Write 10 hooks. Ship 1. | |
| 131 | + | ``` | |
| 132 | + | ||
| 133 | + | **Tweet 4 — Value: one idea per tweet** — 164 chars | |
| 134 | + | ||
| 135 | + | ``` | |
| 136 | + | 2. One idea per tweet. | |
| 137 | + | ||
| 138 | + | Each tweet should make sense screenshotted alone — because that's how people repost it. | |
| 139 | + | ||
| 140 | + | Two ideas in a tweet? Split it into two. | |
| 141 | + | ``` | |
| 142 | + | ||
| 143 | + | **Tweet 5 — Value: no links until the end** — 168 chars | |
| 144 | + | ||
| 145 | + | ``` | |
| 146 | + | 3. No links until the final tweet. | |
| 147 | + | ||
| 148 | + | X throttles reach on posts with external links to keep you on-platform. | |
| 149 | + | ||
| 150 | + | A link in tweet 4 caps the WHOLE thread. Park it last. | |
| 151 | + | ``` | |
| 152 | + | ||
| 153 | + | **Tweet 6 — Value: format for the thumb** — 130 chars | |
| 154 | + | ||
| 155 | + | ``` | |
| 156 | + | 4. Format for skimming. | |
| 157 | + | ||
| 158 | + | 1–3 short lines per tweet. | |
| 159 | + | Blank line between thoughts. | |
| 160 | + | No hashtags in the hook. | |
| 161 | + | ||
| 162 | + | Walls of text get scrolled. | |
| 163 | + | ``` | |
| 164 | + | ||
| 165 | + | **Tweet 7 — Value: make it saveable** — 167 chars | |
| 166 | + | ||
| 167 | + | ``` | |
| 168 | + | 5. Build for bookmarks. | |
| 169 | + | ||
| 170 | + | Bookmarks are a top signal now. People save what they'll USE: | |
| 171 | + | templates, scripts, checklists, exact numbers. | |
| 172 | + | ||
| 173 | + | Give them a reason to return. | |
| 174 | + | ``` | |
| 175 | + | ||
| 176 | + | **Tweet 8 — Value: the recap tweet** — 149 chars | |
| 177 | + | ||
| 178 | + | ``` | |
| 179 | + | 6. End with a recap tweet. | |
| 180 | + | ||
| 181 | + | Compress the whole thread into one screen — that's the tweet people bookmark AND repost. | |
| 182 | + | ||
| 183 | + | Then make ONE ask. Not three. | |
| 184 | + | ``` | |
| 185 | + | ||
| 186 | + | **Tweet 9 — Recap + CTA** — 187 chars | |
| 187 | + | ||
| 188 | + | ``` | |
| 189 | + | Recap: | |
| 190 | + | ||
| 191 | + | 1. Hook = 90% | |
| 192 | + | 2. One idea per tweet | |
| 193 | + | 3. Links last | |
| 194 | + | 4. Format for the thumb | |
| 195 | + | 5. Build for bookmarks | |
| 196 | + | 6. Close with a recap | |
| 197 | + | ||
| 198 | + | Follow @you for a thread breakdown weekly. | |
| 199 | + | ||
| 200 | + | Template 👇 (in reply) | |
| 201 | + | ``` | |
| 202 | + | ||
| 203 | + | **First reply (where the link goes)** — 76 chars | |
| 204 | + | ||
| 205 | + | ``` | |
| 206 | + | The fill-in-the-blank template I use for every thread: | |
| 207 | + | [your-link-here] | |
| 208 | + | ``` | |
| 209 | + | ||
| 210 | + | ## Common Mistakes | |
| 211 | + | ||
| 212 | + | - **Weak hook, strong body.** Backwards. Rewrite the hook 10 times before touching tweet 2. | |
| 213 | + | - **Link in the hook or mid-thread.** Instantly caps reach. Link goes last or in a reply. | |
| 214 | + | - **Hashtags in the hook.** Reads as spam, gives the eye an exit, adds no discovery on X. | |
| 215 | + | - **Two ideas crammed into one tweet.** Split them; density is not depth. | |
| 216 | + | - **A tweet that only makes sense in sequence** ("and that's why…") — it can't be reposted alone. | |
| 217 | + | - **Burying the payoff below "Show more."** Put the punch in line 1. | |
| 218 | + | - **12+ tweets.** Completion rate craters. That's two threads. | |
| 219 | + | - **Three CTAs at the end** (follow + like + link + DM). Pick one action. | |
| 220 | + | - **Round, vague numbers.** "A few tips" < "7 patterns." Specificity signals substance. | |
| 221 | + | - **No recap tweet.** You lose the single most bookmarked and reposted tweet in the thread. | |
| 222 | + | - **Post and ghost.** Reply to the first 5–10 comments within the first hour — early replies boost distribution. | |
| 223 | + |