WastePickupReminder
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill is mostly local and purpose-aligned, but its cron logic can automatically message configured contacts for all future pickups at a matching time, not just the intended reminder window.
Before enabling the cron job, review or fix the date logic so reminders only fire for the intended pickup window, verify every target ID and template, and protect any webhook URLs or contact details stored in the local config.
Findings (4)
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.
The assistant could send misleading or premature reminders to WhatsApp, Telegram, Discord, or email targets, potentially spamming groups or stopping real reminders if someone confirms a false alert.
The cron code skips only past dates and checks only the clock time. It does not verify that the pickup is tomorrow, today, or otherwise due, so at a configured time it can emit reminders for every current or future scheduled pickup.
for date, containers in schedule.items():
# Skip past dates
if date < current_date:
continue
...
if time_slot != current_time:
continueAdd explicit due-date logic, such as day-before/day-of checks, enforce a small reminder limit, and test with a dry-run or approval step before enabling automated sending.
Anyone who can read or reuse the configured webhook or target IDs may be able to direct messages to those channels, depending on the service.
The skill supports third-party channel identifiers, including Discord webhook URLs. A webhook URL can act like a posting credential, even though no credential is hardcoded in the code.
"me_discord": {"id": "https://discord.com/api/webhooks/...", "channel": "discord"}Store configuration files carefully, use least-privilege webhooks or bot permissions, and rotate webhook URLs if they are exposed.
The stored files may contain household schedule details, phone numbers, chat IDs, webhook URLs, and message templates that affect future automated actions.
The skill keeps persistent local configuration and schedule data that the cron job later reuses to generate assistant-readable message instructions.
The skill stores configuration in: `/data/.openclaw/workspace/data/waste-reminder/` `config.json` ... `schedule.json`
Keep the files private, review templates and targets after changes, and avoid placing secrets or unnecessary personal data in the reminder configuration.
The reminder process can continue running and producing message requests until the cron job is removed or disabled.
The skill asks the user to create a recurring background job. This is disclosed and expected for reminders, but it is persistent automation.
Add ONE cron job that runs every 15 minutes: - Name: "Waste Reminder Check" - Schedule: every 15 minutes
Enable the cron job only after verifying the configuration, and document how to disable it if reminders are no longer needed.