daily-brief

What This Skill Does

The daily-brief skill provides a sophisticated operational observability layer for self-hosted OpenClaw instances. It functions by orchestrating a sequence of log aggregation, intelligent summarization via the secretary agent, and automated dissemination through the Telegram messaging platform. By parsing system logs from your Docker gateway and tracking evolutionary milestones from evolver logs, this skill distills complex raw technical data into a human-readable executive digest. It is specifically engineered to surface critical system health indicators, identify unresolved operational issues, and highlight agent capability progress on a recurring, automated schedule, effectively keeping you informed of your agent's performance without requiring manual intervention.

Installation

To integrate this skill into your environment, ensure your OpenClaw instance is self-hosted and the gateway is reachable at its local endpoint. First, confirm you have jq and curl installed on your host system. Use the following command to fetch the skill from the repository:

clawhub install openclaw/skills/skills/baobaodawang-creater/openclaw-daily-brief

After installation, edit the provided daily_brief.sh script to inject your specific TELEGRAM_BOT_TOKEN, CHAT_ID, and OPENCLAW_TOKEN. Finally, configure your system crontab by running crontab -e and adding the line 5 8 * * * /path/to/your/daily_brief.sh to trigger the report generation every morning at 08:05.

Use Cases

• Proactive Monitoring: Receive alerts for gateway failures before they disrupt your core workflows.
• Evolution Tracking: Monitor how your agent's capabilities grow over time as the evolver process logs updates.
• Executive Oversight: Get a 30-second summary of all unfinished tasks and potential risks, allowing for rapid decision-making regarding system parameters.

Example Prompts

1. "Secretary, summarize today's system logs and highlight any persistent gateway errors."
2. "Draft a brief covering all unresolved issues from the last 24 hours of operation."
3. "Provide a concise evolution report focusing on the new capabilities learned by the agent this week."

Tips & Limitations

• Log Volume: The script currently tails the last 100 lines of logs; if your gateway generates high-volume traffic, consider increasing this limit or adding grep filters to focus on ERROR levels only.
• Security: Ensure your daily_brief.sh file has restricted permissions (chmod 700) because it contains sensitive API tokens.
• Timeout: The curl request has a 180-second timeout; if your system logs are massive, ensure your local secretary agent can process the text quickly enough to avoid connection drops.