repurposelisted

Take one long piece — a blog post, README, changelog, or design doc — and turn it into an X thread. **You read the source and write every post** from what it actually says; capx never generates content, it only ships (each post clears the casserole guardrail at send). The thing to repurpose: "$ARGUMENTS" Follow these steps: 1. **Read the actual source.** "$ARGUMENTS" is a file path or a URL. If it's a path, open the file; if it's a URL, fetch it with your web tool. Work from the **real text**, not the title or your memory of the topic. If you can't reach a URL, say so and ask the user to paste it or give a local path — don't guess at the contents. 2. **Pull the load-bearing points.** Find the **3–6 things that actually carry the piece** — the core claim, the key decision and why, the concrete result, the counterintuitive bit, the how. Skip the intro throat- clearing, SEO filler, and anything the source doesn't really commit to. If a point isn't supported by the text in front of you, it doesn't go in the thread. 3. **Shape the thread — hook + one post per point + close.** - **Hook (post 1):** lead with the single sharpest, most specific thing the reader gets — the result or the surprising claim. Not "🧵 a thread on X" and not vague hype; the guardrail blocks bait, and it reads as filler anyway. Make post 1 earn the scroll. - **Body (one post per point):** each post carries exactly one point, concrete and self-contained, in the source'