watchlisted

# xwatch watch -- collect new posts from watched X accounts Reading the X API **costs money** -- it is pay-per-use, about $0.005 per post returned, billed on every post read (client-side filtering saves nothing; you already paid to read it). So the discipline of this skill is: know the cost before a read, and confirm the expensive ones (`poll`, `backfill`, `recent` with a large limit) before running them. ## What this skill does not do It holds no logic. The API calls, the `since_id` watermark rules, archiving, the text filter, the LLM classify/translate, and delivery via pushpush are **all the xwatch package's job.** Do not reimplement them here or copy the API's pricing/limits into a script -- a rule that lives in two places drifts. This skill only assembles one `xwatch` command and runs it. ## Confirm the command is ready This skill calls the **`xwatch` command** the package installs. Once per session, check it: ```sh xwatch --help ``` If the help prints, you are ready. If `command not found` appears, do not invent a path; tell the user to install it: ```sh pip install xwatch # once it is on PyPI pipx install xwatch # for a global command, kept isolated ``` If they installed it into a virtual environment, confirm they run it with that env active. ## The X API bearer token Every read needs a bearer token. If a command fails with a "no X API bearer token" message, the token is not set. **Never have the user paste the token into the chat.** Point t