PromptsOpenClaw
Telegram topics and Slack, each with one job
Use case
An assistant that posts everything into one chat becomes noise you mute. You split Telegram into topics with a single kind of message each, and you let Slack wake the assistant only when you mention it. Files arrive as files. A task gets an acknowledgement and a result, and then it stops talking.
What to connect
A Telegram supergroup with topics enabled, and a Slack app in the workspace where ideas and links already live.
Setup
- Create topics for daily brief, CRM, email, knowledge base, business council, security, video ideas, earnings, cron failures, financials, health, and platform health. Add others only when a skill needs a home.
- Set FINANCIALS to your DM only. That topic does not exist in the group.
- In Slack, turn on mention-only mode, set the allowlist to your user id, and enable an eyes reaction on receipt.
- Save the prompt as messaging-rules and confirm a test file arrives as a file, not a link.
Edit before you send: The topic names, your Slack user id, and which chat is the financials DM.
Prompt to paste into OpenClaw
Save this as a skill named messaging-rules. These rules apply to every other skill. Telegram topics, one content type each: - [DAILY BRIEF], [CRM], [EMAIL], [KNOWLEDGE], [BUSINESS COUNCIL], [SECURITY], [VIDEO IDEAS], [EARNINGS], [CRON], [HEALTH], [PLATFORM]. - Financial notes go to my DM only, never a group topic. - A message belongs in one topic. Do not cross-post the same update. - When the result is a file, send the file. Do not send a link in its place. - [CRON] receives failures only. A quiet job stays quiet. Slack: - Mention-only. Ignore channel chatter. - Only [MY SLACK USER ID] may invoke you. - React with eyes when a mention arrives so I can see it landed. - The reply is one complete message. Do not post "thinking" or partial updates. Across both: - Two messages per task at most: a short acknowledgement when the work will take a while, then the result. - Do not narrate the steps in between.
More OpenClaw prompts
- Personal CRM from mail and calendar
A year of email and meetings is a pile of names you cannot search. OpenClaw reads Gmail and Google Calendar, drops newsletters and cold pitches, and keeps a local profile for each person worth remembering. You ask in plain language who you know at a company, or who has gone quiet.
- Meeting action items with an approval queue
Meetings end and the promises disappear. OpenClaw waits until a meeting is over, pulls the Fathom transcript, matches the room to your CRM, and sends you each action item to approve. Approved items become Todoist tasks. Things other people owe you stay on a waiting-on list, except people on your own team.
- Urgent email, only when it can wait no longer
You do not live in the inbox, including on weekends. OpenClaw checks mail on a timer, ignores senders you have already marked as noise, and pings a Telegram topic only when something needs you now. When you say an alert was wrong, the next check is stricter.
- Knowledge base you fill from a Telegram topic
Links you meant to remember are scattered across chats. You drop a URL into one Telegram topic. OpenClaw saves the article, the video transcript, the full post thread, or the PDF, then you ask later in plain language. A new save can point at something you already kept.