dev-configure-notifications

Configure webhook notifications for Telegram, Discord, and Slack channels.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-configure-notifications-evolution-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-configure-notifications
Source: https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-configure-notifications
Command: npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-configure-notifications-evolution-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering teams often miss important events like long-running task completions, build failures, or critical security findings, forcing manual checking of logs and dashboards.

Core Features & Use Cases

  • Multi-channel webhook setup: Configure outbound notifications for Telegram, Discord, and Slack.
  • Event-trigger mapping: Route engineering layer events such as autopilot completion, critical security findings, oath verification failures, and debugger circuit breakers to your chosen channel(s).
  • Integration with existing EvoNexus components: Leverage the existing int-telegram pathway for Telegram delivery and support webhook-based delivery for Discord and Slack.

Quick Start

Configure your notification triggers and webhook settings in .claude/settings.json so that engineering events like autopilot completion and CRITICAL security findings are sent to Telegram, Discord, or Slack.

Frequently Asked Questions about dev-configure-notifications

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure engineering alerts to send notifications to Discord or Slack?

You configure webhook-based engineering notifications by adding channel-specific webhook URLs and event-trigger mappings to `.claude/settings.json`, enabling operational alerts for long-running tasks, CI/build failures, and high-severity security events across Telegram, Discord, and Slack.

Can I route critical security findings and build failures to different messaging channels?

Yes, event-trigger mapping allows routing specific engineering layer events such as critical security findings, oath verification failures, and CI/build failures to your preferred messaging channels like Telegram, Discord, or Slack for targeted operational alerting.

What types of engineering events can be routed using webhook notifications?

Webhook notifications support routing for long-running task completions, CI/build failures, critical security findings, oath verification failures, and debugger circuit breakers to ensure reliable message delivery outside the local CLI.

Does this notification setup require any external dependencies or API libraries?

No external dependencies are required. The setup uses standard webhook configurations for Discord and Slack, and leverages the existing `int-telegram` pathway for Telegram delivery without needing additional API libraries.

Why should I use webhooks for engineering alerts instead of checking logs manually?

Webhooks deliver operational alerts outside the local CLI so teams avoid missing important events like task completions or critical security findings, eliminating the need for manual log and dashboard checking.