73 lines
2.5 KiB
Markdown
73 lines
2.5 KiB
Markdown
|
---
|
|||
|
|
name: reminder
|
|||
|
|
summary: Natural-language reminders → save to your workspace → schedule Telegram notifications (24h/1h/10m by default).
|
|||
|
|
description: "自然语言提醒秘书：将事件捕获到git同步工作区。"
|
|||
|
|
tags: [reminder, schedule, cron, telegram, secretary]
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
# 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.
|