sending

Dispatch user-approved messages to Slack, email, SMS, webhooks, and GitHub.

105|13|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Hmbown/Wizards-of-the-Ghosts --skill sending
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sending
Source: https://github.com/Hmbown/Wizards-of-the-Ghosts/tree/main/generated/hermes/messaging-and-coordination/sending
Command: npx skills add https://github.com/Hmbown/Wizards-of-the-Ghosts --skill sending

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatching messages to the correct channel with user-approved delivery is streamlined, reducing manual routing and miscommunication.

Core Features & Use Cases

  • Automatically determine the best channel (Slack, email, SMS, webhook, or GitHub) and format content for that destination.
  • Present a draft for user approval before actually sending, then execute delivery and confirm completion.
  • Use cases include incident alerts, team notifications, and status updates across collaboration tools.

Quick Start

Draft a channel-appropriate message and await user approval before sending.

Frequently Asked Questions about sending

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate sending incident alerts to Slack and other channels with user approval?

To automate sending incident alerts, this tool drafts channel-appropriate messages for Slack, email, SMS, webhooks, and GitHub, presenting them for user approval before executing delivery via the correct API.

Do I need a SLACK_TOKEN and curl on PATH to send automated notifications?

Yes, you need a SLACK_TOKEN and curl on PATH to send automated notifications. These are enforced prerequisites for the Skill to authenticate and execute delivery via the correct APIs.

How does channel-aware messaging work for team notifications across different platforms?

Channel-aware messaging automatically determines the best destination and formats content specifically for Slack, email, SMS, webhooks, or GitHub, ensuring the message fits the target before requesting user approval.

Can I review a drafted message before it sends to my webhook or email?

Yes, you can review a drafted message before it sends. The tool presents a draft for user approval and only executes delivery after confirmation, confirming completion with a delivery timestamp.

What is the best way to route status updates across multiple collaboration tools without manual intervention?

The best way to route status updates is using a tool that automatically dispatch messages to the appropriate channel with user approval, drafting concise content for Slack, email, SMS, webhooks, or GitHub.

Why does my automated message fail to send when targeting GitHub notifications?

Your automated message might fail to send if prerequisites are unmet. Ensure SLACK_TOKEN and curl on PATH are configured correctly, as these are enforced before drafting and delivery execution.