Xiaoding Daily Summary

What This Skill Does

The Xiaoding Daily Summary skill is an automated productivity tool designed for the OpenClaw environment. Its primary function is to track, aggregate, and report on the computational cost associated with your agent's activity. By interfacing directly with the OpenClaw system via the openclaw status --json command, this skill meticulously parses input and output token usage, cache performance, and session logs. It synthesizes this technical data into a professionally formatted Markdown document, providing a clear overview of daily progress, accomplishments, and future planning, all while maintaining a persistent record in your workspace.

Installation

To integrate this skill into your OpenClaw agent, execute the following command in your terminal: clawhub install openclaw/skills/skills/asterisk622/xiaoding-daily-summary Ensure that your environment has sufficient permissions to write files to the ~/.openclaw/workspace/memory/ directory and that your system supports the execution of the bundled cron_daily_summary.py script.

Use Cases

• Project Tracking: Maintain a historical log of daily accomplishments to stay aligned with project goals like EasyClaw or Moltbook development.
• Cost Management: Monitor your百炼 (Bailian) API token consumption to ensure you stay within your budget and optimize prompt efficiency.
• Automation: Schedule daily, end-of-day reports to ensure you never forget to reflect on your progress and plan for the next day.

Example Prompts

1. "每日总结，顺便看看我今天用了多少 token？"
2. "帮我生成今日总结，并统计一下目前的 token 消耗情况。"
3. "token 统计"

Tips & Limitations

• Permissions: The skill requires read/write access to the local file system. Ensure your agent is granted appropriate file-write permissions.
• Data Integrity: When parsing the output of the status command, the script is designed to be robust against logging noise, but ensure your system time is set correctly for accurate timestamping in the generated Markdown files.
• Optimization: This skill is highly effective for power users who leverage large context windows. Regularly checking your 'Cache Read' and 'Cache Write' statistics can provide insights into whether your prompt engineering is effectively utilizing caching mechanisms to save costs.