Skip to main content

configure-notifications

Enables users to configure notification integrations for Telegram, Discord, and Slack through natural language interactions.

Install this skill

or
0/100

Security score

The configure-notifications skill was audited on May 19, 2026 and we found 96 security issues across 4 threat categories. Review the findings below before installing.

Categories Tested

Security Issues

medium line 118

Template literal with variable interpolation in command context

SourceSKILL.md
118```bash
medium line 203

Template literal with variable interpolation in command context

SourceSKILL.md
203```bash
medium line 462

Template literal with variable interpolation in command context

SourceSKILL.md
462```bash
medium line 699

Template literal with variable interpolation in command context

SourceSKILL.md
699```bash
medium line 1047

Template literal with variable interpolation in command context

SourceSKILL.md
1047```bash
medium line 1159

Template literal with variable interpolation in command context

SourceSKILL.md
1159```bash
medium line 122

Curl to non-GitHub URL

SourceSKILL.md
122curl -s "https://api.telegram.org/bot${BOT_TOKEN}/getUpdates" | jq '.result[-1].message.chat.id // .result[-1].message.from.id // "No messages found - send /start to your bot first"'
medium line 12

Webhook reference - potential data exfiltration

SourceSKILL.md
12- "discord webhook"
medium line 15

Webhook reference - potential data exfiltration

SourceSKILL.md
15- "slack webhook"
medium line 35

Webhook reference - potential data exfiltration

SourceSKILL.md
352. **Discord** - Webhook or bot token + channel ID.
medium line 36

Webhook reference - potential data exfiltration

SourceSKILL.md
363. **Slack** - Incoming webhook URL.
low line 283

Webhook reference - potential data exfiltration

SourceSKILL.md
283WEBHOOK_URL=$(jq -r '.notifications.discord.webhookUrl // empty' "$CONFIG_FILE" 2>/dev/null)
low line 288

Webhook reference - potential data exfiltration

SourceSKILL.md
288echo "WEBHOOK_CONFIGURED=$HAS_DISCORD"
low line 290

Webhook reference - potential data exfiltration

SourceSKILL.md
290[ -n "$WEBHOOK_URL" ] && echo "WEBHOOK_URL=$WEBHOOK_URL"
medium line 309

Webhook reference - potential data exfiltration

SourceSKILL.md
3091. **Webhook (Recommended)** - Create a webhook in your Discord channel. Simple, no bot needed. Just paste the URL.
medium line 312

Webhook reference - potential data exfiltration

SourceSKILL.md
312### Step 3A: Webhook Setup
medium line 314

Webhook reference - potential data exfiltration

SourceSKILL.md
314If user chose Webhook:
medium line 318

Webhook reference - potential data exfiltration

SourceSKILL.md
318**Question:** "Paste your Discord webhook URL. To create one: Server Settings > Integrations > Webhooks > New Webhook > Copy URL"
medium line 320

Webhook reference - potential data exfiltration

SourceSKILL.md
320The user will type their webhook URL in the "Other" field.
medium line 323

Webhook reference - potential data exfiltration

SourceSKILL.md
323- Must start with `https://discord.com/api/webhooks/` or `https://discordapp.com/api/webhooks/`
medium line 376

Webhook reference - potential data exfiltration

SourceSKILL.md
376**Question:** "Custom bot display name? (Shows as the webhook sender name in Discord)"
medium line 398

Webhook reference - potential data exfiltration

SourceSKILL.md
398#### For Webhook method:
low line 403

Webhook reference - potential data exfiltration

SourceSKILL.md
403# WEBHOOK_URL, MENTION, USERNAME are collected from user
low line 407

Webhook reference - potential data exfiltration

SourceSKILL.md
407--arg url "$WEBHOOK_URL" \
low line 414

Webhook reference - potential data exfiltration

SourceSKILL.md
414webhookUrl: $url,
low line 463

Webhook reference - potential data exfiltration

SourceSKILL.md
463# For webhook:
low line 467

Webhook reference - potential data exfiltration

SourceSKILL.md
467"$WEBHOOK_URL"
low line 479

Webhook reference - potential data exfiltration

SourceSKILL.md
479Method: Webhook / Bot API
low line 487

Webhook reference - potential data exfiltration

SourceSKILL.md
487OMC_DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/...
medium line 499

Webhook reference - potential data exfiltration

SourceSKILL.md
499**Webhook method:**
low line 501

Webhook reference - potential data exfiltration

SourceSKILL.md
501export OMC_DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/..."
low line 531

Webhook reference - potential data exfiltration

SourceSKILL.md
531WEBHOOK_URL=$(jq -r '.notifications.slack.webhookUrl // empty' "$CONFIG_FILE" 2>/dev/null)
low line 537

