message-push
Skill326 starsChanged 9 months agoMITView on GitHub
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.
- Sends data out
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/architecture-constraints.mdcCursor rule
- .cursor/rules/engine-internals.mdcCursor rule
- .cursor/rules/testing-conventions.mdcCursor rule
- escalationSkill
- generalSkill
- im-adapterSkill
- kb-guideSkill
- multi-botSkill
- task-managerSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Follow these steps when the user requests a message push:
- Distinctive: line 61
If the send fails, check the HTTP status code:
- Distinctive: line 68
Before sending, check which channels are available:
- Very specific: line 97
If the user references a group by name rather than ID, check group memory files in memory/groups/ -- the group key format is …
- Distinctive: line 101
Always confirm with the user before sending to a new chat for the first time
- Distinctive: line 103
Keep messages concise -- follow the im-adapter formatting guidelines
- Distinctive: line 104
If the user says "send to the group" without specifying which one, check the current conversation context or ask
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Message Push
You can send messages to IM channels proactively -- to groups or individual users -- without waiting for an incoming message.
Recognizing Push Intent
Note: if the user asks you to send a FILE or IMAGE (e.g. a generated document, chart, photo), do NOT use this skill — instead save to temp_file/ and emit [SEND_IMAGE: ...] / [SEND_FILE: ...] markers (see the im-adapter skill). This skill only sends TEXT messages.
Watch for phrases like:
- "send this to the ops group"
- "tell Alice in DM that..."
- "post this summary to #general"
- "notify the team on Feishu"
- "forward this to chat oc_xxx"
Sending Workflow
Follow these steps when the user requests a message push:
- Identify the target -- determine the channel name and chatId from the user's request
- Discover available channels -- call
GET /api/channelsto confirm the channel exists and supports sending - Compose the message -- draft the text content, following im-adapter formatting guidelines
- Confirm with the user -- if this is the first time sending to this chat, show the draft and ask for approval
- Send the message -- call
POST /api/sendwith the channel, chatId, and text - Report the result -- tell the user whether the send succeeded or failed
Send API
curl -X POST http://localhost:$PORT/api/send \
-H "Content-Type: application/json" \
-d '{
"channel": "feishu",
"chatId": "oc_xxxx",
"text": "Hello from the bot!"
}'Request Fields
| 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) |
Response
200 { "ok": true }-- message sent successfully404-- channel not found (check available channels)501-- channel does not support proactive send503-- no channel adapters available
Error Handling
If the send fails, check the HTTP status code:
- For
404, runGET /api/channelsand inform the user which channels are actually available - For
501, explain that the target channel adapter does not support proactive sending - For
503, inform the user that no IM adapters are currently running
Discovering Available Channels
Before sending, check which channels are available:
curl http://localhost:$PORT/api/channelsReturns:
{
"channels": [
{ "name": "feishu", "canSend": true },
{ "name": "slack", "canSend": true }
]
}Finding Chat IDs
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}.
Guidelines
- Always confirm with the user before sending to a new chat for the first time
- For DMs, make sure the recipient has interacted with the bot before (most platforms require this)
- Keep messages concise -- follow the im-adapter formatting guidelines
- If the user says "send to the group" without specifying which one, check the current conversation context or ask
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

