Progress Reporter

Automatically reports task progress every 10 minutes during execution, including current status, recent work, overall progress, and next steps.

This skill appears to do what it says: periodically scan the local OpenClaw workspace for a running task and write human-readable progress reports into workspace directories. Before installing, check these points: 1) Cron/privileges: SKILL.md asks you to add a crontab entry for /root/.openclaw/..., which requires the user account that adds the cron job to have access to that path — if you install the cron as root it will run with root privileges. Only add the cron if you intend that persistence and privilege level. 2) Workspace paths: the script reads running task JSONs and .log files and writes markdown files under tasks/ and memory/. Ensure those directories contain only data you expect to be read and written locally. 3) No network exfiltration: the script does not make network calls or require credentials, but it will create report files that might be read by other processes — ensure those reports won't be forwarded to external services unless you want that. 4) Dependencies & portability: the script uses common POSIX utilities; jq is used to extract the task field but the script tolerates its absence. If your environment differs (non-root home, different workspace path), edit SKILL.md/report.sh to point to the correct workspace and verify cron user. 5) Logs and retention: the script produces files every run (every 10 minutes if you enable cron); consider log/retention policies to avoid storage growth. If you want tighter guarantees (no persistent cron, different paths, or reduced privilege), modify the crontab instruction and the script before enabling.

Type: OpenClaw Skill Name: progress-reporter Version: 1.0.0 The skill is a utility designed to generate periodic progress reports by monitoring local task and log files within the OpenClaw workspace. The core logic in `report.sh` uses standard shell utilities (bash, jq, grep, tail) to extract task metadata and recent logs, formatting them into markdown files stored locally. While it suggests adding a crontab entry for persistence, this behavior is transparently documented and directly supports the stated purpose of the skill without any evidence of data exfiltration or malicious command execution.