Reminder
PassAudited by ClawScan on May 1, 2026.
Overview
This reminder skill is coherent and benign, but it stores personal schedule data in your workspace and creates persistent Telegram cron reminders.
Install only if you are comfortable with the agent saving reminder details to `~/.openclaw/workspace/reminders/events.yml` and creating Telegram cron notifications. Review confirmations for parsed dates and times, and keep any synced workspace or Git repository private if reminders include personal information.
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.
Incorrectly parsed or outdated events could result in unwanted Telegram reminders until the cron jobs are removed or replaced.
The skill intentionally creates future scheduled actions. This is disclosed and central to reminder delivery, but it is persistent behavior that users should be aware of.
Create `cron` jobs for each reminder time (delivery to current Telegram).
Check the confirmation message for the resolved date and time, and ask the agent to cancel or update reminders when plans change.
Personal reminders, birthdays, meetings, or deadlines may remain in the workspace and be reused in later queries.
The skill persists personal event data in a workspace file and later reads it to answer upcoming-event queries. This is purpose-aligned, but it creates retained personal context.
User data lives in the workspace at: - Events file: `~/.openclaw/workspace/reminders/events.yml`
Avoid storing highly sensitive details in reminder notes, review the events file periodically, and keep any synced repository private.
If the workspace is synced to a remote or shared repository, reminder details could be exposed outside the local machine.
The artifact explicitly encourages storing reminder data in a workspace that may be synced with Git or claw-roam. That is useful for backup, but it can broaden where personal schedule data is stored.
Store events in a **workspace data file** (easy to back up & sync via Git/`claw-roam`)
Confirm where the workspace is synced, keep the repository private, and exclude reminder data from sync if it contains sensitive information.