Reminder

Capture natural-language events, save to your workspace, and schedule Telegram reminders with automatic cron notifications and upcoming event queries.

Security Scan

The skill's instructions and behavior are coherent with a local reminder/cron scheduler that stores events in the user's workspace, but verify how Telegram delivery is implemented and where event files are stored before installing.

Purpose & Capability

The SKILL.md describes a reminder secretary that parses natural-language events, stores them in a workspace file, and schedules Telegram reminders via the platform cron. Required actions (writing an events file and scheduling cron jobs) match that purpose. Minor inconsistency: the skill references delivery to "current Telegram" but does not document any Telegram credential or integration requirement.

Instruction Scope

Runtime instructions are limited to parsing events, writing/updating reminders/events.yml, creating cron jobs via OpenClaw cron, and reading that events.yml to answer queries. It does not instruct reading unrelated system files. Note: the SKILL.md references both an absolute path (~/.openclaw/workspace/reminders/events.yml) and a relative path (reminders/events.yml) — clarify which path the agent will use to avoid accidental writes in unexpected locations.

Install Mechanism

Instruction-only skill with no install spec and no code files included, so nothing is downloaded or written by an installer. Low installation risk.

Credentials

The skill does not request secrets or credentials. It documents optional env vars (REMINDER_TZ, REMINDER_OFFSETS_MINUTES) with sensible defaults, which is proportional. However, it implies sending messages to Telegram without documenting required Telegram credentials or auth — confirm whether the platform's Telegram integration will be used and whether any tokens/chat IDs are needed or stored elsewhere.

Persistence & Privilege

The skill writes event data into the user's workspace and creates OpenClaw cron jobs (its own scheduled tasks). It does not request always:true or modify other skills. Creating cron jobs is an expected capability for a scheduler, but you should confirm what those cron jobs execute and what permissions they run with.

Assessment

Before installing, confirm these points: (1) where exactly events are stored (absolute path vs relative) and that the directory is intended for personal data; (2) whether your Telegram integration or bot credentials are already configured in OpenClaw (the skill does not declare or request a Telegram token); (3) review your gitignore and repo rules so personal events aren't accidentally committed; and (4) inspect what the scheduled cron jobs will execute (commands/targets) so you understand what the scheduler can do and with what permissions.

Reminder (secretary)

A lightweight personal secretary for OpenClaw:

• Tell it events in natural language (Chinese/English).
• It extracts structured info and stores it in your workspace (so Git/claw-roam can sync across devices).
• It schedules Telegram reminders using OpenClaw cron.

What it does

• Capture events from chat (meetings / birthdays / deadlines)
• Store events in a workspace data file (easy to back up & sync via Git/claw-roam)
• Schedule Telegram reminders using OpenClaw cron
• Answer queries like “我最近有什么安排/计划？”

Data (separated from skill)

This skill contains no personal event data.

User data lives in the workspace at:

• Events file: ~/.openclaw/workspace/reminders/events.yml

Template (shipped with the skill):

• skills/reminder/assets/events.template.yml

Config (env)

• REMINDER_TZ (default: Asia/Shanghai)
• REMINDER_OFFSETS_MINUTES (default: 1440,60,10 for 24h/1h/10m)

Capture behavior

When user says something like:

• “后天上午10点有个会”
• “下个月2号我妈生日”
• “周五下午三点交报告”

Do:

1. Parse the event:
   • title
   • start datetime (Shanghai)
   • notes (optional)
   • reminders offsets (default 24h/1h/10m)
   • repeat (optional: yearly/monthly/weekly)
2. If key info is ambiguous (e.g. ‘后天’ date, ‘下个月’ which month, lunar birthday conversion, time missing), ask only the minimal clarifying question(s).
3. Write/update the event in reminders/events.yml.
4. Create cron jobs for each reminder time (delivery to current Telegram).

Reply style

• After scheduling: reply briefly with the resolved datetime + confirmation.
• For cancellations/changes: confirm what was changed and whether cron jobs were removed/replaced.

Queries

If user asks:

• “我最近有什么安排？”
• “下周有什么？”

Then read reminders/events.yml, compute upcoming items (Shanghai time), and summarize.

Notes / safety

• Never commit machine-specific secrets (keep them in LOCAL_CONFIG.md, already gitignored).
• For lunar birthdays: store the canonical lunar date + the computed solar date for the target year; ask how to handle leap months when needed.