Slash Command

/send

Send something via any channel (email today, more later)

Install

Run in your terminal

npx claudepluginhub punt-labs/claude-plugins --plugin beadle

Details

Argument<what to send> [via <channel>]

Allowed Tools

mcp__plugin_beadle_email__send_emailmcp__plugin_beadle_email__list_contactsmcp__plugin_beadle_email__find_contactmcp__plugin_beadle-dev_email__send_emailmcp__plugin_beadle-dev_email__list_contactsmcp__plugin_beadle-dev_email__find_contact

Command Content

Other plugins with /send

/send

Send any message type to any Omni channel instance

omni

/send

Send a direct message, group message, or broadcast.

thrum

/send

api/messages/

Send a message via Sinch Conversation API (SMS, RCS)

mcp__sinch__send-text-messagemcp__sinch__send-media-messagemcp__sinch__send-location-message+3

sinch-claude-plugin

/send

Use when a spec.md is ready for implementation and needs to be submitted to the belayer pipeline

explorer

/send

Send an email directly from the command line

gmcli

/send

Send a message through a messaging channel

Bash

computer

Stats

Stars2

Forks0

Last CommitMar 18, 2026

Actions

View Source View Plugin View on GitHub View README

Task

Send something to the user or a specified recipient via the best available channel. Today, email is the only channel. In the future, this command will support Signal and other channels.

Parse the arguments

The arguments describe what to send and optionally the channel. Examples:

/send me an email summary — send via email (explicit)

/send me a summary — send via email (default, only channel today)

/send this to kai@example.com — send to a specific recipient via email

Default behavior

Default recipient: the owner (ask if unclear)

Default channel: email (the only channel currently available)

Compose and send

Compose the content based on the arguments. Use plain text.

Choose a clear, descriptive subject line.

Call send_email with the recipient, subject, and body.

The result is already formatted by a PostToolUse hook and displayed in the panel. Do not repeat or reformat the send confirmation.

Future channels

When new channels are added (Signal, etc.), this command will route based on the via argument or infer the channel from context. For now, all sends go through email.

Input

Arguments: $ARGUMENTS

Task

Send something to the user or a specified recipient via the best available channel. Today, email is the only channel. In the future, this command will support Signal and other channels.

Parse the arguments

The arguments describe what to send and optionally the channel. Examples:

/send me an email summary — send via email (explicit)
/send me a summary — send via email (default, only channel today)
/send this to kai@example.com — send to a specific recipient via email

Default behavior

Default recipient: the owner (ask if unclear)
Default channel: email (the only channel currently available)

Compose and send

Compose the content based on the arguments. Use plain text.
Choose a clear, descriptive subject line.
Call send_email with the recipient, subject, and body.

The result is already formatted by a PostToolUse hook and displayed in the panel. Do not repeat or reformat the send confirmation.

Future channels

When new channels are added (Signal, etc.), this command will route based on the via argument or infer the channel from context. For now, all sends go through email.