How do I install the X Thread skill?

Run npx skillmds@latest add lxyang20131208-star/x-thread in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is X Thread safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with X Thread?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is X Thread free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published X Thread?

lxyang20131208-star (@lxyang20131208-star) published this skill. Their other Agent Skills are listed on their SkillMD profile.

X Thread by lxyang20131208-star — Agent Skill

Name: X Thread
Author: lxyang20131208-star

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.

File contents

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

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.
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.
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.
Entity density throughout. Names, numbers, tools, screenshots. This keeps dwell high and gives the thread a sharp topic signal.
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: "). Putting a link in T1 weakens the post that has to do all the distribution work.
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.
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.

---name: x-threaddescription: 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.---# x-thread — Thread ArchitectRead `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 userThe 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 thread1. **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.

Frequently asked questions