configure-slack_skill

Overview

This skill configures Slack incoming webhook notifications for the OMC agent system using natural language prompts. It interactively collects webhook URL, mention preferences, event triggers, and optional channel/username overrides, then writes a merged configuration to ~/.claude/.omc-config.json.

How this skill works

The skill detects any existing config and offers to update it. It guides you step‑by‑step to create or paste a valid Slack webhook URL, choose mention behavior, select which events should trigger notifications, and optionally override the channel or display name. Finally it writes the merged settings to the config file and can send a test payload to verify the webhook.

When to use it

• Enable Slack alerts for session lifecycle updates and background task completion
• Reconfigure notifications after rotating or revoking a webhook URL
• Add or change who gets pinged (user, @channel, @here) for urgent alerts
• Limit notifications to specific events to avoid noise
• Quickly verify webhook and channel permissions with a test message

Best practices

• Validate the webhook URL starts with https://hooks.slack.com/services/ before saving
• Prefer webhook default channel unless you have permission to post to another channel
• Use member IDs (<@U...>) for precise user mentions instead of plain names
• Select only necessary events (session-end and input-needed recommended) to reduce alert fatigue
• Test the webhook immediately and inspect HTTP status codes for troubleshooting

Example use cases

• Notify a team channel when long-running agent tasks require human input
• Ping a specific engineer when a critical session finishes using their Slack member ID
• Send session-end summaries to #alerts while keeping normal chatter in the webhook default channel
• Temporarily override the bot display name to reflect project-specific notifier branding
• Automate configuration via env vars (OMC_SLACK_WEBHOOK_URL / OMC_SLACK_MENTION) in CI or dotfiles