Skip to content
Automation
Skill

/dev-configure-notifications

Set up Telegram, Discord, or Slack webhooks for engineering layer alerts — long-running task completion, build failures, security audit alerts.

From plugin
evo-nexus
549193 skills38 agents40 commands9 MCP

Claude Code

$ npx -y skills add evolution-foundation/evo-nexus --skill dev-configure-notifications --agent claude-code

SKILL.md

dev-configure-notifications.SKILL.md
name: dev-configure-notifications
description: Set up Telegram, Discord, or Slack webhooks for engineering layer alerts — long-running task completion, build failures, security audit alerts.

Dev Configure Notifications

Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.

Configure outbound notifications for engineering layer events: long-running task completion, build failures, critical security findings, etc.

Use When

  • You want to be notified when `dev-autopilot` finishes (it can take minutes)
  • You want CI / build failure alerts in Telegram or Discord
  • You want `@vault-security` to ping you on CRITICAL findings

Channels Supported

  • **Telegram** — via the existing EvoNexus `int-telegram` integration
  • **Discord** — via webhook URL
  • **Slack** — via webhook URL

Workflow

Step 1 — Pick the trigger

Common triggers:

  • `dev-autopilot` completion
  • `@vault-security` CRITICAL finding
  • `@oath-verifier` FAIL verdict
  • `@hawk-debugger` 3-failure circuit breaker

Step 2 — Pick the channel

  • Telegram (uses existing bot via `int-telegram`)
  • Discord (needs webhook URL)
  • Slack (needs webhook URL)

Step 3 — Configure

Save webhook config to `.claude/settings.json` or env vars:

{
  "engineeringLayer": {
    "notifications": {
      "telegram": {
        "enabled": true,
        "chatId": "${USER_TELEGRAM_CHAT_ID}",
        "triggers": ["autopilot.complete", "vault.critical", "oath.fail"]
      },
      "discord": {
        "enabled": false
      }
    }
  }
}

Step 4 — Test

Send a test notification via the configured channel. Verify it arrives.

Step 5 — Document

Save config notes to `workspace/development/research/[C]notifications-config-{date}.md`.

Output Format

Notification message format:

🤖 [EvoNexus Eng] {agent} {event}
{summary}

📁 {path to artifact}

Pairs With

  • `int-telegram` (for Telegram delivery)
  • `dev-autopilot` (most common notification source)
  • `@vault-security` (CRITICAL finding alerts)
  • `update-config` (built-in skill for settings edits)
Read more
@evolution-foundation
Ships withevo-nexus

The open source operating system for AI-powered businesses

549193 skills38 agents9 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
549
Star history of evolution-foundation/evo-nexus on GitHub, a chart by star-history.com

Other skills on evo-nexus.

More skills from other plugins.

agent-builder

agent-builder

Load immediately after an Agent intent, before the first agent_builder_* call. Governs how you create, configure, test, and…

n8n12d209k
@n8n-io@n8n-ioInstall Skill
browser-use

browser-use

Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…

@browser-use@browser-useInstall Skill
agent-browser

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…

@vercel-labs-2@vercel-labs-2Install Skill
add-anydoc

add-anydoc

Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when…

@nanocoai@nanocoaiInstall Skill

Questions about dev-configure-notifications.

Which coding agents can use dev-configure-notifications?
dev-configure-notifications installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.