# X Thread

> Turn an idea, article, or notes into a well-structured X (Twitter) thread. Use when the user wants to write a thread, asks "make this into a thread", "thread-ify this", has long content that won't fit one post, or wants thread structure advice. Returns a numbered thread with a standalone first post.

- Skill: `lxyang20131208-star/x-thread` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lxyang20131208-star/x-thread`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lxyang20131208-star/x-thread/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lxyang20131208-star (https://skillmd.com/u/lxyang20131208-star)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lxyang20131208-star/x-thread

---


# x-thread — Thread Architect

Read `reference/ALGORITHM.md` if available. The key fact for threads:

> **Only the first post is ranked and distributed.** Phoenix scores T1 as a candidate.
> Every later post in the thread reaches only the subset of people who engaged with T1.

So a thread is a **dwell-time amplifier**, not a reach amplifier. T1 does the reaching;
the rest does the depth. Design accordingly.

## What you need from the user

The raw material (notes, an article, a transcript, a brain-dump) and the niche/audience.
Any external link they want to include.

## How to build the thread

1. **T1 must stand alone as a viral post.** It has to work for someone who never reads
   T2. Apply hook discipline: one concrete entity minimum, no `🧵`, no "thread below",
   stops a scroll on its own. T1 should promise a specific payoff the thread delivers.

2. **Length: 5–9 posts is the sweet spot.** Beyond ~12 the drop-off is steep. If the
   material won't compress to 9, it's two threads or a long-form post — say so.

3. **One idea per post.** Each post should be skimmable in isolation. Front-load the point,
   then support it. Break every 1–2 sentences with a line break.

4. **Entity density throughout.** Names, numbers, tools, screenshots. This keeps dwell
   high and gives the thread a sharp topic signal.

5. **Links go in a self-reply, never in T1 or mid-thread body.** End the thread with a
   final post, then a separate reply with the link ("Full write-up: <link>"). Putting a
   link in T1 weakens the post that has to do all the distribution work.

6. **Last post = identity + soft CTA.** The final post is where `follow_author` converts:
   one line on who you are and what you do, and a low-friction ask ("I write about X —
   follow if useful" or "what would you add?"). No hard sell.

7. **Media:** put the strongest screenshot/visual in T1 or T2. Aspect ratio 1:1, 4:5,
   or 9:16 — never 16:9 (it gets cropped in-feed).

## Output format

```
Thread (N posts):

1/ <T1 — standalone hook post>

2/ <...>
...
N/ <final post — identity + soft CTA>

↳ reply: <link, if any>

Notes:
- Why T1 works: <one line>
- Posting tip: <e.g. reply to your own thread / engage first hour>
```

## Rules

- Never invent facts, numbers, or quotes not in the user's material.
- If the material is too thin for a thread, recommend a single post instead — don't pad.
- Don't add a post just to hit a count. Every post must earn its place.
- Keep the user's voice. You are structuring their content, not replacing it.