home / skills / splitleaseteam / splitlease_monorepo / slack-webhook

slack-webhook skill

safe

/.claude/skills/slack-webhook

This skill sends concise Slack alerts for task completions, errors, and security issues using the TINYTASKAGENT webhook to keep you informed.

npx playbooks add skill splitleaseteam/splitlease_monorepo --skill slack-webhook

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

2.0 KB

---
name: slack-webhook
description: |
  Claude's voice for alerting users via Slack. Use this skill to send notifications when:
  (1) A task completes that the user should know about (deployments, builds, long-running operations)
  (2) An error or failure occurs that requires attention
  (3) A security issue, vulnerability, or concerning pattern is discovered
  (4) A warning about potential problems (deprecated APIs, risky patterns, data inconsistencies)
  (5) Anything requiring the user's immediate attention
  Triggers: "notify me", "alert", "let me know", "send to slack", or proactively when encountering issues the user should see immediately.
  IMPORTANT: This skill is designed for external use only. It will refuse to run inside the splitleasesharath GitHub account
  to prevent accidental modifications to the production codebase.
---

# Slack Webhook Notifications

Send 1-line summaries to Slack via `TINYTASKAGENT` webhook.

## End of Task (MANDATORY)

After completing any task, send a brief summary:

```bash
python "C:/Users/Split Lease/Documents/Split Lease/.claude/skills/slack-webhook/scripts/send_slack.py" "<1-line summary>" --type success
```

Keep summaries concise: "Implemented X", "Fixed Y bug", "Deployed Z to staging"

## Message Types

| Type | When to Use |
|------|-------------|
| `success` | Task completed successfully |
| `error` | Task failed or encountered errors |
| `warning` | Potential issues found |
| `urgent` | Security issues, critical failures |
| `info` | General status updates |

## Examples

```bash
# Successful completion
python "...send_slack.py" "Built slack-webhook skill with TINYTASKAGENT support" --type success

# Error encountered
python "...send_slack.py" "Build failed: 3 TypeScript errors in auth.ts" --type error

# Security concern
python "...send_slack.py" "Found hardcoded API key in config.js" --type urgent
```

## Configuration

Webhook URL resolved from (in order):
1. `TINYTASKAGENT` environment variable
2. `.env` file in cwd or home directory
3. `--webhook` argument (override)

Overview

This skill sends concise, actionable Slack notifications using the TINYTASKAGENT webhook. It reports task completions, errors, warnings, security alerts, and other items that require immediate attention. The skill is for external use only and will refuse to run inside the splitleasesharath GitHub account to avoid accidental production modifications.

How this skill works

After any task, call the script with a one-line summary and a message type (success, error, warning, urgent, info). The webhook URL is resolved from the TINYTASKAGENT environment variable, a .env file in the working or home directory, or an explicit --webhook argument. Messages are formatted as single-line summaries to keep Slack channels clear and actionable.

When to use it

When a long-running task or deployment finishes and the user should be notified
When an error or build failure occurs that needs attention
When a security issue, vulnerability, or sensitive secret is discovered
When a potential problem or risky pattern is detected (deprecated APIs, data inconsistencies)
For urgent alerts that require immediate human response
To provide brief, regular status updates to stakeholders

Best practices

Keep messages to a single concise sentence: implement X, fixed Y, deployed Z
Select the correct message type (success/error/warning/urgent/info) to set urgency
Avoid posting large logs or stack traces; link to the full report instead
Ensure TINYTASKAGENT webhook is set in environment or .env and test with non-production channels first
Use the --webhook override only for temporary testing to avoid misrouting alerts

Example use cases

Notify team that a CI build completed successfully: 'Built slack-webhook skill with TINYTASKAGENT support' --type success
Alert on a broken build: 'Build failed: 3 TypeScript errors in auth.ts' --type error
Signal a critical security finding: 'Found hardcoded API key in config.js' --type urgent
Warn about deprecated API usage detected during static analysis --type warning
Send routine deployment notices to the operations channel --type info

FAQ

How do I set the webhook URL?

Set TINYTASKAGENT in the environment, add it to a .env file in the working or home directory, or pass --webhook when sending a message.

What message length is recommended?

Keep it to one short sentence so it reads clearly in Slack channels and is easy to scan.

Can I run this from the splitleasesharath GitHub account?

No. The skill refuses to run inside the splitleasesharath GitHub account to prevent accidental changes to production.