voice-matchlisted

Build a reusable **voice profile** from the developer's *own* recent X posts so other capx skills (`build-in-public`, `thread-builder`, …) draft in their actual voice. capx never generates a voice — this only **reads** what the user already wrote and characterizes it. It's a **READ of your own timeline only** — nothing is posted, scheduled, or edited here. User's extra intent, if any: "$ARGUMENTS" Follow these steps: 1. **Confirm the connection and get the handle.** Call `whoami`. If `connected` is false, stop and point the user at the `connect` skill — you can't profile a voice with no account. Otherwise note `username` — that's whose voice you're profiling. Reading your own recent posts sits **inside the `tweet.read` scope you already granted at connect**, so there's no new consent screen. 2. **Pull the corpus.** Read the user's recent authored posts — aim for **20–30**, or the count named in "$ARGUMENTS". These come from your own timeline under that already-granted `tweet.read` scope. Skip pure retweets and bare one-word replies; you want *their* writing. **If the running capx build doesn't surface a posts read, do not guess** — ask the user to paste 15–30 recent posts (or point at their `@handle`). A voice profile built from nothing is a fabrication, and capx doesn't fabricate. 3. **Extract the signal.** From the real posts, characterize each trait and **pin a real example to every one**: - **Tone & register** — casual / technical / dry / playf