skywatch-search-incidents

To search for and classify incidents across AT Protocol data streams, you need a topic-based discovery workflow that expands keywords, filters by relevance, and groups results by geography and temporal distribution. This approach identifies key accounts and verifies incident reports.

You can expand simple topics into comprehensive search strategies by automatically generating synonyms, regional terms, and platform-specific slang. This keyword expansion transforms broad topics into effective queries for discovering coordinated campaigns or regional protests.

The best way to investigate emerging events on the AT Protocol is by using topic-based discovery to identify temporal spikes, key accounts, and verified incident reports. Structured classification then organizes these findings by geography and temporal distribution.

Yes, you need the data-analyst subagent and content similarity tools to execute incident response searches. This integration is required to facilitate investigative workflows, perform topic-based discovery, and apply classification schemas across data streams.

Yes, you can group search results by geography and temporal distribution to investigate coordinated campaigns. This grouping mechanism helps identify regional patterns, temporal spikes, and key accounts involved in emerging events across the network.

Starting from a broad topic rather than a specific account limits search precision, requiring automated keyword expansion and rigorous relevance filtering to manage noise. Without these filters, broad topic discovery yields unverified content across data streams.