Twitter/X Thread Creation

Write high-engagement Twitter/X threads via inference.sh CLI.

Quick Start

CODEBLOCK0

Install note: The install script only detects your OS/architecture, downloads the matching binary from dist.inference.sh, and verifies its SHA-256 checksum. No elevated permissions or background processes. Manual install & verification available.

Character Limits

Element	Limit
Tweet text	280 characters (free), 25,000 (Premium)
Thread length

No limit (10-15 tweets is sweet spot) | | Image alt text | 1,000 characters | | Quote tweet addition | 280 characters | | Reply | 280 characters | | Display name | 50 characters |

Thread Structure

The Anatomy

CODEBLOCK1

Tweet 1: The Hook

This tweet lives or dies alone in the timeline. It must work WITHOUT the thread.

Hook Type	Template
I did X + result	"I analyzed 1,000 [things]. Here's what I found:"
Number + list

"10 [topic] tips that [benefit]:" |
| Contrarian | "Unpopular opinion: [bold take]" |
| Story opener | "In 2019, I [dramatic event]. Here's what happened:" |
| How-to promise | "How to [achieve outcome] (step by step):" |
| Surprising fact | "[Stat that seems wrong]. Let me explain:" |

CODEBLOCK2

Content Tweets (3-9)

Rule	Why
One idea per tweet	Clarity and retweetability
Number them (1/, 2/, etc.)

Progress signal, easy to reference | | Each tweet should stand alone | People share individual tweets | | Lead with the insight | Don't bury the point | | Use line breaks | Visual breathing room | | Include examples | Abstract → concrete |

CODEBLOCK3

Closing Tweet

CODEBLOCK4

Formatting Rules

Tweet Formatting

CODEBLOCK5

Symbols for Lists

Symbol	Use For
→	Steps, actions, directions
•

Bullet points, lists | | — | Asides, attributions | | ✅ | Do's, positives | | ❌ | Don'ts, negatives | | 1/ 2/ 3/ | Numbered thread tweets |

Line Break Strategy

CODEBLOCK6

Line breaks create pacing. Use them to control reading speed and emphasis.

Media in Threads

When to Add Images

Tweet Position	Image Type	Purpose
Hook (tweet 1)	Eye-catching graphic	Stop the scroll
Key points

Screenshots, examples | Evidence | | Summary | Infographic | Shareable recap |

CODEBLOCK7

Image Specs

Format	Dimensions	Max Size
Single image	1200 x 675 (16:9) recommended	5 MB
Two images

700 x 800 each | 5 MB each | | Four images | 600 x 600 each | 5 MB each | | GIF | 1280 x 1080 max | 15 MB |

Thread Types

Educational

CODEBLOCK8

Story/Journey

CODEBLOCK9

Curation/List

CODEBLOCK10

Teardown/Analysis

CODEBLOCK11

Engagement Strategy

Action	Timing	Why
Post hook tweet	Peak hours (8-10 AM, 12-1 PM your audience's TZ)	Maximum initial visibility
Reply-chain the thread

Immediately after hook | Complete the thread | | Pin the thread | Right after posting | Visitors see your best work | | Engage with replies | First 60 minutes | Algorithm boost | | Quote-tweet highlight | Next day | Second wave of visibility | | Repost hook | 1-2 weeks later | Catch new followers |

Repurposing to Thread

CODEBLOCK12

Common Mistakes

Mistake	Problem	Fix
Weak hook tweet	Thread dies at tweet 1	Use hook formulas — bold, specific, curiosity-driving
Too many tweets (20+)

Readers drop off after 10-12 | Sweet spot is 8-12 tweets | | Multiple ideas per tweet | Confusing, not retweetable | One idea = one tweet | | No numbers on tweets | Hard to follow, no progress signal | Always number: 1/, 2/, 3/ | | No images | Threads with images get 2x engagement | Add visuals to hook + key points | | Thread only (no standalone) | Miss the non-thread audience | Post standalone tweets too, not just threads | | No CTA at the end | Missed follow/engagement opportunity | Always ask to RT, follow, bookmark | | Posting at wrong time | Low initial engagement kills reach | Post during your audience's peak hours | | Wall of text tweets | Nobody reads dense tweets | Line breaks, symbols, short sentences |

Related Skills

CODEBLOCK13

Browse all apps: INLINECODE1