devopsby evolution-foundation
Dev Configure Notifications
evolution-foundation/dev-configure-notifications
Set up Telegram, Discord, or Slack webhooks for engineering layer alerts — long-running task completion, build failures, security audit alerts.
What it changes
Passed 21 of 21 test cases with the skill, and 4 of 21 without it.
Without skill18%
With skill100%
Checks it passed that the model alone missed
- Identifies oath.fail as the trigger identifier
- Specifies .claude/settings.json as the file path
- Identifies vault.critical as the trigger event key
and 24 more in the full report
18 fixed4 passed either way0 still failing0 broke
- Pass-rate lift
- +82 pp
- Tokens
- -34%
- Agent turns
- 0%
- Response time
- -64%
Model gemini-3.6-flashMeasured 8/19/2026v122 of 22 cases passed with skill · 21 comparable
See it in action
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
PromptList the three outbound messaging channels explicitly supported for notification delivery in this environment.
What was checked, without and with the skill| Checked | Without skill | With skill |
|---|
| Lists Telegram, Discord, and Slack as the supported notification channels | Missed | Passed |
|---|
What's inside
The instructions your model reads when the skill loads.
SKILL.md71 linessingle file
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}",
Track record
Benchmark
21 / 21
test cases passed, vs 4 / 21 without
Adoption
- Users
- 0
- Times used
- 0
Safety and source details
SkillSafety
✓ 3 of 3 passed✓Code scan15 of 15 checks clean
0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026
View 15 scanner checks
live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing
✓IntentSafe
LLM judge · does the skill do what it claims
✓ContentClean
LLM judge · policy & harmful-content review
Source
Importedevolution-foundation / evo-nexus
.claude/skills/dev-configure-notifications/SKILL.md
License NOASSERTIONImported 8/3/2026Version v1