Task Supervisor
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill is useful for tracking long tasks, but it automatically creates recurring background reporters and sends task details to an unclear messaging service, which needs review.
Before installing, confirm that you want automatic background progress reporters, verify exactly which messaging service and recipient will receive updates, and make sure paused tasks stop their cron jobs. Do not include secrets or sensitive details in task logs unless you are comfortable with them being stored in `.tasks/` and summarized in status messages.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A background reporter may keep running and sending updates after the user expects the task to be paused or stopped.
The skill directs the agent to create an autonomous scheduled reporter. Cleanup is tied to done or failed status, while the skill also uses paused status for stuck tasks, leaving a plausible path for the reporter to continue running.
At task start, spawn a cron reporter using `exec` ... `openclaw cron add "task-report-<SLUG>"` ... `Remove this cron when Status=done or Status=failed.`
Require explicit user approval before creating a cron job, include a clear stop condition for paused tasks, and provide a visible command or instruction to list and remove active task-report crons.
Task details, blockers, or sensitive project context could be sent to an unexpected messaging service or recipient.
The artifact names two different messaging destinations and instructs periodic transmission of task status outside the local task file, without defining the recipient, account, or data boundary.
`periodic WhatsApp reports` ... `send a Feishu message to the user with progress update. Include: completed steps, current step, blockers if any.`
Clarify the exact messaging provider and recipient, ask the user before sending external updates, and document what task information will be included.
Local task files may retain sensitive task details and be reused in later status updates.
The skill persistently stores task progress and later reuses those files for reports and heartbeat responses. This is purpose-aligned, but users should know that task summaries and logs may persist locally.
Create a task file at `.tasks/<TASK-SLUG>.md` ... `Append a Log entry` ... `On heartbeat, check `.tasks/` for any `in_progress` tasks`
Avoid putting secrets in task logs, periodically review or delete `.tasks/` files, and treat task-file contents as persistent context rather than temporary notes.