Webhook reference - potential data exfiltration

SourceSKILL.md
537[ -n "$WEBHOOK_URL" ] && echo "WEBHOOK_URL=$WEBHOOK_URL"
medium line 550

Webhook reference - potential data exfiltration

SourceSKILL.md
550### Step 2: Create a Slack Incoming Webhook
medium line 552

Webhook reference - potential data exfiltration

SourceSKILL.md
552Guide the user through creating a webhook if they don't have one:
low line 555

Webhook reference - potential data exfiltration

SourceSKILL.md
555To set up Slack notifications, you need a Slack incoming webhook URL.
low line 557

Webhook reference - potential data exfiltration

SourceSKILL.md
557CREATE A WEBHOOK:
low line 561

Webhook reference - potential data exfiltration

SourceSKILL.md
5614. Go to "Incoming Webhooks" in the left sidebar
low line 562

Webhook reference - potential data exfiltration

SourceSKILL.md
5625. Toggle "Activate Incoming Webhooks" to ON
low line 563

Webhook reference - potential data exfiltration

SourceSKILL.md
5636. Click "Add New Webhook to Workspace"
low line 565

Webhook reference - potential data exfiltration

SourceSKILL.md
5658. Copy the webhook URL (starts with https://hooks.slack.com/services/...)
medium line 568

Webhook reference - potential data exfiltration

SourceSKILL.md
568### Step 3: Collect Webhook URL
medium line 572

Webhook reference - potential data exfiltration

SourceSKILL.md
572**Question:** "Paste your Slack incoming webhook URL (starts with https://hooks.slack.com/services/...)"
medium line 574

Webhook reference - potential data exfiltration

SourceSKILL.md
574The user will type their webhook URL in the "Other" field.
medium line 624

Webhook reference - potential data exfiltration

SourceSKILL.md
624**Question:** "Override the default notification channel? (The webhook already has a default channel)"
medium line 627

Webhook reference - potential data exfiltration

SourceSKILL.md
6271. **Use webhook default (Recommended)** - Post to the channel selected during webhook setup
medium line 636

Webhook reference - potential data exfiltration

SourceSKILL.md
636**Question:** "Custom bot display name? (Shows as the webhook sender name in Slack)"
low line 657

Webhook reference - potential data exfiltration

SourceSKILL.md
657# WEBHOOK_URL, MENTION, USERNAME, CHANNEL are collected from user
low line 659

Webhook reference - potential data exfiltration

SourceSKILL.md
659--arg url "$WEBHOOK_URL" \
low line 667

Webhook reference - potential data exfiltration

SourceSKILL.md
667webhookUrl: $url,
low line 700

Webhook reference - potential data exfiltration

SourceSKILL.md
700# For webhook:
low line 709

Webhook reference - potential data exfiltration

SourceSKILL.md
709"$WEBHOOK_URL"
medium line 713

Webhook reference - potential data exfiltration

SourceSKILL.md
713- **403 Forbidden**: Webhook URL is invalid or revoked
medium line 714

Webhook reference - potential data exfiltration

SourceSKILL.md
714- **404 Not Found**: Webhook URL is incorrect
low line 725

Webhook reference - potential data exfiltration

SourceSKILL.md
725Webhook: https://hooks.slack.com/services/T00/B00/xxx...
low line 727

Webhook reference - potential data exfiltration

SourceSKILL.md
727Channel: #alerts (or "webhook default")
low line 734

Webhook reference - potential data exfiltration

SourceSKILL.md
734OMC_SLACK_WEBHOOK_URL=https://hooks.slack.com/services/...
low line 747

Webhook reference - potential data exfiltration

SourceSKILL.md
747export OMC_SLACK_WEBHOOK_URL="https://hooks.slack.com/services/T00/B00/xxx"
medium line 772

Webhook reference - potential data exfiltration

SourceSKILL.md
772- `omc --webhook` — Activates webhook notifications (sets `OMC_WEBHOOK=1`)
medium line 779

Webhook reference - potential data exfiltration

SourceSKILL.md
779- `omc --telegram --slack --webhook` — Telegram + Slack + Webhook active
medium line 944

Webhook reference - potential data exfiltration

SourceSKILL.md
944Configure custom webhooks and CLI commands for services beyond the native Discord/Telegram/Slack integrations.
medium line 948

Webhook reference - potential data exfiltration

SourceSKILL.md
948If the user says "custom integration", "openclaw", "n8n", "webhook", "cli command", or similar → follow this section.
medium line 995

Webhook reference - potential data exfiltration

SourceSKILL.md
9952. **n8n Webhook** - Trigger n8n workflows
medium line 997

Webhook reference - potential data exfiltration

SourceSKILL.md
9974. **Generic Webhook** - Custom HTTPS webhook
medium line 1004

Webhook reference - potential data exfiltration

SourceSKILL.md
1004**Question:** "What is your gateway/webhook URL?"
medium line 1043

Webhook reference - potential data exfiltration

SourceSKILL.md
10431. **Yes, test now** - Send test webhook
low line 1048

Webhook reference - potential data exfiltration

SourceSKILL.md
1048# For webhook integrations
low line 1053

Webhook reference - potential data exfiltration

SourceSKILL.md
1053"$WEBHOOK_URL"
low line 1070

Webhook reference - potential data exfiltration

SourceSKILL.md
1070"type": "webhook",
medium line 1090

Webhook reference - potential data exfiltration

SourceSKILL.md
1090### Generic Webhook Flow
medium line 1093

Webhook reference - potential data exfiltration

SourceSKILL.md
1093Ask for webhook URL (HTTPS required).
medium line 46

Access to hidden dotfiles in home directory

SourceSKILL.md
46This is an interactive, natural-language configuration skill. Walk the user through setup by asking questions with AskUserQuestion. Write the result to `~/.claude/.omc-config.json`.
low line 242

Access to hidden dotfiles in home directory

SourceSKILL.md
242Config saved to: ~/.claude/.omc-config.json
medium line 272

Access to hidden dotfiles in home directory

SourceSKILL.md
272This is an interactive, natural-language configuration skill. Walk the user through setup by asking questions with AskUserQuestion. Write the result to `~/.claude/.omc-config.json`.
low line 484

Access to hidden dotfiles in home directory

SourceSKILL.md
484Config saved to: ~/.claude/.omc-config.json
medium line 522

Access to hidden dotfiles in home directory

SourceSKILL.md
522This is an interactive, natural-language configuration skill. Walk the user through setup by asking questions with AskUserQuestion. Write the result to `~/.claude/.omc-config.json`.
low line 731

Access to hidden dotfiles in home directory

SourceSKILL.md
731Config saved to: ~/.claude/.omc-config.json
medium line 795

Access to hidden dotfiles in home directory

SourceSKILL.md
795Check if `~/.claude/omc_config.hook.json` exists. If it does, show the current configuration. If not, explain what it does.
low line 802

Access to hidden dotfiles in home directory

SourceSKILL.md
802Config file: ~/.claude/omc_config.hook.json
medium line 882

Access to hidden dotfiles in home directory

SourceSKILL.md
882Read or create `~/.claude/omc_config.hook.json` and merge the new settings:
medium line 952

Access to hidden dotfiles in home directory

SourceSKILL.md
952If `~/.claude/omc_config.openclaw.json` exists, detect and offer migration:
low line 88

External URL reference

SourceSKILL.md
882. Visit: https://api.telegram.org/bot<YOUR_TOKEN>/getUpdates
low line 122

External URL reference

SourceSKILL.md
122curl -s "https://api.telegram.org/bot${BOT_TOKEN}/getUpdates" | jq '.result[-1].message.chat.id // .result[-1].message.from.id // "No messages found - send /start to your bot first"'
low line 209

External URL reference

SourceSKILL.md
209"https://api.telegram.org/bot${BOT_TOKEN}/sendMessage" \
low line 323

External URL reference

SourceSKILL.md
323- Must start with `https://discord.com/api/webhooks/` or `https://discordapp.com/api/webhooks/`
low line 487

External URL reference

SourceSKILL.md
487OMC_DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/...
low line 501

External URL reference

SourceSKILL.md
501export OMC_DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/..."
low line 558

External URL reference

SourceSKILL.md
5581. Go to https://api.slack.com/apps
low line 565

External URL reference

SourceSKILL.md
5658. Copy the webhook URL (starts with https://hooks.slack.com/services/...)
low line 572

External URL reference

SourceSKILL.md
572**Question:** "Paste your Slack incoming webhook URL (starts with https://hooks.slack.com/services/...)"
low line 577

External URL reference

SourceSKILL.md
577- Must start with `https://hooks.slack.com/services/`
low line 725

External URL reference

SourceSKILL.md
725Webhook: https://hooks.slack.com/services/T00/B00/xxx...
low line 734

External URL reference

SourceSKILL.md
734OMC_SLACK_WEBHOOK_URL=https://hooks.slack.com/services/...
low line 747

External URL reference

SourceSKILL.md
747export OMC_SLACK_WEBHOOK_URL="https://hooks.slack.com/services/T00/B00/xxx"
low line 1074

External URL reference

SourceSKILL.md
1074"url": "https://my-gateway.example.com/wake",
low line 1145

External URL reference

SourceSKILL.md
1145https://my-api.com/notify
Scanned on May 19, 2026
View Security Dashboard
Installation guide →