agentleFS
lxyang20131208-starlxyang20131208-star/x-algorithm-skills/skills/x-thread/SKILL.md

x-thread

Skill1 starsChanged 6 months agoMITView on GitHub

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.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. Jakeschincariol/x-agent-skill★ 4same name
    2. belzoralolbtw/x-agent-skill★ 0same name
    3. swayamdhawan/x-agent★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read reference/ALGORITHM.md if available.

    line 8
  2. Distinctive:

    Media: put the strongest screenshot/visual in T1 or T2.

    line 44
  3. Distinctive:

    Never invent facts, numbers, or quotes not in the user's material.

    line 67
  4. Distinctive:

    If the material is too thin for a thread, recommend a single post instead — don't pad.

    line 68
  5. Distinctive:

    Don't add a post just to hit a count.

    line 69
  6. Distinctive:

    Keep the user's voice. You are structuring their content, not replacing it.

    line 70

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.