메뉴
Send proactive messages to IM groups or individual users via the gateway Send API. Use when the user says to send, post, notify, forward, or tell someone a message on Feishu, Slack, Telegram, Discord, DingTalk, or WeCom.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | message-push |
| description | Send proactive messages to IM groups or individual users via the gateway Send API. Use when the user says to send, post, notify, forward, or tell someone a message on Feishu, Slack, Telegram, Discord, DingTalk, or WeCom. |
You can send messages to IM channels proactively -- to groups or individual users -- without waiting for an incoming message.
Watch for phrases like:
Follow these steps when the user requests a message push:
GET /api/channels to confirm the channel exists and supports sendingPOST /api/send with the channel, chatId, and textcurl -X POST http://localhost:$PORT/api/send \
-H "Content-Type: application/json" \
-d '{
"channel": "feishu",
"chatId": "oc_xxxx",
"text": "Hello from the bot!"
}'
| Field | Type | Required | Description |
|---|---|---|---|
channel | string | yes | Channel name: feishu, dingtalk, wecom, slack, telegram, discord |
chatId | string | yes | Chat/group/conversation ID on the target platform |
text | string | yes | Message content (Markdown supported) |
200 { "ok": true } -- message sent successfully404 -- channel not found (check available channels)501 -- channel does not support proactive send503 -- no channel adapters availableIf the send fails, check the HTTP status code:
404, run GET /api/channels and inform the user which channels are actually available501, explain that the target channel adapter does not support proactive sending503, inform the user that no IM adapters are currently runningBefore sending, check which channels are available:
curl http://localhost:$PORT/api/channels
Returns:
{
"channels": [
{ "name": "feishu", "canSend": true },
{ "name": "slack", "canSend": true }
]
}
Chat IDs are platform-specific. Common ways to find them:
| Channel | How to find chatId |
|---|---|
| Feishu | Group settings > Group ID (starts with oc_) |
| Slack | Channel ID from URL (C prefix) or user ID (U prefix) for DMs |
| Telegram | Chat ID from message events (negative for groups) |
| Discord | Channel ID from URL or developer mode |
| DingTalk | Conversation ID from webhook or API |
| WeCom | Chat ID from API |
If the user references a group by name rather than ID, check group memory files in memory/groups/ -- the group key format is {channel}-{chatId}.
Creates and manages scheduled tasks, cron jobs, recurring reminders, and timers via the Task HTTP API. Use when the user asks to schedule something, set a recurring reminder, run a periodic check, or manage existing scheduled tasks.
Research analyst in a multi-bot group chat — synthesizes background information, fact-checks claims, identifies knowledge gaps, and suggests next steps. Use when the conversation needs context, a factual claim needs verification, someone asks for background research, or a discussion lacks supporting evidence.
Code specialist in a multi-bot group chat — writes, reviews, debugs, and explains code. Use when someone asks to write a function, fix a bug, review a pull request, explain a code snippet, or solve a programming problem.
Escalate unresolvable or sensitive requests to a human agent by recording an escalation entry. Use when the user asks to speak to a human, the bot cannot answer confidently, the request involves financial, legal, or security concerns, a safety issue is detected, or the user is frustrated after repeated failures.
Handle everyday conversation, answer questions, manage files, take notes, run scripts, and maintain persistent memory across sessions. Use when the user asks a general question, requests file operations, wants to brainstorm ideas, needs to-do tracking, asks you to remember something, or requests skill search and installation.
Format responses for instant messaging platforms such as Lark, DingTalk, WeCom, Slack, and Telegram. Controls response length, Markdown formatting, tone, group chat behavior, and the [PASS] protocol. Use when replying through an IM channel, composing a group chat message, or adapting output for a chat-based interface.