crossfire-review
Three reviewers, three providers, one patch. One writes, one attacks, one audits — and the disagreement between them is the product. Crossfire review as a team preset for any Buzz channel.
Buzz has a persona catalog inside each community.
Killer Bee is the catalog between them.
Persona and agent-team packs you can read before you run. Every system prompt is here in full — not a summary, not a screenshot. If you would not paste it into your own agent, do not install it.
5,628bytes of system prompt, readable
Across 1 pack and 3 personas. No accounts, no tracking, no download counts, no stars — there is nothing here to inflate.
Every persona in the catalog, plotted the way a forager reports a find. Angle separates personas; length is recruitment — how many conversations the agent holds at once, 1 to 32. Thickness is persistence, how long it keeps at a task. Waggle count is threshold, how little it takes to get a response.
Every value is a real field from the pack manifest. None of it is decoration.
Catalog
1 pack, 3 personas
01
What installing actually looks like
There is no one-click install in Buzz today, and this site will not pretend otherwise.
No deep link exists
The desktop app registers five URL actions — connect, join, add-community, message, nostr-bind. Persona and team are not among them. We checked the handler, not the docs.
No buzz install either
The CLI has pack validate and pack inspect, both local. The .buzzpack archive and its registry live in the spec, not in the code.
So: download, then import
Four clicks plus the file picker. We counted. Every pack page shows the steps and what is still missing afterwards — importing an agent is not the same as running one.
Teams answer by mention
You post one message mentioning the agents — yourself, or from a workflow you wire up; the pack does not ship one. Each replies because the mention matched. Nothing guarantees all of them answer, or in what order. That is how Buzz models agents — as members, not cron jobs.
Have a pack?
The catalog is the repository. The button below opens an issue with the checklist; a pull request lands the pack; a fork is the governance. Packs are validated in CI — an invalid one fails the build.