菜单
Proactively send a message to the user (or a chat) over a connected messaging platform — Telegram, WhatsApp, Discord, Slack, or a generic webhook. Use when asked to "notify", "ping", "message", "tell", "send", "let me know on Telegram/WhatsApp", or to deliver a result to a chat.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | send-message |
| description | Proactively send a message to the user (or a chat) over a connected messaging platform — Telegram, WhatsApp, Discord, Slack, or a generic webhook. Use when asked to "notify", "ping", "message", "tell", "send", "let me know on Telegram/WhatsApp", or to deliver a result to a chat. |
| allowed-tools | ["@send"] |
| triggers | ["send a message","notify me","ping me","message me","tell me on","let me know on","mande mensagem","me avise","me notifique","manda no telegram","manda no whatsapp"] |
Deliver a message to a person/chat through ChatCLI's gateway platform adapters —
the same Telegram/WhatsApp/Discord/Slack/webhook integrations the gateway daemon uses,
now reachable to initiate a message. This is the native, no-gambiarra path: do not
shell out to curl/pywhatkit/browser automation when @send covers the platform.
@send has two subcommands. Always pass the JSON envelope on one line:
<tool_call name="@send" args='{"cmd":"send","args":{"to":"telegram","message":"Build is green ✅"}}' />
<tool_call name="@send" args='{"cmd":"list"}' />
send {to, message}to is either:
"telegram", "whatsapp", "discord", "slack", "webhook" —
which delivers to that platform's configured home channel
(CHATCLI_<PLATFORM>_HOME_CHANNEL); orplatform:chat_id target — e.g. "telegram:-1001234567890",
"whatsapp:+5511999999999", "slack:C0123ABC", "discord:<channel_id>".
Anything after the first : is passed verbatim, so thread/suffix forms like
"telegram:-100123:42" are preserved.message is plain text. Messaging apps render plain text best — avoid tables,
ASCII banners, and code fences unless the user explicitly wants code.listReports which platforms are configured and whether each has a home channel.
Run it first when you're unsure what's available or which to to use.
@send list and pick the only configured one, or ask.platform:chat_id."... is not configured" → that platform has no credentials. Run @send list and
use a configured one, or tell the user which env vars to set
(e.g. CHATCLI_TELEGRAM_BOT_TOKEN)."No target for <platform>" → no chat_id given and no home channel set. Either
pass platform:chat_id or tell the user to set CHATCLI_<PLATFORM>_HOME_CHANNEL.@send sends text. Outbound media (images/audio/files) is not yet supported by the
gateway adapters — if asked, say so plainly rather than improvising a workaround.
Read and write Airtable bases via the official REST API and the user's personal access token — list/filter records, create, update, delete. Use when asked to "add a row to Airtable", "find records in my base", "update this Airtable record".
Search and retrieve academic papers from arXiv by keyword, author, category, or ID, and read abstracts or full PDFs. Free, keyless. Use when asked to "find papers on", "search arXiv", "summarize this paper", or given an arXiv ID/link.
Render ASCII/terminal art — big text banners (figlet/toilet), colorized output (lolcat), and image-to-ASCII/terminal previews (chafa/jp2a). Keyless, local. Use when asked to "make a banner", "ascii art of", "big text", "show this image in the terminal".
Create, list, and manage calendar events / meetings from the terminal using whatever native CLI is installed (gcalcli for Google Calendar, khal for CalDAV, or AppleScript Calendar on macOS). Use when asked to "schedule a meeting", "create an event", "what's on my calendar", "am I free", "book".
Send and read email from the terminal using whatever native CLI is installed (himalaya, msmtp/mutt/neomutt on Linux, or AppleScript Mail on macOS). Use when asked to "send an email", "email someone", "check my inbox", "read my email", "reply to".
Manage the full GitHub workflow from the terminal — auth, issues, pull request lifecycle (branch/commit/open/CI/merge), code review, and repo management. Uses the gh CLI when present, with a git + REST API fallback. Use when asked to "open a PR", "create an issue", "review this PR", "check CI", "list issues".