whisper-bulk-triagelisted
Install: claude install-skill whisper-sec/whisper-skills
# Bulk triage
A list is not many single investigations. Doing it one indicator at a time is slow, burns budget, and —
the part that actually hurts — produces a flat list in which "never seen" and "checked and clean" look
identical. This is the discipline for doing it in one pass and reporting it honestly.
## 1. Prepare the list
Normalise before you send anything.
- Strip scheme, port, path and query. The graph anchors on bare hostnames and addresses.
- Undo defanging: `hxxp`, `[.]`, `(.)`, `[:]` and similar. An analyst pasting from a ticket will have
defanged everything.
- Deduplicate, case-fold hostnames, and keep the original order — the analyst's row numbers are how they
will match your output back to their spreadsheet.
- Un-defang for the lookup **only**. Every hostname you print back goes out re-defanged —
`evil[.]com` — in every section of the report, including the never-seen list. A triage table gets
skim-read, and a live link in one is a mis-click waiting to happen.
- Separate the types. Hostnames, addresses, networks and CIDR blocks can be mixed in one call, but the
modes below treat them differently.
- Count what you have and say so before you start. A list of thousands is a different conversation from
a list of thirty.
If the list came from a file, read it rather than asking the user to paste it.
## 2. Choose the mode
`explain_indicator` has two depths, and picking wrong is the most common mistake here.
| Situation | Mode | Why |
|---|---|---|
|