Reminder

Capture natural-language events in Chinese or English, save them to your workspace, and schedule Telegram reminders with default 24h, 1h, and 10m notifications.

Security Scan

The skill's stated purpose (capture reminders and schedule Telegram notifications) is plausible, but there are several inconsistencies and missing details—most notably undeclared environment/credential requirements, vague cron/Telegram delivery instructions, and metadata mismatches—that warrant caution before installing.

Purpose & Capability

The described functionality (parse natural-language events, store them in the workspace, and schedule reminders) aligns with the files present (events template) and being instruction-only. However, _meta.json owner/version differ from the registry metadata included in the submission, which is an inconsistency that could indicate repackaging or stale metadata.

Instruction Scope

SKILL.md instructs the agent to write/read ~/.openclaw/workspace/reminders/events.yml and to 'create cron jobs' that deliver to the user's current Telegram. It does not show the exact cron commands or payloads, and it gives the agent wide discretion to schedule jobs. The instructions also reference asking clarifying questions and modifying events.yml; those behaviours are expected, but the vagueness around how cron jobs are created/delivered is concerning because cron jobs could run arbitrary commands if not constrained.

Install Mechanism

There is no install spec and no code files — it is instruction-only. That minimizes disk-write risk; nothing is downloaded or installed by the skill itself.

Credentials

SKILL.md references REMINDER_TZ and REMINDER_OFFSETS_MINUTES, but the skill declares no required env vars or credentials. It also claims to deliver reminders to the 'current Telegram' without declaring any Telegram API key/token or stating how Telegram auth is provided. This mismatch (undeclared env vars/credentials) is an incoherence that should be clarified before use.

Persistence & Privilege

The skill is not always-enabled and does not request system-wide configuration. It writes to a workspace file under ~/.openclaw and schedules platform cron jobs; those are reasonable for a reminder skill provided the cron actions are constrained. It does not attempt to modify other skills' configs.

What to consider before installing

Before installing, ask the skill author or maintainer to clarify: (1) how Telegram delivery is authenticated—where the Telegram token comes from and whether the skill will ever ask for/store it (the SKILL.md mentions sending to 'current Telegram' but no credentials are declared); (2) what exact cron jobs/commands will be scheduled (inspect the cron payload to ensure it won't run arbitrary shell commands); (3) whether REMINDER_TZ and REMINDER_OFFSETS_MINUTES should be set as env vars (they're referenced but not declared); and (4) why registry metadata (owner/version) differs from the included _meta.json. If you cannot get these clarifications, test the skill in a restricted/sandbox environment and review any scheduled cron jobs and the events.yml contents before allowing it to run in a real account. Avoid storing secrets in the workspace and confirm LOCAL_CONFIG.md is properly gitignored as suggested.

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.