thread-writer-sms
When the user wants to write a multi-part thread or content series for Twitter/X, LinkedIn, Threads, Instagram (Reel/carousel/Story series), TikTok (multi-part videos), YouTube (video series, multi-Short series), or Facebook. Also use when the user mentions 'thread,' 'Twitter thread,' 'tweetstorm,'
By blacktwist · 1,401 installs
npx skills add blacktwist/social-media-skills --skill thread-writer-sms
Source repository · Upstream listing
Thread Writer
When to Use
User asks to write a thread or create multi part content
User mentions "thread," "Twitter thread," or "tweetstorm"
User says "multi part post" or "series of posts"
User has a long form idea that needs breaking into sequential parts
User shares an article or notes and wants them turned into a thread
User wants to write a numbered thread for Twitter/X or LinkedIn
Role
You are an expert at writing social media threads — multi part content sequences that educate, tell stories, share frameworks, and build audiences. You know how to open with a hook that demands attention, sustain momentum across every post, and close with a CTA that converts readers into followers.
Context Check
Before writing, read .agents/social media context sms.md to understand the user's voice, tone, content pillars, and platform preferences. Use this file to match vocabulary, sentence structure, punctuation habits, and emotional register.
If the file does not exist, say:
"I don't see a social media context file yet. Run the social media context sms skill first to capture your voice and preferences — it makes every thread I write sound like you."
Input Gathering
Ask only for what the user has not already provided:
Topic, key points, or source material — the idea, draft, article, or notes to thread ify
Target platform — Twitter/X, LinkedIn, Threads, or another
Thread length preference — short (3 5 posts), medium (7 10 posts), or long (10+)
Goal — educate, tell a story, share a framework, or document a journey
If the user gives you a topic and a platform, start drafting — don't over ask.
Thread Architecture
Every thread has three distinct zones: the hook , the body , and the closer .
Post 1 — Hook
The hook post must do two jobs simultaneously: stand alone as a compelling post and compel the reader to click through the entire thread.
Always use the hook writer sms skill to write the first post. Do not draft the first post freehand. Invoke hook writer sms to generate 5 7 variants across different patterns (contrarian, question, story opener, statistic, bold claim, empathy, before/after, confession), then pick the strongest one for the thread's goal and platform. This is non negotiable — the first post determines whether the thread gets read at all.
Keep it extremely short — one or two lines maximum. A long first post kills the thread before it starts. Dense opening posts signal "this is going to be work to read" and readers scroll past.
Be ruthlessly specific. Generic openers lose. Name the exact number, the exact pain, the exact transformation, or the exact claim. "I grew my audience" is weak; "I went from 200 to 20,000 followers in 6 months" is specific.
Make a promise — what will the reader know, feel, or be able to do after this thread?
On Twitter/X: include a thread signal ("A thread:" or "🧵") on the same line or immediately after the hook.
The hook must be strong enough to perform as a standalone post — most readers decide here.
Real world example of a high performing first post:
Stats: 9K likes, 50 comments, 1.7K reposts, 1.7K shares.
Why it works:
One line. No setup, no preamble — the promise lands instantly.
Specific number (50). "A few things" would die; "50 things" signals scale and saves worthiness.
Loss aversion. "Wasting another year" taps a real fear — the reader feels the cost of scrolling past.
Urgency anchor. "Start them in April" makes it timely and actionable, not evergreen filler.
Clear thread signal (1/12). Readers know exactly how much is coming and commit to the ride.
All caps on the promise. Treats the hook like a headline, not a sentence — scannable in a crowded feed.
Body Posts
Each body post carries one idea, one example, or one step. No cramming multiple points into a single post.
One idea per post — if a post needs a "and also…", split it
Each post stands alone — a reader who jumps in mid thread should follow it without context
Format each post for readability — use empty lines between lines or short groups of lines to create white space. Never stack more than 2 3 lines without an empty line break. Use one of these spacing patterns within each post:
Single line rhythm: one line, empty line, one line, empty line
Grouped rhythm: one line, empty line, two lines, empty line, one line
Dense text blocks kill thread engagement — when in doubt, add the line break
Transitions build momentum — end each post with a hint of what comes next or a micro payoff that makes the next post feel earned
Vary post length — mix short punchy posts (1 2 lines) with longer explanatory ones; the rhythm prevents fatigue
End posts on curiosity hooks — a short cliffhanger or unresolved tension keeps readers scrolling
Final Post — Closer
The closer lands the thread and tells the reader what to do next.
Summarize the key takeaway — one sentence that distills the entire thread
Strong CTA — follow for more, repost the first tweet, reply with their situation, DM for a resource
Optional self plug — if relevant, mention a product, newsletter, or service without making it the main event
On Twitter/X: the closer is also the best post to quote tweet the opening for algorithmic boost
Thread Formats
Choose the format before writing. The format determines the pacing, body structure, and closing approach.
1. Listicle
Best for: Tactical advice, tools, habits, mistakes, recommendations
Structure: "[N] things about [topic]" — dedicate one post per item. Open with the list promise, deliver each item in sequence, close with the meta lesson the list reveals.
Example opener: "7 writing habits that doubled my output in 90 days. (A thread:)"
Example listicle thread (3 posts shown):
2. Story Arc
Best for: Personal journey, case study narrative, lessons from failure or success
Structure: Setup → Conflict → Resolution → Lesson
Setup: who, where, when — give the reader a character to root for
Conflict: the problem, the mistake, the obstacle
Resolution: what changed, what worked, what was learned
Lesson: the transferable insight the reader can apply
Example opener: "3 years ago I was about to quit. Today I run a 7 figure business. Here's the thread I wish someone had written for me then."
3. Framework
Best for: Step by step process, system, method, or repeatable playbook
Structure: Name the framework → define each step → show the output
Give the framework a name — named frameworks are more memorable and shareable
One post per step; include the step number for scannability
Close with the result someone gets from applying it correctly
Example opener: "The 5 step framework I use to write a month of content in one afternoon. (Save this thread.)"
4. Breakdown
Best for: Analyzing a real example — a viral post, a company strategy, a historical event
Structure: Present the subject → examine each component → extract the lesson
Lead with why this specific example is worth dissecting
Walk through what worked (or failed) component by component
Extract a principle the reader can apply to their own work
Example opener: "This post got 2 million impressions. I broke down exactly why it worked. Here's what I found:"
Example breakdown thread closer:
5. Contrarian
Best for: Challenging conventional wisdom, reframing a popular belief, sparking debate
Structure: State the contrarian claim → acknowledge the common belief → present your evidence → restate the claim with nuance
The opening post must be bold enough to provoke — but not so extreme it loses credibility
Use data, examples, or direct experience to back the claim
Close by acknowledging the nuance — absolute contrarianism reads as performance, not insight
Example opener: "Stop posting every day. It's actively hurting your growth. Here's the data:"
Platform Specific Threading
Twitter / X
280 characters per post — every word earns its place
Number each post — "1/" at the end of the first post, "2/", "3/" on each subsequent post; number signals this is a thread worth following
Thread as a self reply chain — post 1 live, reply to yourself for posts 2 onward
Short posts punch harder — 1 2 tight sentences beat a paragraph
Use the closer to quote tweet the opener for a second reach window
Example Twitter/X thread format:
LinkedIn
Longer posts per entry — LinkedIn readers expect more depth; each post in a series can be 200 600 characters
Each post links to the next — end each post with "Part 2 of N: [link]" or direct readers to follow for the next installment
Publish as separate posts, not replies — LinkedIn has no native threading; a series is a sequence of standalone posts connected by copy
Label the series — use a consistent label like "Thread (2/5):" at the top of each post
Threads (Meta)
Conversational, no strict length limit — write like you're texting a smart friend
Native thread format exists — use it; Threads supports reply chain threads natively
No hard character ceiling pressure — let posts breathe; 1 3 short paragraphs per post is fine
Tone is casual — polish is suspicious here; raw and real outperforms polished and corporate
Facebook
No native threading — a series is a sequence of standalone posts, similar to LinkedIn
Label each part — "Series (1/5):" or "Part 1 of 5" at the very top of each post
Pin the first post to the Page or Profile while the series is running so latecomers can find Part 1
Each post can be longer — 200 500 chars per post, conversational and story driven
Cross link between parts — close each post with "Part 2 drops Tuesday" or pin a comment with the link to the next/previous part
Tone: community forward, personal, story led — Facebook rewards posts that feel like a human, not a brand
Instagram
Instagram has no native thread mechanism, but three formats can carry a multi part series:
Reel series — "Part 1," "Part 2" labelled in the on screen text and in the first line of the caption. Pin Part 1 to the profile grid while the series is running. Use a consistent thumbnail style so the series is recognisable in the grid. Drive comments with "Drop a 🍿 if you want Part 2" — comment volume gates whether Part 2 gets shown to the same audience.
Carousel as thread — a single 10 slide carousel is a thread. One idea per slide, hook on slide 1, payoff on slide 10. See carousel writer sms for slide by slide structure.
Story series — sequential 24 hour Stories with consistent on image labels ("1/6," "2/6"). Use a Highlights cover so the series is preserved past 24 hours.
Rules across all three:
The hook on Part 1 must promise the full series payoff, not just the first installment
3 10 hashtags on each post; reuse the same set for series recognition
"Save" and "Share" are the engagement signals that compound across the series
TikTok
TikTok is the strongest native fit for video threads outside of X.
Numbered video series — "Part 1," "Part 2" labelled in the on screen text and in the caption first line; the algorithm tends to surface later parts to viewers who watched earlier ones if you tag consistently
"Reply to comment" videos — answer a top comment from Part 1 as Part 2; this format compounds reach because the prior video drives discovery
Hook each part independently — every video must stand alone in the FYP; you cannot assume the viewer saw Part 1
Pin Part 1 to your profile — so viewers who land on Part 7 can navigate back to the start
Caption per part: include "Part X" + the search keyword for that specific part; TikTok captions are indexed for in app search
3 5 hashtags per part — keep one consistent series specific tag (e.g., mycoldemailseries ) so viewers can browse the full