AgentSkillsCN

tg-calendar

直接使用 ClawPlanner 的 Postgres/Supabase 数据库，以兼容机器人语义的方式（UTC 存储、用户时区、重复日程、TG/最大 ID），实现日历事件与参与者的创建、读取、更新、重新安排及删除操作。当用户询问日历/事件/提醒/参与者相关问题，或发送/转发包含日期、时间、描述信息的文本时（可将其视为“创建事件”意图），系统将自动触发相应流程。若仅提供了日期而未明确时间，系统会推荐一个合理的默认时间并征询用户确认。此外，当用户请求从 tg_users 中获取时区、语言或姓名信息，或希望从现有事件/类似笔记的描述中提炼有用信息，又或是排查提醒不匹配的问题时，此技能同样大有裨益。

SKILL.md
--- frontmatter
name: tg-calendar
description: Use the ClawPlanner Postgres/Supabase database directly to create, read, update, reschedule, and delete calendar events and participants with bot-compatible semantics (UTC storage, user timezone, recurrence, tg/max IDs). Trigger when user asks about calendar/events/reminders/participants, OR sends/forwards text where date/time/description can be inferred (treat as create-event intent). If date is present but time is missing, propose a reasonable default time and ask confirmation. Also use when user asks to fetch timezone/language/name from tg_users, summarize useful info from existing events/notes-like descriptions, or debug reminder mismatch.

tg-calendar

Operate the existing planner DB used by ClawPlanner.

Core behavior

  • •Treat forwarded/quoted plain text containing actionable date/time/description as an event-creation request.
  • •If date is known but time is absent, suggest a sensible default (e.g., 10:00 for daytime tasks, 19:00 for evening activities) and ask for confirmation before writing.
  • •Resolve and use profile context from public.tg_users: display name, time_zone, language_code, and platform ids (tg_id, max_id).
  • •Keep writes compatible with bot logic in database/db_controller.py, handlers/events.py, and cron_handler.py.

Time and identity rules

  • •Store all datetimes in UTC in DB; show time to users in their timezone (tg_users.time_zone, fallback config.DEFAULT_TIMEZONE_NAME).
  • •Keep tg/max linkage consistent:
    • •events: tg_id, creator_tg_id, max_id, creator_max_id
    • •participants: participant_tg_id, participant_max_id
  • •For edits/reschedules, preserve recurrence semantics or follow bot behavior for creating a shifted copy when requested as “+1 hour / tomorrow”.

CRUD expectations

Create event

  1. •Resolve user row in tg_users and effective timezone/language.
  2. •Parse title/description/date/time/optional end time/participants from user text.
  3. •Convert local datetime to UTC.
  4. •Insert into events with correct recurrence flags and IDs.
  5. •Insert owner (and other users if requested) into event_participants.

Read/list events

  • •Use the same recurrence expansion semantics as the bot (see database/db_controller.py).
  • •When summarizing “notes/events”, extract useful context primarily from events.description, emoji, time ranges, recurrence, and participant rows.

Update event

  • •Support changing description, emoji, start/stop times, recurrence, and participants.
  • •Use bot-compatible updates so reminder selection remains correct.

Reschedule

  • •Handle explicit shifts (+1 hour, tomorrow, specific new datetime).
  • •If user asks to move a single upcoming occurrence of recurrent event, follow cancel/clone semantics used by bot (canceled_events + new/specific event handling as applicable).

Delete/cancel

  • •Delete single non-recurrent events directly.
  • •For recurrent events, support canceling one occurrence when asked.

Required code references

  • •database/db_controller.py (source of truth for semantics)
  • •handlers/events.py (UI flow and intent mapping)
  • •cron_handler.py (reminder selection)
  • •database/models/user_model.py
  • •database/models/event_models.py

References

  • •Read references/schema.md for table/column map.
  • •Read references/queries.md for safe SQL templates.