Reminder Scheduling Skill

Core Workflow

1. Determine Available Python Command.
2. Check if the service is running (health check).
3. Convert user requests into reminder commands.
4. Execute the reminder command and feed back the result (reminders are sent via email).

1) Determine Available Python Command

• <skill_root>/.venv/Scripts/python.exe

  (if exists)

• py

• python

• python3

2) Ensure Service is Running

• <skill_root>/config/app_config.json

web_api_base

http://{host}:{port}

• GET {api_base}/health

• Use the selected Python command to run

  <skill_root>/scripts/start_server.py

  .
• Request

  GET {api_base}/health

  again.
• If it still fails, report the error and stop.

• Use the

  --daemon

  parameter to start the background service (will write to

  <skill_root>/server.pid

  ).
• If the user does not specify explicitly, first ask if background persistence is needed; if the user agrees, use

  --daemon

  , otherwise run in foreground by default.

3) Parse User Requests (Two Types of Intentions)

A) Relative Time (No Follow-up Needed)

• "Remind me to eat in 2 hours"
• "Remind me to submit the report in 3 days"

python remind.py <offset> <content>

<offset>

1d2h30m10s

<content>

• Extract the original intent text (remove guiding words like "Remind me/Remind me to... later")
• Rewrite into a friendlier prompt
• Example:
  • Original intent: Eat
  • Rewritten content: Hey, it's time to eat! Don't go hungry!

B) Relative Date / Specific Time (Follow-up May Be Needed)

• "Remind me to attend the meeting at 8 AM tomorrow"
• "Remind me to hand in my homework at 9 AM the day after tomorrow"
• "Remind me to attend the meeting at 09:00 on 2026-02-07"

python remind.py --at "<time>" <content>

• When the user says "tomorrow/the day after tomorrow/next week..." but does not specify a specific time, must follow up: "What time should I remind you?"
• If the user provides a specific time, pass it to

  --at

  as is.
• Maximum allowed future time: 30 days (verified by the script). Pass the reminder content directly as the only content parameter.

• Add time prompt to the content
• Example:
  • Original intent: Attend the meeting
  • User-specified time: 08:00 tomorrow
  • Rewritten content: Hey, it's 08:00 now, it's time for the meeting!

4) Execute Reminder Command

• <skill_root>/scripts

python remind.py 2h30m Submit report
python remind.py --at "tomorrow 08:00" Attend meeting

Output to User

• Success: Confirm the reminder content and time (email has been sent/will be sent on time).
• Failure: Display the script error message, and prompt to check the service or configuration.