SkillMedev Tweet Thread Builder
Threads live or die on the first post: 90%+ of potential readers see only the hook, so a mediocre hook wastes every good post behind it. The costly mistake is spreading one thin idea across fifteen posts or burying the payoff behind "a thread 🧵" with no substance. Earn each scroll.
Operating procedure
Step 1: Gather inputs
- The single idea or story - one sentence. If the user gives several, pick the one with the most concrete specifics (numbers, names, before/after); park the rest.
- The payoff for the reader: what they know or can do after reading.
- Proof material: numbers, screenshots, examples. A thread without at least two concrete specifics is an opinion, not a thread - send the user back for material.
- The one CTA (default: follow; alternatives: a link, or "reply with your version").
Label any number the user estimates as an estimate.
Step 2: Write the hook (post 1) - and an A/B pair
- Promise a specific payoff: a number, a transformation, a contrarian take.
- No preamble. The first line is the whole pitch. Keep the hook under 200 characters - dense hooks read as work.
- Proven patterns: "I did X for N days. Here's what happened." / "Everyone believes X. They're wrong." / "N lessons from [hard thing]:"
Always draft two hooks with different mechanisms so the user can pick or test:
- A (curiosity/story): "I deleted 80% of our landing page. Signups went up 34%. What we removed:"
- B (contrarian/claim): "Long landing pages are killing your signups. We cut ours to one screen and grew 34%. Proof:"
Same material, different bet: A sells the mystery of what was removed; B sells the argument. Pick A for story-driven audiences, B when the take itself is polarizing enough to drive replies.
Step 3: Outline the beats
- One idea per post. If a post has two ideas, split it. If two posts share one idea, merge them.
- 5-12 posts is the sweet spot. Under 5, make it a single tweet; over 12, cut - every post past 12 sheds readers faster than it adds value.
- Order the beats so each ends on a small open loop that the next post resolves; momentum is the structure.
Step 4: Write the body posts
- Make it concrete: examples, numbers, and specifics over abstractions.
- Short lines and white space; threads are read on phones.
- Front-load each post - the first line of every post is a mini-hook.
Step 5: Write the close
- Restate the single takeaway in one post.
- One CTA only. Optional: a one-line summary post people can quote-tweet.
Step 6: The scroll test
Read the thread top to bottom once in one sitting. At any post where you would stop scrolling, fix that post or cut it. Then check the numeric guardrails: 5-12 posts, hook under 200 characters, at least two concrete specifics across the body, exactly one CTA.
Worked example thread (6 posts)
1/ I sent 200 cold emails with a 2% reply rate.
Rewrote one sentence. Reply rate hit 11%.
The sentence, and why it worked:
2/ The old opener: "Hi, I'm the founder of [company], we help teams do X."
Nobody cares who you are in sentence one.
They care whether you know THEM.
3/ The new opener: "Saw you're hiring 3 SDRs - usually means outbound
is working but reporting is a mess."
One observed fact + one inferred pain. That's it.
4/ Why it works: it proves 30 seconds of research.
2% of cold email gets replies because 98% of it could be
sent to anyone. Specificity is the whole game.
5/ The formula: [thing you observed about them] + [what that
usually means] + one-sentence ask.
Under 60 words total. No deck attached.
6/ Takeaway: your first sentence should be about them, not you.
Steal the formula, run 50 sends, check your reply rate.
Follow @[handle] - I share one outbound experiment a week.
Why it passes: 6 posts (in range), hook is 118 characters with two numbers and an open loop, every post carries exactly one idea, posts 1-5 each end pulling toward the next, and the close restates the takeaway with one CTA.
Deliverable
Produce a numbered, post-by-post thread draft containing: two hook variants labeled A and B, 5-12 body posts each carrying one idea, a closing post with the takeaway and one CTA, and a one-line note on which hook to prefer and why.
Do NOT
- Do not open with "A thread 🧵" and no substance - the hook must contain the promise, not announce the format.
- Do not exceed one idea per post; splitting is free, cramming costs readers.
- Do not stack CTAs (follow + link + reply) - each added ask cuts response to all of them.
- Do not pad to hit a post count; a tight 6 beats a padded 12 every time.
- Do not write abstractions where the user has numbers - "grew a lot" when the material says "34%" is malpractice.
Quality bar
- Hook under 200 characters, contains a specific payoff, and would stop your own scroll.
- 5-12 posts, one idea each, at least two concrete specifics in the body.
- Every post's last line creates pull toward the next.
- Exactly one CTA; the takeaway is stated, not implied.
- The thread survives the top-to-bottom scroll test with zero stop-points.
To adapt the finished thread into a LinkedIn post, newsletter section, or other formats, route to content-repurposing; for a native LinkedIn version written from scratch, use linkedin-post-writer.