Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub punt-labs/claude-plugins --plugin beadleHow this command is triggered — by the user, by Claude, or both
Slash command
/beadle-dev:send <what to send> [via <channel>]Files this command reads when invoked
This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
<!-- markdownlint-disable MD041 --> ## 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 - Def...
/sendSends direct messages to agents or roles, group messages, or broadcasts to everyone. Provide message and --to @name/@group/@everyone; prompts for details if omitted.
/emailBuilds email delivery and multi-channel notification systems with provider integrations, responsive templates (React Email/MJML), channel routing, deliverability monitoring, bounce handling, and DNS authentication. Supports flags for specific components.
/sendSends a WhatsApp message to a JID or contact name. Resolves JID using chats/contacts list if only message or name provided.
/candidate-outreachDrafts personalized candidate outreach messages for email or LinkedIn InMail including subject lines, follow-up sequences, and personalization notes.
/employee-emailDrafts professional employee emails for HR communications including policy changes, benefits updates, performance reviews, org announcements, welcomes, and offboarding.
/sendSends text, TTS, media, reactions, stickers, embeds, polls, and presence indicators to any Omni channel instance via omni CLI.
Share bugs, ideas, or general feedback.
Arguments: $ARGUMENTS
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.
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 emailsend_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.
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.