asets-gobizit/myday

MyDay — Daily productivity assistant

Single-pane view of Danny's schedule across Zoho Calendar (which already syncs Google Calendar inbound) plus a 48-hour scan of work + personal email for meeting-related updates. Lets Danny read, create, modify, and cancel events with natural language.

Single source of truth for calendar: Zoho Calendar. Google Calendar events are synced into Zoho via Zoho's native Google integration, so the skill never calls a Google API.

---

Constants (hardcoded)

| Key | Value | |---|---| | Timezone | Europe/Madrid | | Display date format | DD/MM/YYYY | | Display time format | HH:mm (24-hour) | | Zoho Books org ID | 20100889648 | | Zoho work mail (Himalaya) | zoho-danny ([email protected]) | | Personal mail (Himalaya) | gmail ([email protected]) | | Cached IDs file | C:\Users\dansk\.claude\projects\C--Users-dansk-Claude\memory\project_myday_setup.md |

The cached IDs file holds caluid (primary calendar) and accountId (Zoho Mail). Both are discovered on first use and reused thereafter.

---

CRITICAL: Date & Time Format Rule

There are two date formats. The skill always converts at the boundary:

| Layer | Format | Example | When | |---|---|---|---| | User-facing (read & write) | DD/MM/YYYY + HH:mm (24h) | 12/04/2026 15:00 | Everything Danny reads or types | | Zoho API wire format | YYYYMMDD and YYYYMMDDTHHmmssZ | 20260412T150000Z | ONLY when calling ZohoCalendar_* MCP tools |

Rules — never violate:

1. Display every date to Danny as DD/MM/YYYY. Never YYYY-MM-DD, never MM/DD/YYYY, never YYYYMMDD.
2. Display every time as 24-hour HH:mm in Europe/Madrid local time.
3. Accept Danny's input as DD/MM/YYYY OR natural language ("tomorrow at 3pm" = 15:00, "next Monday at 10").
4. Convert to the Zoho wire format immediately before the MCP call.
5. Convert API responses immediately after the call, before showing or storing.
6. The Zoho wire format must NEVER appear in any message Danny sees.
7. Madrid local time → UTC conversion: respect DST. If unsure of the offset, compute it from the current date command output rather than guessing.

Quick reference for the conversion:

• 12/04/2026 → API date: 20260412
• 12/04/2026 15:00 Madrid (CEST = UTC+2) → API datetime: 20260412T130000Z
• 12/04/2026 15:00 Madrid (CET = UTC+1) → API datetime: 20260412T140000Z

---

First-run setup (one-time)

The first time the skill is invoked, the cached IDs file may not exist or may be incomplete. Bootstrap as follows:

1. Read project_myday_setup.md. If caluid and accountId are both present, skip to the requested feature.
2. If caluid is missing:
   • Call ZohoCalendar_getAllCalendar with {category: "own"}.
   • From the response, pick the calendar marked as default/primary (look for isdefault: true or the one matching [email protected]).
   • Save caluid to project_myday_setup.md.
3. If accountId is missing:
   • Call ZohoMail_getMailAccounts (no params).
   • If that returns an OAuth scope error, ask Danny to paste his Zoho Mail accountId once and save it. (One-time only.)
   • Save accountId to project_myday_setup.md.
4. After setup, also append a one-line entry to MEMORY.md if not already there.

If MCP authorization is broken (token expired), tell Danny exactly which MCP server to reconnect in claude.ai (CRM-Activities-Engagement-MCP-Server) — don't keep retrying.

---

HOW TO INVOKE

Trigger phrases (be generous in matching):

Daily summary:

• "what's my day", "my day", "myday", "my schedule", "today's schedule", "any meetings today", "agenda"

Week view:

• "what's my week", "this week", "week ahead", "upcoming week"

Next event:

• "what's next", "next meeting", "what do I have coming up"

Create:

• "schedule a meeting", "add event", "book a meeting", "set up a call with…", "new meeting"

Modify:

• "move my meeting", "reschedule", "change my [event] to…", "push my [event] to…"

Delete:

• "cancel my meeting", "delete event", "remove my call with…"

Availability:

• "am I free at…", "am I available on…", "do I have anything at…", "find me a slot"

---

Feature 1 — Daily summary

Calendar (today + 48h forward):

1. Compute today and today+2 days in Europe/Madrid (use date if needed).
2. Convert each to YYYYMMDD.
3. Call ZohoCalendar_getEventsInRange with {start: <today>, end: <today+2>}.
4. Convert each returned event's start/end back to DD/MM/YYYY + HH:mm.
5. Group events by day (Today / Tomorrow / Day after tomorrow).

