community-automations/slack-monitor

Sales & CRM

PublicClaude subagent

Slack Monitor

Alerting channels get so noisy that people mute them, which defeats the point. This monitor watches your service events, suppresses the known-noise patterns, and groups related failures into a single incident thread.

sonnet4 daysSlack APIWebhookPostgreSQLClaude
ClaudeClaude
ROI for
README.md

Why this subagent

Alerting channels get so noisy that people mute them, which defeats the point. This monitor watches your service events, suppresses the known-noise patterns, and groups related failures into a single incident thread.

What reaches Slack is a clear, deduplicated alert with severity and a runbook link, not fifty repeats of the same blip. The signal stays loud enough that on-call actually trusts the channel again.

How it runs

    • Read

      Used at step 01 to kick off the pipeline.

    • Write

      Used at step 01 to kick off the pipeline.

    • WebFetch

      Used at step 01 to kick off the pipeline.

    • WebSearch

      Used at step 01 to kick off the pipeline.

Sample output

json
// Sample output
// (generated when the pipeline finishes)

Classify this alert by severity, decide if it duplicates a recent one, and write a one-line Slack summary.

Unlock the rest

The full agent definition, install snippet, and starter task are gated for community members.

Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.