> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xhuntr.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Build a watchlist that fires
> Who is actually worth a slot, and how to tell after two weeks.
The most common reason XHuntr feels quiet is not the bot — it is a list of accounts that never touch communities. This guide is how to build one that actually produces signal.
## The principle
XHuntr watches **community behaviour**, not posting. An account can tweet forty times a day and generate zero alerts. What you want are accounts whose *actions* precede a token.
Devs who spin up a community before launching. Serial launchers. KOLs whose joins reliably front-run a push. Small accounts that keep showing up early.
Celebrities and mainstream accounts. Pure commentators who never join anything. Huge accounts already in hundreds of communities, where one more is meaningless.
## Step one: seed from what you already know
Start with accounts you have personally watched call something early. Add them in one shot:
```text theme={null}
somedev, anotherdev, thatkol, serialauncher
```
Use **🏆 Top** (`/top`, Yearly plans) to see the accounts producing the most activity across the whole XHuntr userbase. It is the fastest shortcut to a list that fires, because it is measured rather than guessed.
## Step two: vet before you commit
Before spending a slot, spy the account — it costs nothing:
```text theme={null}
/communities somedev
```
What you want to see:
| Signal | Reading |
| ------------------------------------ | ---------------------------------- |
| **Owner** of one or more communities | They build, not just join. Strong. |
| A handful of recent communities | Actively moving. Strong. |
| Member of 200 communities | Every join is noise. Weak. |
| No communities at all | Nothing to detect. Skip. |
## Step three: get to two, then past it
[🔀 Convergence](/alerts/types) cannot fire until you track **two** accounts, and it gets sharper the more you track from the same scene.
Tracking ten accounts from one niche beats ten unrelated famous accounts — convergence only means something when the accounts share a world.
## Step four: prune after two weeks
After a couple of weeks, check `/history`. Accounts that produced nothing while others produced repeatedly are costing you a slot.
Removing an account discards its baseline. If you re-add later, you get a fresh snapshot and hear nothing about the gap. Prune accounts you have genuinely lost interest in, not ones you are unsure about.
## Step five: turn the noise down
Once the list is right, tune what it sends. Switch off 📌 Pin change first, then 👀 Joined if it is still too much. Keep 🚀 Launch and 🚨 Created on — those two are the product.
See [History and settings](/alerts/history-and-settings).
What to actually do in the sixty seconds after an alert lands.