Email scan (48h back): 6. Scan Zoho Mail (last 48 h) via ZohoMail_SearchEmails for keywords: meeting, calendar, invite, confirmed, rescheduled, cancelled, postponed, agenda, call, zoom, teams, appointment, booking, reservation. 7. Scan Gmail in parallel via Himalaya CLI:

himalaya envelope list -a gmail --page-size 50 -o json "after <YYYY-MM-DD of 48h ago>"

Then filter envelopes whose subject contains any of the keywords above (case-insensitive). For deeper context on a hit, run himalaya message read -a gmail <id>. 8. Render output (tables + notes):

## Today — <Weekday>, DD/MM/YYYY

| Time         | Event           | Location | With           |
|--------------|-----------------|----------|----------------|
| HH:mm–HH:mm  | …               | …        | …              |

## Tomorrow — <Weekday>, DD/MM/YYYY

| Time         | Event           | Location | With           |
|--------------|-----------------|----------|----------------|
| …            | …               | …        | …              |

## <Day after tomorrow — Weekday>, DD/MM/YYYY   ← only if events exist

| Time         | Event           | Location | With           |
|--------------|-----------------|----------|----------------|
| …            | …               | …        | …              |

## Notes
- ⚠ Conflict: <details>     ← only if events overlap
- 🟢 Free block: HH:mm–HH:mm (Xh)   ← only if a gap > 1h exists in working hours

## Meeting-related                          ← only if meeting-related emails were found

| # | Source | Date | Subject | With (email) |
|---|--------|------|---------|--------------|
| 1 | Zoho/Gmail | DD/MM/YYYY | Subject line | from/to email of the person Danny is meeting with |

→ Extract the contact email from the `from` or `to` field of the envelope. For calendar updates/invites, the participant email is usually in the subject or the `from` field. Show it in the "With (email)" column.
→ **Time filter:** Only show meeting-related emails about meetings happening **today or in the next 2 days** (today + 48h forward). Past meetings (yesterday or earlier) are irrelevant — discard them.
→ Number each row sequentially starting from 1. Danny can reference rows by number to request removal or action.

## Action items                             ← only if actionable emails were found

| # | Source | Date | Subject | Details (sent to) |
|---|--------|------|---------|-------------------|
| 1 | Zoho/Gmail | DD/MM/YYYY | Subject line | Key detail + recipient email address (`to` field) |

→ Always include the `to` email address in the Details column so Danny knows which account received it.
→ Number each row sequentially starting from 1 (independent numbering from Meeting-related table). Danny can say "remove 3, 5" to drop rows.

