agentleFS
0xranx0xranx/golembot/skills/message-push/SKILL.md

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

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
  1. Distinctive:

    Follow these steps when the user requests a message push:

    line 23
  2. Distinctive:

    If the send fails, check the HTTP status code:

    line 61
  3. Distinctive:

    Before sending, check which channels are available:

    line 68
  4. Very specific:

    If the user references a group by name rather than ID, check group memory files in memory/groups/ -- the group key format is …

    line 97
  5. Distinctive:

    Always confirm with the user before sending to a new chat for the first time

    line 101
  6. Distinctive:

    Keep messages concise -- follow the im-adapter formatting guidelines

    line 103
  7. Distinctive:

    If the user says "send to the group" without specifying which one, check the current conversation context or ask

    line 104

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Identify the target -- determine the channel name and chatId from the user's request
  2. Discover available channels -- call GET /api/channels to confirm the channel exists and supports sending
  3. Compose the message -- draft the text content, following im-adapter formatting guidelines
  4. Confirm with the user -- if this is the first time sending to this chat, show the draft and ask for approval
  5. Send the message -- call POST /api/send with the channel, chatId, and text
  6. 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

FieldTypeRequiredDescription
channelstringyesChannel name: feishu, dingtalk, wecom, slack, telegram, discord
chatIdstringyesChat/group/conversation ID on the target platform
textstringyesMessage content (Markdown supported)

Response

  • 200 { "ok": true } -- message sent successfully
  • 404 -- channel not found (check available channels)
  • 501 -- channel does not support proactive send
  • 503 -- no channel adapters available

Error Handling

If the send fails, check the HTTP status code:

  • For 404, run GET /api/channels and 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/channels

Returns:

{
  "channels": [
    { "name": "feishu", "canSend": true },
    { "name": "slack", "canSend": true }
  ]
}

Finding Chat IDs

Chat IDs are platform-specific. Common ways to find them:

ChannelHow to find chatId
FeishuGroup settings > Group ID (starts with oc_)
SlackChannel ID from URL (C prefix) or user ID (U prefix) for DMs
TelegramChat ID from message events (negative for groups)
DiscordChannel ID from URL or developer mode
DingTalkConversation ID from webhook or API
WeComChat 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.