thread-builderlisted

Turn raw material into a structured X thread: a hook that earns attention, body beats that each carry one idea, and a close that lands the point. **You write every post** from the material below — capx never generates content; it only ships (each post passes the casserole guardrail at send). Raw material and intent: "$ARGUMENTS" If you're not connected yet, run the `connect` skill first; `whoami` confirms which account you'll post as. Follow these steps: 1. **Read the raw material.** Take "$ARGUMENTS" as the source — notes, a story, a decision log, a topic with key points. Everything in the thread must trace back to something real here (or the user's own knowledge). If the material is thin or you'd have to invent features, numbers, or outcomes to fill it, **ask instead of padding** — a fabricated thread fails the moment a reader checks. 2. **Find the spine.** A thread is ONE argument told in beats, not a pile of tweets. Name the single takeaway the reader should leave with. If the material actually holds two unrelated ideas, that's two threads — say so rather than forcing them together. 3. **Write the hook (post 1).** The first post earns the rest. Lead with a concrete claim, number, or tension pulled straight from the material — the guard blocks vague hype and engagement-bait ("a 🧵 you NEED to read"), and readers scroll past it anyway. Substance is the hook. A light "here's how it went" at the end is fine to pull them down; bait is not. 4. **Br