tweet

name	tweet
description	Write high-retention X/Twitter posts and threads. NOT for product copy or long-form marketing prose (use writing).
when_to_use	tweet, X post, Twitter thread, launch thread, viral hook, numeric hook, banger, tweetstorm, make this shareable, promote this project on X
user-invocable	true

X/Twitter Writing

ALWAYS apply the writing skill. ALWAYS verify unstable facts and numeric claims against primary sources before drafting.

Workflow

1. ALWAYS name the reader and the belief the post must change.
2. ALWAYS collect one to three defensible claims with sources and caveats.
3. ALWAYS draft three hooks before writing the body.
4. ALWAYS choose the hook with the clearest tension, not the loudest adjective.
5. ALWAYS write one tweet or a 4–8 tweet arc; reveal the project late.
6. ALWAYS count every tweet and cut each below 280 characters.
7. ALWAYS return final copy plus brief source notes outside the thread.

Hook

• ALWAYS start with a familiar unit: 100 people, one team, money, time, tasks, or another scale the reader understands immediately.
• ALWAYS prefer one or two strong numbers when defensible data exists.
• ALWAYS put the surprise or contradiction by line two.
• ALWAYS end with the consequence—the banger—not a teaser question.
• NEVER open with “I built,” the project name, or a link — ALWAYS open with the reader's outcome or changed belief.
• NEVER invent a comparison — ALWAYS preserve the source's denominator, causality, date, uncertainty, and wording.

Thread Arc

1. Hook — familiar anchor, surprising number, tension, consequence.
2. Proof — explain the measure; state the source and material caveat.
3. Reframe — name the bottleneck or belief that changed.
4. Reasons — advance one concrete reason per tweet.
5. Reveal — introduce the project as the response to the proven problem.
6. Close — memorable line, direct action, project link, source links.

Guardrails

• NEVER hide a material caveat — ALWAYS place it in the proof tweet.
• NEVER repeat a claim to fill space — ALWAYS move the argument forward.
• NEVER use “game-changing,” “changes everything,” or empty superlatives — ALWAYS let the facts create the impact.
• NEVER clutter the hook with links — ALWAYS put them in the close or source reply unless the user explicitly prioritizes immediate clicks.
• NEVER promise virality — ALWAYS optimize for clarity, surprise, credibility, and shareability.