• 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

.agents/social-media-context-sms.md

"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."

• 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

• Apply hook-writer-sms patterns (contrarian, question, story opener, statistic, bold claim, empathy, before/after, confession)
• 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

• 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
• 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

• 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

• 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

• 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

• 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

7/ The takeaway:

This post worked because it did 3 things most posts don't:
→ Led with a specific, surprising number
→ Showed the work, not just the result
→ Made the reader feel like they could do it too

That's the formula. Save this thread and use it on your next post.

Follow @handle for one content breakdown every week.

• 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

• 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

1/ Stop posting every day. It's actively hurting your growth.

Here's the data: 🧵

2/ I tracked 200 accounts for 6 months.

The ones posting daily averaged 1.8% ER.
The ones posting 3x/week averaged 4.3% ER.

More isn't better. Better is better.

3/ Why?

Daily posting forces you to fill slots.
3x/week lets you choose your best ideas.

The algorithm rewards engagement rate, not volume.

• 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

• 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

• Vary post length intentionally — a long explanatory post lands harder after two short punchy ones
• Use short punchy posts as palate cleansers — one-liners between heavier posts reset the reader's attention
• End posts on curiosity — "But here's where it gets interesting…" or an unresolved question pulls the reader to the next post
• Don't resolve too early — if you give away the core insight in post 3 of a 10-post thread, the rest feels like filler; pace the payoff
• Number posts explicitly on X — readers need to know how far they are and how much is left

"Want me to schedule this thread? I can queue it for your next available slot or set a specific time."

create_post

• Hook stands alone — would this first post perform without the thread?
• One idea per post — no post tries to do two jobs
• Transitions are present — each post flows into the next
• Posts are numbered — on Twitter/X, every post has its number
• Closer has a CTA — the reader knows exactly what to do after finishing
• Length matches platform — 280 chars on X, longer on LinkedIn, conversational on Threads
• Voice is consistent — sounds like the user, not a generic expert

• Does not write single standalone posts — see post-writer-sms for short-form content
• Does not write carousels or slide decks — see carousel-writer-sms for slide-by-slide content
• Does not analyze post performance or metrics — see performance-analyzer-sms for analytics
• Does not define content strategy or decide what to post — see content-strategy-sms for planning
• Does not execute code or access external APIs unless BlackTwist MCP is connected
• Does not produce visual design or images — output is text copy for each thread post only

• social-media-context-sms — establish voice, pillars, and platform preferences before writing
• hook-writer-sms — generate and test opening lines before threading
• platform-strategy-sms — decide which platform to prioritize and why
• post-writer-sms — write a single post when the idea doesn't need a thread