work-progress

What This Skill Does

The Work Progress Skill (work-progress) is an essential automation tool designed to monitor the health of your OpenClaw environment. It operates on a 10-minute cadence to perform two primary functions: tracking progress on your daily to-do lists stored in memory/daily/ and managing sub-agent reliability. The skill includes an intelligent 'timeout detection' feature that scans system logs for execution failures or hung tasks. Once an issue is identified, it logs the event in memory/error.md and provides a mechanism for automatic recovery, ensuring that your long-running agents or background tasks do not stall indefinitely. It follows a strict 'silent mode' philosophy, outputting reports only when intervention is required.

Installation

To install, ensure you are within your OpenClaw workspace. You can use the provided install script by navigating to the skill directory or register the cron job manually using the command: openclaw cron add --name "工作进度检查" --schedule '{"kind":"every","everyMs":600000}' --payload '{"kind":"systemEvent","text":"..."}' --session-target main --delivery '{"mode":"none"}'. Alternatively, execute the shorthand installation command: clawhub install openclaw/skills/skills/amd5/work-progress.

Use Cases

• Continuous Monitoring: Keep track of pending development tasks without manual checks.
• Agent Resilience: Automatically detect and resolve timeouts for long-running sub-agents during complex workflows.
• Error Logging: Centralize system errors in a dedicated memory/error.md file for easy debugging.
• Automated Reporting: Maintain a clutter-free interface by only receiving notifications when a task is overdue or an error occurs.

Example Prompts

1. "Check if there are any outstanding tasks or timeout errors in the current session."
2. "Show me the last 10 minutes of error logs recorded by the work-progress skill."
3. "Force a manual progress scan to ensure all sub-agents are running correctly."

Tips & Limitations

• Silent Reporting: The skill uses a 'NO_REPLY' policy for healthy statuses to avoid notification fatigue.
• Log Pathing: Ensure your environment has the correct permissions for the skill to read memory/daily/ and write to memory/error.md.
• Customization: You can modify the CHECK_INTERVAL_MS in the configuration to increase or decrease the frequency of checks based on your workload intensity.