/dev-configure-notifications
Set up Telegram, Discord, or Slack webhooks for engineering layer alerts — long-running task completion, build failures, security audit alerts.
$ npx -y skills add evolution-foundation/evo-nexus --skill dev-configure-notifications --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/dev-configure-notifications
Context preview
The summary Claude sees to decide when to auto-load this skill.
Set up Telegram, Discord, or Slack webhooks for engineering layer alerts — long-running task completion, build failures, security audit alerts.
SKILL.md
dev-configure-notifications.SKILL.mdname: 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
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)
Other skills on evo-nexus.
- /ai-image-creator
Generate PNG images using AI (multiple models via OpenRouter including Gemini, FLUX.2, Riverflow, SeedDream, GPT-5 Image, proxied through Cloudflare AI Gateway BYOK). Also analyze/describe existing images using multimodal AI vision. Use when user asks to "generate an image",
Open skill - /create-agent
Create a new custom agent for the workspace. Guides the user through defining agent name, domain, personality, skills, model, and memory folder. Use when the user says 'create an agent', 'new agent', 'add an agent', 'I need a custom agent', or wants to create a specialized agent
Open skill - /create-command
Create a new slash command for Claude Code. Guides the user through defining the command name, what it does, and generates the markdown file in .claude/commands/. Use when the user says 'create a command', 'new command', 'add a slash command', 'I want a shortcut for', or wants
Open skill - /create-goal
Create a Mission, Project, or Goal (Mission → Project → Goal → Task hierarchy) in EvoNexus. Guides the user through picking a mission, choosing or creating a project, defining a measurable goal with metric_type and target_value. Writes to the SQLite goals tables via POST
Open skill - /create-heartbeat
Create a new heartbeat (proactive agent scheduled with a decision prompt) for EvoNexus. Guides the user through picking an agent, setting interval, wake triggers, and the decision prompt that governs when the agent acts. Writes to config/heartbeats.yaml with pydantic validation.
Open skill - /create-integration
Create a new custom integration (API/service wrapper) for the workspace. Guides the user through defining the integration's slug, display name, description, category, and required env keys. Writes .claude/skills/custom-int-{slug}/SKILL.md via POST /api/integrations/custom. Use
Open skill

