PromptsOpenClaw
Nightly business council
Use case
The numbers live in ten different tools, so the pattern stays invisible. Once a night, eight specialists each read only the slice that matches their job, in parallel, and a synthesizer turns that into a short numbered list. You reply with a number when you want the longer version, and you approve or reject so the next night fits you better.
What to connect
The local databases from social tracking, CRM, meetings, and the newsletter cache, plus Slack and Asana if those skills are on. YouTube, Instagram, and X credentials if the collectors should pull fresh stats.
Setup
- List which collectors are actually connected. Leave the others out rather than inventing numbers.
- Pick eight specialist names and the one data slice each may see. A useful start: revenue, growth, content, pipeline, delivery, retention, cost, and a skeptic who only sees claims the others made.
- Schedule the run at night, at a different minute from the security council and the platform council, so they do not pile onto the same quota.
- Set the Telegram topic to [BUSINESS COUNCIL].
- Save preference notes in business-council-notes.md and confirm a reject on night one is still there on night two.
Edit before you send: Which sources are connected, the eight specialist names, the run time, and the Telegram topic.
Prompt to paste into OpenClaw
Save this as a skill named business-council. Run every night at [22:30] [TIMEZONE]. Collectors, and only the ones that are connected: YouTube analytics, Instagram per-post engagement, X analytics, CRM contacts, email activity, meeting transcripts, cron job reliability, Slack messages, Asana tasks, HubSpot deals, newsletter stats. If a source is missing, skip it and name it at the bottom. Do not fill the gap with a guess. Create these specialists: [RevenueGuardian], [GrowthStrategist], [ContentLead], [PipelineLead], [DeliveryLead], [RetentionLead], [CostLead], [SkepticalOperator]. Run all eight in parallel. Each one sees only the data for their domain. They do not read each other's notes. Then a synthesizer: - Merge the findings. - Drop duplicates. - Rank what is left by how much it changes the business if I ignore it. - Send a numbered digest to the [BUSINESS COUNCIL] Telegram topic. One or two lines per item. No tables. If I say "tell me more about #3", answer with the evidence, the source, and what I would do next. If I approve or reject an item, append the reason to business-council-notes.md and read that file before the next run. If there is nothing worth changing, send "No change worth a recommendation." Do not invent a list to fill the message.
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.