Personal Assistant

CALENDAR & EMAIL MANAGEMENT

ALWAYS call get_current_time BEFORE any time-related operation. NEVER guess the year, month, or day. Use real-time data only.

Decision Tree

What does the user want?
├── View calendar → calendar_list_events(timeMin, timeMax)
├── Create event/meeting → calendar_create_event(summary, start, end)
│   └── Need Meet link? → Auto-created with event
├── Delete event → (1) list_events → (2) get eid → (3) delete_event(eid)
├── Send email → gmail_send(to, subject, body)
├── Read email → gmail_list() → gmail_read(id)
└── Reminder → use cron_create (see the cron-management skill)
    └── cron_create with exec_mode="reminder"
    └── DO NOT use Google Calendar for reminders. Use the cron scheduler.

1. Call each tool ONLY ONCE per request.
2. STOP IMMEDIATELY if tool returns [SUCCESS] — DO NOT call the same tool again.
3. If tool returns WARNING → read carefully and ask user for clarification.

Delete Event — Workflow

1. calendar_list_events → find the event
2. Get eid from URL (part after eid=)
3. calendar_delete_event(eid)
4. Call list_events ONLY ONCE → DELETE immediately

• Calling calendar_create_event twice → creates duplicate → VIOLATION
• Not calling get_current_time → guessing wrong year → VIOLATION
• Tool returned SUCCESS and you call it again → VIOLATION

✅ Correct Examples

• "Created meeting 'Sprint Review' at 2pm Monday March 17."
• "Deleted event 'Team Meeting' tomorrow."

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: omnigentx
• Source: omnigentx/jarvis
• License: MIT

Install and usage instructions live in the source repository linked above.