x-thread-builder
Skill4 starsChanged 4 months agoMITView on GitHub
Builds an X (Twitter) thread — one scroll-stopping opener, 5–9 self-contained body tweets, a CTA close — with a python3 character-count check on every tweet. Use when the user asks for an "X thread", "Twitter thread", "thread about [topic]", "tweetstorm", or wants long-form content broken into tweets. Don't use for single tweets (draft directly), LinkedIn posts (linkedin-content-pack), or fanning one piece across many platforms (content-repurposer).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- sergebulaev/x-skillstheir own version, first seen Jul 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- sergebulaev/x-skills★ 163same 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 repository74 other files it gives its agents.
- agent-eval-harnessSkill
- context-budget-managerSkill
- incident-rollbackSkill
- memory-hygieneSkill
- model-cost-optimizerSkill
- prompt-debuggerSkill
- skill-author-coachSkill
- third-party-skill-vetterSkill
- api-endpoint-testerSkill
- bug-triage-protocolSkill
- changelog-release-notesSkill
- docs-readme-writerSkill
- env-secrets-hygieneSkill
- github-pr-reviewSkill
- git-ship-flowSkill
- lovable-brief-writerSkill
- supabase-migration-writerSkill
- vercel-deploy-checkSkill
- cold-outreach-sequencerSkill
- competitor-pricing-scanSkill
- contract-redline-scanSkill
- customer-support-inboxSkill
- invoice-runnerSkill
- kpi-dashboard-weeklySkill
- lead-research-dossierSkill
- payment-reconciliationSkill
- pipeline-trackerSkill
- proposal-builderSkill
- stripe-payment-linkSkill
- testimonial-harvesterSkill
- weekly-revenue-reportSkill
- brand-voice-guardianSkill
- case-study-builderSkill
- content-repurposerSkill
- deep-research-briefSkill
- email-nurture-sequenceSkill
- landing-page-copywriterSkill
- linkedin-content-packSkill
- newsletter-assemblerSkill
- seo-blog-writerSkill
- social-listening-reportSkill
- youtube-script-writerSkill
- budget-guardrailsSkill
- ceo-operating-doctrineSkill
- delegation-protocolSkill
- editor-personaSkill
- heartbeat-standupSkill
- hiring-briefSkill
- ops-agent-personaSkill
- researcher-personaSkill
- sales-agent-personaSkill
- support-agent-personaSkill
- weekly-retroSkill
- writer-personaSkill
- calendar-conciergeSkill
- decision-journalSkill
- email-triageSkill
- file-organizerSkill
- habit-trackerSkill
- inbox-zero-sprintSkill
- The first 60 shown.
The file
Files
X Thread Builder
Builds threads where every tweet earns its place: an opener that stops the scroll on substance (not bait), 5–9 body tweets that each stand alone when quoted out of context, and a close with one clear CTA. Every tweet is machine-verified under 280 characters before delivery. Output is always a draft — nothing gets posted.
When to Use
- The user wants a thread from a topic, article, brief, or set of notes.
- A
deep-research-briefor long-form piece needs an X-native breakdown. - Not for: single tweets (draft directly), LinkedIn posts (
linkedin-content-pack), or fanning one piece across many platforms (content-repurposer).
Quick Reference
| Action | Command / Call |
| Count one tweet | python3 -c "print(len('''TWEET TEXT'''))" |
| Count whole thread | Write tweets to /tmp/thread.txt separated by ---, then run the step 5 script |
| URL length rule | Any URL counts as 23 chars regardless of actual length |
| Thread size | 1 opener + 5–9 body + 1 close = 7–11 tweets total |
| Numbering | 2/ style on body tweets; opener unnumbered or 1/ |
Procedure
- Precheck — confirm
python3is available (python3 --version). Confirm you have the source material, the audience, and the one thing the reader should do at the end (follow, read, reply, sign up). One CTA only — ask if unstated. - Outline — list 5–9 points, one per body tweet, in an order that builds (setup → payoff, or list of escalating value). Each point must survive alone: assume any tweet may be someone's first contact with the thread.
- Draft the opener — a concrete claim, result, number, or tension in ≤280 chars. It must promise exactly what the thread delivers. Banned: "🧵👇" as the whole hook, "You won't believe", "Most people don't know this", curiosity gaps with no payoff, "A thread on threads".
- Draft body tweets — one idea each, ≤280 chars, self-contained (restate the subject; no bare "It also..." referencing a previous tweet). Line breaks inside a tweet are fine and free. Numbers, specifics, and short sentences over adjectives. No mid-thread hashtags.
- Character check (hard gate) — save the thread to
/tmp/thread.txtwith tweets separated by lines containing only---, then run:
Expected: every line printspython3 -c " import re ts=[t.strip() for t in open('/tmp/thread.txt').read().split('\n---\n')] for i,t in enumerate(ts,1): n=len(re.sub(r'https?://\S+','x'*23,t)) print(f'{i}: {n} chars', 'OK' if n<=280 else 'OVER') "OK. AnyOVERtweet gets trimmed (cut adjectives and hedges first) and the script rerun until clean. - Close with CTA — final tweet: one-line recap of the payoff + the single CTA + at most one link. Optionally "If this was useful, RT the first tweet" — once, plainly, no begging.
- Deliver — output the template below with the verified character counts shown per tweet. Recommend a
brand-voice-guardianpass if a voice profile exists. Do not post.
Output Template
# X Thread: [topic]
**Audience:** [who] | **CTA:** [the one action] | **Tweets:** [n]
1/ [opener] (xxx chars ✓)
2/ [body tweet] (xxx chars ✓)
...
n/ [close + CTA] (xxx chars ✓)
## Notes
- [attachment suggestion for tweet 1, if any: image/screenshot/chart]
- [best posting window + timezone assumption]Pitfalls
- Eyeballed character counts — a "looks fine" tweet at 293 chars breaks on posting. Recovery: the step 5 script is mandatory, not optional; rerun after every edit, including "tiny" ones.
- Dependent tweets — tweet 4 reads "It also does this" and means nothing when quoted alone. Recovery: reread each body tweet in isolation; restate the subject noun in any tweet that fails the standalone test.
- Opener overpromises — hook says "10x your output", thread delivers three mild tips. Recovery: rewrite the opener DOWN to what the thread proves, or upgrade the weakest body tweets with concrete numbers/examples until the promise is honest.
- Multi-CTA close — follow me, AND read the blog, AND join the list. Recovery: keep the CTA chosen in step 1; move the rest to a reply-to-self suggestion in Notes.
Verification
- Step 5 script run on final text; every tweet printed
OK(counts shown in output) - 7–11 tweets total; each body tweet passes the standalone read test
- Opener contains a specific claim/number and none of the banned patterns
- Exactly one CTA in the close; no mid-thread hashtags
- Delivered as a draft; no posting performed
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
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.

