Daily Brief

Send a daily operational brief from your self-hosted OpenClaw to Telegram — agent health, unresolved issues, and weekly evolution highlights, every morning.

Security Scan

The skill's requirements and runtime instructions are consistent with its stated purpose — collecting gateway/evolver logs, summarizing them via the local OpenClaw agent, and posting the result to Telegram — but it will transmit potentially sensitive logs to an external chat and that privacy risk should be considered before installation.

Purpose & Capability

Name/description match the runtime actions: the script collects OpenClaw gateway logs, reads evolver logs, calls the local OpenClaw chat completion endpoint (secretary agent) and posts to Telegram. Required binaries (bash, curl, jq, docker) and env vars (OPENCLAW_TOKEN, TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID) are appropriate for this workflow.

Instruction Scope

Instructions explicitly read docker logs from the openclaw-gateway container and tail /tmp/evolver-*.log, then submit those contents to a local OpenClaw completion endpoint and forward the summary to Telegram. This is within scope, but it means logs (which may contain secrets or sensitive operational data) will be aggregated and sent off-host.

Install Mechanism

Instruction-only skill with no install spec or downloaded code — nothing will be written to disk by the skill itself. Low install risk.

Credentials

Requested env vars are proportional to the task (OpenClaw token to call the local API; Telegram bot token and chat id to send messages). However, those credentials enable sending potentially sensitive data externally; Telegram is a third-party endpoint outside your network, so token and chat selection matter.

Persistence & Privilege

always:false and user-invocable:true (defaults) — the skill is not forced into every agent run and does not request elevated platform privileges or changes to other skills' configs.

Assessment

This skill does what it says: it collects container logs and an evolver log, summarizes them with your local 'secretary' agent, and posts the report to Telegram. Before installing, consider: 1) Do your gateway/evolver logs contain secrets (API keys, tokens, PII)? If so, add log redaction or filtering before sending. 2) Ensure the Telegram chat is private and the BOT token is stored/rotated securely. 3) Limit who can read the cron job and script (run under an appropriate non-root account). 4) Confirm the OPENCLAW_TOKEN scope is minimal and that the 'secretary' agent is trusted. 5) Test in a staging environment first to verify nothing sensitive is leaked. If you need higher confidentiality, consider delivering reports to an internal endpoint instead of Telegram or implementing log sanitization.

daily-brief packages a production-style daily report workflow for self-hosted OpenClaw users.

It generates a structured morning digest and sends it to Telegram, with focus on:

• Agent/system health signals from gateway logs
• Unfinished or risky items inferred from recent runtime behavior
• Capability evolution highlights from latest evolver logs

Typical deployment scenario

Use this skill when your OpenClaw instance is self-hosted and you want a reliable daily operations snapshot at a fixed time (for example 08:05 every day).

Required components

• secretary agent configured and available
• system cron enabled
• Telegram bot delivery configured
• OpenClaw gateway reachable at local endpoint

Real script pattern (redacted example)

The following is a redacted usage example adapted from daily_brief.sh:

#!/bin/bash
BOT_TOKEN="${TELEGRAM_BOT_TOKEN}"
CHAT_ID="${TELEGRAM_CHAT_ID}"
OPENCLAW_TOKEN="${OPENCLAW_TOKEN}"

LOGS=$(docker logs openclaw-gateway --since 24h 2>&1 | tail -100)

EVOLVER_LOG=""
LATEST_EVOLVER=$(ls -t /tmp/evolver-*.log 2>/dev/null | head -1)
if [ -n "$LATEST_EVOLVER" ]; then
  EVOLVER_LOG=$(tail -50 "$LATEST_EVOLVER")
fi

PROMPT="You are the private secretary. Build a concise daily brief with:
1) system status
2) what happened today
3) issues found
4) resolved vs unresolved
5) items requiring executive attention

System logs:
${LOGS}

Evolution report:
${EVOLVER_LOG}"

RESPONSE=$(curl -s -X POST http://127.0.0.1:18789/v1/chat/completions \
  -H "Authorization: Bearer ${OPENCLAW_TOKEN}" \
  -H "Content-Type: application/json" \
  -H "x-openclaw-agent-id: secretary" \
  --max-time 180 \
  -d "{\"model\":\"openclaw\",\"messages\":[{\"role\":\"user\",\"content\":$(echo "$PROMPT" | jq -Rs .)}]}")

RESULT=$(echo "$RESPONSE" | jq -r '.choices[0].message.content // "Secretary unavailable"')

curl -s -X POST "https://api.telegram.org/bot${BOT_TOKEN}/sendMessage" \
  -d chat_id="${CHAT_ID}" \
  --data-urlencode text="${RESULT}"

Cron example

5 8 * * * /Users/lihaochen/openclaw/daily_brief.sh