X thread

Skill lxyang20131208-star/x-algorithm-skills/skills/x-thread

Claude Code skills for growing on X (Twitter), built on the open-source xai-org/x-algorithm (Phoenix) code — audit, write, and reverse-engineer posts the way the algorithm actually ranks them.

Install

npx -y skills add lxyang20131208-star/x-algorithm-skills --skill x-thread

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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

2.8 KB, as published. Nobody here has run it

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: <link>"). 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.