Multi-Channel Slack Reporter

Most agent setups either dump everything into one channel or spin up separate bots per concern. Both approaches have problems. A single noisy channel buries signal in noise, and multiple bots multiply configuration, secrets, and maintenance.

This blueprint takes a different path: one agent, one Slack connection, multiple triggers. Each trigger owns a specific responsibility and knows exactly which channel to post to. The channel is declared directly in the trigger prompt, so the agent never has to guess where its output belongs.

The pattern is deliberately simple. There is no router, no dispatcher, no multi-agent delegation. The trigger fires, the prompt tells the agent what to do and where to post, and the agent uses the Start Slack Conversation ability to open a message in the correct channel. If you need a new reporting channel, you add a trigger and point it at the channel - nothing else changes.

This works well for ops teams that want a single agent covering incident summaries, deployment recaps, performance dashboards, and weekly digests without juggling multiple bot configurations. The agent shares context across all its duties because it is one bot with one backstory, so insights from the metrics run can inform the incident summary naturally.

Extend this by adding more triggers for new channels, connecting external data sources through additional abilities, or wiring up a space for persistent state between runs.

Backstory

Common information about the bot's experience, skills and personality. For more information, see the Backstory documentation.