If a section has nothing to show, omit it (don't print empty tables).

---

Feature 2 — Week view

1. Range = today through today + 6 days.
2. One call: ZohoCalendar_getEventsInRange with the full range as YYYYMMDD.
3. Group results by day.
4. Render one table per day, dates as DD/MM/YYYY.
5. Footer line: total events this week, busiest day.

---

Feature 3 — Next event

1. Get today's events.
2. Filter to events whose start time is later than now (Europe/Madrid).
3. Show the next 3, with a countdown ("in 45 min", "in 2h 10min").

---

Feature 4 — Create event

1. Parse from Danny's request: title, date, start time, end time (or duration → default 60 min), participants, location, description.
2. For each named participant, run the contact resolution chain (below) → email.
3. Compute dateandtime.start and dateandtime.end in YYYYMMDDTHHmmssZ.
4. Run ZohoCalendar_getUserBusySlots for that window. If conflict → warn and offer alternatives via ZohoCalendar_findTimeSlots.
5. Confirm with Danny first in DD/MM/YYYY HH:mm format:

   Create Title on DD/MM/YYYY at HH:mm–HH:mm with email1@…, email2@…?

6. On explicit confirmation only, call ZohoCalendar_addEvent with:

   {
     "caluid": "<from cache>",
     "title": "<title>",
     "description": "<optional>",
     "dateandtime": {
       "start": "YYYYMMDDTHHmmssZ",
       "end": "YYYYMMDDTHHmmssZ",
       "timezone": "Europe/Madrid"
     },
     "attendees": [{"email": "..."}, ...]
   }
   

7. Confirm success, displaying the event back in DD/MM/YYYY HH:mm.

---

Feature 5 — Modify event

1. Use ZohoCalendar_searchEvents with keywords from the request (search range = today − 7 days to today + 30 days unless Danny specified).
2. If multiple matches → list them in DD/MM/YYYY HH:mm, ask which one.
3. Parse the new time/date.
4. Check availability at the new time (getUserBusySlots).
5. Confirm:

   Move Title from DD/MM/YYYY HH:mm to DD/MM/YYYY HH:mm?

6. On confirmation, call ZohoCalendar_updateEvent with the event's uid, current etag, and updated dateandtime. Etag must come from the search result — never invent it.
7. Confirm success.

---

Feature 6 — Delete / cancel event

1. Search to identify the target event.
2. Always confirm:

   Cancel Title on DD/MM/YYYY at HH:mm? This cannot be undone.

3. On explicit confirmation, call ZohoCalendar_deleteEvent with uid, etag, caluid.
4. Confirm deletion.

---

Feature 7 — Availability check

1. Parse date/time (accept DD/MM/YYYY or natural language).
2. Call ZohoCalendar_getUserBusySlots for the requested window.
3. Report:
   • Free → "Yes, you're free DD/MM/YYYY HH:mm–HH:mm."
   • Busy → "Busy: Event title (DD/MM/YYYY HH:mm–HH:mm)." Then offer nearest free slots via findTimeSlots, all in DD/MM/YYYY HH:mm.

---

Contact resolution chain

When Danny mentions a person by name and we need their email:

1. Zoho Books contacts — ZohoBooks_list_contacts with organization_id: 20100889648, contact_name_contains: <name>.
2. Recent Zoho Mail senders — ZohoMail_listEmails last 50 messages, scan from field for the name.
3. Recent Gmail senders — himalaya -a gmail envelope list --page-size 50 -o json, scan from field.
4. Multiple matches — present them as a numbered list, ask Danny to pick.
5. No match — ask Danny for the email directly. Never invent an email.

Once resolved, optionally cache the name → email mapping to project_myday_setup.md for next time.

---

Email intelligence (used by Daily summary)

• Keywords (case-insensitive): meeting, calendar, invite, confirmed, rescheduled, cancelled, postponed, agenda, call, zoom, teams, appointment, booking, reservation.
• Scan window: Emails (Action items) = 48h back from now. Calendar + Meeting-related emails = today + 48h forward only. Discard any meeting-related emails about meetings that already happened (yesterday or earlier).
• Sources: Zoho Mail (MCP ZohoMail_SearchEmails or ZohoMail_listEmails + filter) AND Gmail (Himalaya CLI).
• Filter rule: only surface emails containing actionable schedule info (date/time/people). Discard generic newsletters that happen to contain a keyword.
• Exclude: Holistic CRM support tickets (emails from/to [email protected] or @holisticcrm.co.il that are client support threads). These are handled separately and should never appear in the daily summary.
• Output format: Two tables:
  1. Meeting-related — columns: Source, Subject, With (email). Extract the contact's email from the envelope from/to fields. For calendar invites/updates the participant is typically in from; for outbound meetings check to.
  2. Action items — columns: Source, Subject, Details (sent to). Always append the to email address so Danny knows which mailbox received it.

---

Response rules

• Default format: Tables for schedules, bullets for notes (rich markdown).
• Telegram format: When the prompt contains "for Telegram" or "plain text" or "no markdown tables", use phone-friendly plain text:
  • No markdown tables — use emoji bullets and indented lines instead
  • Keep it scannable on a small screen
  • Use this structure:

    ☀️ Good morning Danny — <Weekday>, DD/MM/YYYY
    
    📅 TODAY
    • HH:mm–HH:mm  Event title (Location)
    • HH:mm–HH:mm  Event title
    
    📅 TOMORROW
    • HH:mm–HH:mm  Event title
    
    📬 MEETING-RELATED
    • Subject — from [email protected] (Source)
    
    📋 ACTION ITEMS
    • Subject — key detail (sent to [email protected])
    
    ⚠️ Conflicts: None / details
    🟢 Free: HH:mm–HH:mm (Xh block)
    

  • Omit empty sections (same rule as default format)
• Always 24-hour HH:mm, always DD/MM/YYYY.
• Merge Zoho-native + Google-synced events into one chronological list (they're already merged in Zoho's API response, but verify nothing is duplicated by uid).
• Never output raw JSON to Danny unless he explicitly asks.
• Mark conflicts with ⚠.
• Confirm ALL write actions (create, modify, delete) before executing. Use the human-readable DD/MM/YYYY HH:mm format in the confirmation prompt.
• Missing detail (date, time, participant email) → ask, never guess.
• If an MCP call fails with auth error → tell Danny exactly which MCP server needs reconnecting in claude.ai. Don't retry blindly.

---

Files this skill maintains

• C:\Users\dansk\.claude\projects\C--Users-dansk-Claude\memory\project_myday_setup.md — caluid, accountId, optional contact cache.
• C:\Users\dansk\.claude\projects\C--Users-dansk-Claude\memory\MEMORY.md — pointer line.
• C:\Users\dansk\Claude\Obsidian@Claude\MyDay Skill.md — Obsidian vault entry (dual-save rule).