PromptsOpenClaw

Specific purposeNightly · repo, logs, databases

Platform health council

Use case

Security review catches hostile bugs. This pass catches a system that is quietly getting worse: failing cron jobs, a prompt nobody updated, a dependency with a known hole, a database that will fill the disk. You get a numbered list, and silence means it looked fine.

What to connect

The same repo as the security council, cron logs, the CRM database, and the skill folder.

Setup

  1. Schedule this at a different time from security-council. 4:15am is a reasonable gap after a 3:30am security run.
  2. Set the Telegram topic to [PLATFORM].
  3. Run it once and confirm each of the nine areas is either a finding or an explicit "ok".
  4. Confirm a healthy run can collapse to one line, so the topic is not a nightly novel.

Edit before you send: The run time, the repo path, and the Telegram topic.

Prompt to paste into OpenClaw

Save this as a skill named platform-council. Run every night at [4:15] [TIMEZONE]. Read the repo at [REPO PATH] and the logs next to it. Use the model to look at the code and the config. Do not stop at a checklist. Review these nine areas: 1. Cron health: which scheduled jobs failed or did not run. 2. Code quality: debt that is getting worse, named with a file. 3. Test coverage: a path that matters and has no test. 4. Prompt quality: a skill that drifts from the prompt guide. 5. Dependencies: packages that are outdated or have a known vulnerability. Name the package and the advisory. Do not include exploit steps. 6. Storage: databases that are growing fast enough to matter. 7. Skill integrity: a skill that errors when you describe what it should do, or a file the skill expects and cannot find. 8. Config consistency: two config files that disagree. 9. Data integrity: the contact database. Duplicates, empty profiles, or broken links between meetings and people. Send numbered recommendations to the [PLATFORM] Telegram topic. Each item: the area, what you saw, and what I should change. If an area is fine, fold it into a single "ok" line at the end. If everything is fine, send one line: "Platform looks healthy." If I ask for a number, show the evidence.

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.