[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C49C15DPYTCRPFREN9Q48C":3,"skill-same:01M7C49C15DPYTCRPFREN9Q48C":263},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":27,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7C49C15DPYTCRPFREN9Q48C","email-to-calendar",null,"Extract calendar events and deadlines from emails and create calendar entries. Two modes: monitor your inbox directly, or process emails you forward to a dedicated address. Trigger when a user asks to scan emails for events, mentions an event in an email, or wants to add something from an email to their calendar.","SillyHippy\u002Fzo-skills","SillyHippy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F159052837?v=4","01M7C43A8PDYMCDPTNFYF2RSC1","01M7C43A9CBS76QPH4PPTKXX54",0,"MIT","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: email-to-calendar\nversion: 1.13.1\ndescription: \"Extract calendar events and deadlines from emails and create calendar entries. Two modes: monitor your inbox directly, or process emails you forward to a dedicated address. Trigger when a user asks to scan emails for events, mentions an event in an email, or wants to add something from an email to their calendar.\"\n---\n\n> **CRITICAL RULES - READ BEFORE PROCESSING ANY EMAIL**\n>\n> 1. **NEVER CALL `gog` DIRECTLY** - ALWAYS use wrapper scripts (`create_event.sh`, `email_read.sh`, etc.). Direct `gog` calls bypass tracking and cause duplicates. THIS IS NON-NEGOTIABLE.\n> 2. **IGNORE CALENDAR NOTIFICATIONS** - DO NOT process emails from `calendar-notification@google.com` (Accepted:, Declined:, Tentative:, etc.). These are responses to existing invites, NOT new events. Run `process_calendar_replies.sh` to archive them.\n> 3. **ALWAYS ASK BEFORE CREATING** - Never create calendar events without explicit user confirmation in the current conversation\n> 4. **CHECK IF ALREADY PROCESSED** - Before processing any email, check `processed_emails` in index.json\n> 5. **READ CONFIG FIRST** - Load and apply `ignore_patterns` and `auto_create_patterns` before presenting events\n> 6. **READ MEMORY.MD** - Check for user preferences stored from previous sessions\n> 7. **INCLUDE ALL CONFIGURED ATTENDEES** - When creating\u002Fupdating\u002Fdeleting events, always include attendees from config with `--attendees` flag (and `--send-updates all` if supported)\n> 8. **CHECK TRACKED EVENTS FIRST** - Use `lookup_event.sh --email-id` to find existing events before calendar search (faster, more reliable)\n> 9. **TRACK ALL CREATED EVENTS** - The `create_event.sh` script automatically tracks events; use tracked IDs for updates\u002Fdeletions\n> 10. **SHOW DAY-OF-WEEK** - Always include the day of week when presenting events for user verification\n\n> ⛔ **FORBIDDEN: DO NOT USE `gog` COMMANDS DIRECTLY** ⛔\n>\n> **WRONG:** `gog calendar create ...` or `gog gmail ...`\n> **RIGHT:** `\"$SCRIPTS_DIR\u002Fcreate_event.sh\" ...` or `\"$SCRIPTS_DIR\u002Femail_read.sh\" ...`\n>\n> Direct CLI calls bypass event tracking, break duplicate detection, and cause duplicate events.\n> ALL operations MUST go through the wrapper scripts in `scripts\u002F`.\n\n# Email to Calendar Skill\n\nExtract calendar events and action items from emails, present them for review, and create\u002Fupdate calendar events with duplicate detection and undo support.\n\n**First-time setup:** See [SETUP.md](SETUP.md) for configuration options and smart onboarding.\n\n## Reading Email Content\n\n**IMPORTANT:** Before you can extract events, you must read the email body. Use the wrapper scripts.\n\n```bash\nSCRIPTS_DIR=\"$HOME\u002F.openclaw\u002Fworkspace\u002Fskills\u002Femail-to-calendar\u002Fscripts\"\n\n# Get a single email by ID (PREFERRED)\n\"$SCRIPTS_DIR\u002Femail_read.sh\" --email-id \"\u003CmessageId>\"\n\n# Search with body content included\n\"$SCRIPTS_DIR\u002Femail_search.sh\" --query \"in:inbox is:unread\" --max 20 --include-body\n```\n\n**Note on stale forwards:** Don't use `newer_than:1d` because it checks the email's original date header, not when it was received. Process all UNREAD emails and rely on the \"already processed\" check.\n\n## Workflow\n\n### 0. Pre-Processing Checks (MANDATORY)\n\n```bash\nSCRIPTS_DIR=\"$HOME\u002F.openclaw\u002Fworkspace\u002Fskills\u002Femail-to-calendar\u002Fscripts\"\nCONFIG_FILE=\"$HOME\u002F.config\u002Femail-to-calendar\u002Fconfig.json\"\nINDEX_FILE=\"$HOME\u002F.openclaw\u002Fworkspace\u002Fmemory\u002Femail-extractions\u002Findex.json\"\n\n# Start activity logging\n\"$SCRIPTS_DIR\u002Factivity_log.sh\" start-session\n\n# Check email mode\nEMAIL_MODE=$(jq -r '.email_mode \u002F\u002F \"forwarded\"' \"$CONFIG_FILE\")\n\n# Check if email was already processed\nEMAIL_ID=\"\u003Cthe email message ID>\"\nif jq -e \".extractions[] | select(.email_id == \\\"$EMAIL_ID\\\")\" \"$INDEX_FILE\" > \u002Fdev\u002Fnull 2>&1; then\n    \"$SCRIPTS_DIR\u002Factivity_log.sh\" log-skip --email-id \"$EMAIL_ID\" --subject \"Subject\" --reason \"Already processed\"\n    exit 0\nfi\n\n# Load ignore\u002Fauto-create patterns\nIGNORE_PATTERNS=$(jq -r '.event_rules.ignore_patterns[]' \"$CONFIG_FILE\")\nAUTO_CREATE_PATTERNS=$(jq -r '.event_rules.auto_create_patterns[]' \"$CONFIG_FILE\")\n```\n\n### 1. Find Emails to Process\n\n**DIRECT mode:** Scan all unread emails for event indicators (dates, times, meeting keywords).\n\n**FORWARDED mode:** Only process emails with forwarded indicators (Fwd:, forwarded message headers).\n\n### 2. Extract Events (Agent does this directly)\n\nRead the email and extract events as structured data. Include for each event:\n- **title**: Descriptive name (max 80 chars)\n- **date**: Event date(s)\n- **day_of_week**: For verification\n- **time**: Start\u002Fend times (default: 9 AM - 5 PM)\n- **is_multi_day**: Whether it spans multiple days\n- **is_recurring**: Whether it repeats (and pattern)\n- **confidence**: high\u002Fmedium\u002Flow\n- **urls**: Any URLs found in the email (REQUIRED - always look for registration links, info pages, ticketing sites, etc.)\n- **deadline_date**: RSVP\u002Fregistration\u002Fticket deadline date (if found)\n- **deadline_action**: What user needs to do (e.g., \"RSVP\", \"get tickets\", \"register\")\n- **deadline_url**: Direct link for taking action (often same as event URL)\n\n**URL Extraction Rule:** ALWAYS scan the email for URLs and include the most relevant one at the BEGINNING of the event description.\n\n### 2.1 Deadline Detection\n\nScan the email for deadline patterns that indicate action is required before the event:\n\n**Common Deadline Patterns:**\n- \"RSVP by [date]\", \"Please RSVP by [date]\"\n- \"Register by [date]\", \"Registration closes [date]\"\n- \"Tickets available until [date]\", \"Get tickets by [date]\"\n- \"Early bird ends [date]\", \"Early registration deadline [date]\"\n- \"Must respond by [date]\", \"Respond by [date]\"\n- \"Sign up by [date]\", \"Sign up deadline [date]\"\n- \"Deadline: [date]\", \"Due by [date]\"\n- \"Last day to [action]: [date]\"\n\nWhen a deadline is found:\n1. Extract the deadline date\n2. Determine the required action (RSVP, register, buy tickets, etc.)\n3. Find the URL for taking that action\n4. Flag the event for special handling (see sections below)\n\n### 3. Present Items to User and WAIT\n\nApply event rules, then present with numbered selection:\n\n```\nI found the following potential events:\n\n1. ~~ELAC Meeting (Feb 2, Monday at 8:15 AM)~~ - SKIP (matches ignore pattern)\n2. **Team Offsite (Feb 2-6, Sun-Thu)** - PENDING\n3. **Staff Development Day (Feb 12, Wednesday)** - AUTO-CREATE\n\nReply with numbers to create (e.g., '2, 3'), 'all', or 'none'.\n```\n\n**STOP AND WAIT for user response.**\n\nAfter presenting, record pending invites for follow-up reminders:\n```bash\n# Record pending invites using add_pending.sh\n\"$SCRIPTS_DIR\u002Fadd_pending.sh\" \\\n    --email-id \"$EMAIL_ID\" \\\n    --email-subject \"$EMAIL_SUBJECT\" \\\n    --events-json '[{\"title\":\"Event Name\",\"date\":\"2026-02-15\",\"time\":\"14:00\",\"status\":\"pending\"}]'\n```\n\n### 4. Check for Duplicates (MANDATORY)\n\n**ALWAYS check before creating any event:**\n\n```bash\n# Step 1: Check local tracking first (fast)\nTRACKED=$(\"$SCRIPTS_DIR\u002Flookup_event.sh\" --email-id \"$EMAIL_ID\")\nif [ \"$(echo \"$TRACKED\" | jq 'length')\" -gt 0 ]; then\n    EXISTING_EVENT_ID=$(echo \"$TRACKED\" | jq -r '.[0].event_id')\nfi\n\n# Step 2: If not found, try summary match\nif [ -z \"$EXISTING_EVENT_ID\" ]; then\n    TRACKED=$(\"$SCRIPTS_DIR\u002Flookup_event.sh\" --summary \"$EVENT_TITLE\")\nfi\n\n# Step 3: Fall back to calendar search using wrapper script\nif [ -z \"$EXISTING_EVENT_ID\" ]; then\n    \"$SCRIPTS_DIR\u002Fcalendar_search.sh\" --calendar-id \"$CALENDAR_ID\" --from \"${EVENT_DATE}T00:00:00\" --to \"${EVENT_DATE}T23:59:59\"\nfi\n```\n\nUse LLM semantic matching for fuzzy duplicates (e.g., \"Team Offsite\" vs \"Team Offsite 5-6pm\").\n\n### 5. Create or Update Calendar Events\n\n**Use create_event.sh (recommended)** - handles date parsing, tracking, and changelog:\n\n```bash\n# Create new event\n\"$SCRIPTS_DIR\u002Fcreate_event.sh\" \\\n    \"$CALENDAR_ID\" \\\n    \"Event Title\" \\\n    \"February 11, 2026\" \\\n    \"9:00 AM\" \\\n    \"5:00 PM\" \\\n    \"Description\" \\\n    \"$ATTENDEE_EMAILS\" \\\n    \"\" \\\n    \"$EMAIL_ID\"\n\n# Update existing event (pass event_id as 8th parameter)\n\"$SCRIPTS_DIR\u002Fcreate_event.sh\" \\\n    \"$CALENDAR_ID\" \\\n    \"Updated Title\" \\\n    \"February 11, 2026\" \\\n    \"10:00 AM\" \\\n    \"6:00 PM\" \\\n    \"Updated description\" \\\n    \"$ATTENDEE_EMAILS\" \\\n    \"$EXISTING_EVENT_ID\" \\\n    \"$EMAIL_ID\"\n```\n\nFor direct gog commands and advanced options, see [references\u002Fgog-commands.md](references\u002Fgog-commands.md).\n\n### 6. Email Disposition (Automatic)\n\nEmail disposition (mark as read and\u002For archive) is handled **automatically** by `create_event.sh` based on config settings. No manual step needed - emails are dispositioned after event creation.\n\nTo manually disposition an email:\n```bash\n\"$SCRIPTS_DIR\u002Fdisposition_email.sh\" --email-id \"$EMAIL_ID\"\n```\n\nTo process calendar reply emails (accepts, declines, tentatives):\n```bash\n\"$SCRIPTS_DIR\u002Fprocess_calendar_replies.sh\"           # Process all\n\"$SCRIPTS_DIR\u002Fprocess_calendar_replies.sh\" --dry-run # Preview only\n```\n\n```bash\n# End activity session\n\"$SCRIPTS_DIR\u002Factivity_log.sh\" end-session\n```\n\n## Event Creation Rules\n\n### Date\u002FTime Handling\n- **Single-day events**: Default 9:00 AM - 5:00 PM\n- **Multi-day events** (e.g., Feb 2-6): Use `--rrule \"RRULE:FREQ=DAILY;COUNT=N\"`\n- **Events with specific times**: Use exact time from email\n\n### Event Descriptions\n\n**Format event descriptions in this order:**\n\n1. **ACTION WARNING** (if deadline exists):\n   ```\n   *** ACTION REQUIRED: [ACTION] BY [DATE] ***\n   ```\n\n2. **Event Link** (if URL found):\n   ```\n   Event Link: [URL]\n   ```\n\n3. **Event Details**: Information extracted from the email\n\n**Example WITH deadline:**\n```\n*** ACTION REQUIRED: GET TICKETS BY FEB 15 ***\n\nEvent Link: https:\u002F\u002Fexample.com\u002Ftickets\n\nSpring Concert at Downtown Theater\nDoors open at 7 PM\nVIP meet & greet available\n```\n\n**Example WITHOUT deadline:**\n```\nEvent Link: https:\u002F\u002Fexample.com\u002Fevent\n\nSpring Concert at Downtown Theater\nDoors open at 7 PM\n```\n\n### Duplicate Detection\nConsider it a duplicate if:\n- Same date AND similar title (semantic matching) AND overlapping time\n\nAlways update existing events rather than creating duplicates.\n\n### Creating Deadline Events\n\nWhen an event has a deadline (RSVP, registration, ticket purchase, etc.), create TWO calendar events:\n\n**1. Main Event** (as normal, but with warning in description):\n```bash\n\"$SCRIPTS_DIR\u002Fcreate_event.sh\" \\\n    \"$CALENDAR_ID\" \\\n    \"Spring Concert\" \\\n    \"March 1, 2026\" \\\n    \"7:00 PM\" \\\n    \"10:00 PM\" \\\n    \"*** ACTION REQUIRED: GET TICKETS BY FEB 15 ***\n\nEvent Link: https:\u002F\u002Fexample.com\u002Ftickets\n\nSpring Concert at Downtown Theater\nDoors open at 7 PM\" \\\n    \"$ATTENDEE_EMAILS\" \\\n    \"\" \\\n    \"$EMAIL_ID\"\n```\n\n**2. Deadline Reminder Event** (separate event on the deadline date):\n```bash\n# Use create_event.sh for deadline reminders too (ensures tracking)\n\"$SCRIPTS_DIR\u002Fcreate_event.sh\" \\\n    \"$CALENDAR_ID\" \\\n    \"DEADLINE: Get tickets for Spring Concert\" \\\n    \"2026-02-15\" \\\n    \"09:00\" \\\n    \"09:30\" \\\n    \"Action required: Get tickets\n\nEvent Link: https:\u002F\u002Fexample.com\u002Ftickets\n\nMain event: Spring Concert on March 1, 2026\" \\\n    \"\" \\\n    \"\" \\\n    \"$EMAIL_ID\"\n```\n\n**Deadline Event Properties:**\n- **Title format**: `DEADLINE: [Action] for [Event Name]`\n- **Date**: The deadline date\n- **Time**: 9:00 AM (30 minute duration)\n- **Reminders**: Email 1 day before + popup 1 hour before\n- **Description**: Action required, URL, reference to main event\n\n### Email Notifications for Deadlines\n\nWhen creating events with deadlines, send a notification email to alert the user:\n\n```bash\n# Load config\nCONFIG_FILE=\"$HOME\u002F.config\u002Femail-to-calendar\u002Fconfig.json\"\nUSER_EMAIL=$(jq -r '.deadline_notifications.email_recipient \u002F\u002F .gmail_account' \"$CONFIG_FILE\")\nNOTIFICATIONS_ENABLED=$(jq -r '.deadline_notifications.enabled \u002F\u002F false' \"$CONFIG_FILE\")\n\n# Send notification if enabled (using wrapper script)\nif [ \"$NOTIFICATIONS_ENABLED\" = \"true\" ]; then\n    \"$SCRIPTS_DIR\u002Femail_send.sh\" \\\n        --to \"$USER_EMAIL\" \\\n        --subject \"ACTION REQUIRED: Get tickets for Spring Concert by Feb 15\" \\\n        --body \"A calendar event has been created that requires your action.\n\nEvent: Spring Concert\nDate: March 1, 2026\nDeadline: February 15, 2026\nAction Required: Get tickets\n\nLink: https:\u002F\u002Fexample.com\u002Ftickets\n\nCalendar events created:\n- Main event: Spring Concert (March 1)\n- Deadline reminder: DEADLINE: Get tickets for Spring Concert (Feb 15)\n\n---\nThis notification was sent by the email-to-calendar skill.\"\nfi\n```\n\n**When to send notifications:**\n- Only when `deadline_notifications.enabled` is `true` in config\n- Only for events that have action-required deadlines\n- Include the deadline date, action, URL, and event details\n\n## Activity Log\n\n```bash\n# Start session\n\"$SCRIPTS_DIR\u002Factivity_log.sh\" start-session\n\n# Log skipped emails\n\"$SCRIPTS_DIR\u002Factivity_log.sh\" log-skip --email-id \"abc\" --subject \"Newsletter\" --reason \"No events\"\n\n# Log events\n\"$SCRIPTS_DIR\u002Factivity_log.sh\" log-event --email-id \"def\" --title \"Meeting\" --action created\n\n# End session\n\"$SCRIPTS_DIR\u002Factivity_log.sh\" end-session\n\n# Show recent activity\n\"$SCRIPTS_DIR\u002Factivity_log.sh\" show --last 3\n```\n\n## Changelog and Undo\n\nChanges can be undone within 24 hours:\n\n```bash\n# List recent changes\n\"$SCRIPTS_DIR\u002Fchangelog.sh\" list --last 10\n\n# List undoable changes\n\"$SCRIPTS_DIR\u002Fundo.sh\" list\n\n# Undo most recent change\n\"$SCRIPTS_DIR\u002Fundo.sh\" last\n\n# Undo specific change\n\"$SCRIPTS_DIR\u002Fundo.sh\" --change-id \"chg_20260202_143000_001\"\n```\n\n## Pending Invites\n\nEvents not immediately actioned are tracked for reminders:\n\n```bash\n# Add pending invites (after presenting events to user)\n\"$SCRIPTS_DIR\u002Fadd_pending.sh\" \\\n    --email-id \"$EMAIL_ID\" \\\n    --email-subject \"Party Invite\" \\\n    --events-json '[{\"title\":\"Birthday Party\",\"date\":\"2026-02-15\",\"time\":\"14:00\",\"status\":\"pending\"}]'\n\n# List pending invites (JSON)\n\"$SCRIPTS_DIR\u002Flist_pending.sh\"\n\n# Human-readable summary\n\"$SCRIPTS_DIR\u002Flist_pending.sh\" --summary\n\n# Update reminder tracking\n\"$SCRIPTS_DIR\u002Flist_pending.sh\" --summary --update-reminded\n\n# Auto-dismiss after 3 ignored reminders\n\"$SCRIPTS_DIR\u002Flist_pending.sh\" --summary --auto-dismiss\n```\n\n## Event Tracking\n\n```bash\n# Look up by email ID\n\"$SCRIPTS_DIR\u002Flookup_event.sh\" --email-id \"19c1c86dcc389443\"\n\n# Look up by summary\n\"$SCRIPTS_DIR\u002Flookup_event.sh\" --summary \"Staff Development\"\n\n# List all tracked events\n\"$SCRIPTS_DIR\u002Flookup_event.sh\" --list\n\n# Validate events exist (removes orphans)\n\"$SCRIPTS_DIR\u002Flookup_event.sh\" --email-id \"abc\" --validate\n```\n\n## File Locations\n\n| File | Purpose |\n|------|---------|\n| `~\u002F.config\u002Femail-to-calendar\u002Fconfig.json` | User configuration |\n| `~\u002F.openclaw\u002Fworkspace\u002Fmemory\u002Femail-extractions\u002F` | Extracted data |\n| `~\u002F.openclaw\u002Fworkspace\u002Fmemory\u002Femail-extractions\u002Findex.json` | Processing index |\n| `~\u002F.openclaw\u002Fworkspace\u002Fmemory\u002Femail-to-calendar\u002Fevents.json` | Event tracking |\n| `~\u002F.openclaw\u002Fworkspace\u002Fmemory\u002Femail-to-calendar\u002Fpending_invites.json` | Pending invites |\n| `~\u002F.openclaw\u002Fworkspace\u002Fmemory\u002Femail-to-calendar\u002Factivity.json` | Activity log |\n| `~\u002F.openclaw\u002Fworkspace\u002Fmemory\u002Femail-to-calendar\u002Fchangelog.json` | Change history |\n| `~\u002F.openclaw\u002Fworkspace\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002F` | Utility scripts |\n| `~\u002F.openclaw\u002Fworkspace\u002Fskills\u002Femail-to-calendar\u002FMEMORY.md` | User preferences |\n\n## References\n\n- **Setup Guide**: [SETUP.md](SETUP.md) - Configuration and onboarding\n- **CLI Reference**: [references\u002Fgog-commands.md](references\u002Fgog-commands.md) - Detailed gog CLI usage\n- **Extraction Patterns**: [references\u002Fextraction-patterns.md](references\u002Fextraction-patterns.md) - Date\u002Ftime parsing\n- **Workflow Example**: [references\u002Fworkflow-example.md](references\u002Fworkflow-example.md) - Complete example\n\n## Notes\n\n### Date Parsing\nHandles common formats:\n- January 15, 2026, Wednesday January 15\n- 01\u002F15\u002F2026, 15\u002F01\u002F2026\n- Date ranges like \"Feb 2-6\"\n\n### Time Zones\nAll times assumed local timezone. Time zone info preserved in descriptions.\n","> **CRITICAL RULES - READ BEFORE PROCESSING ANY EMAIL**\n>\n> 1. **NEVER CALL `gog` DIRECTLY** - ALWAYS use wrapper scripts (`create_event.sh`, `email_read.sh`, etc.). Direct `gog` calls bypass tracking and cause duplicates. THIS IS NON-NEGOTIABLE.\n> 2. **IGNORE CALENDAR NOTIFICATIONS** - DO NOT process emails from `calendar-notification@google.com` (Accepted:, Declined:, Tentative:, etc.). These are responses to existing invites, NOT new events. Run `process_calendar_replies.sh` to archive them.\n> 3. **ALWAYS ASK BEFORE CREATING** - Never create calendar events without explicit user confirmation in the current conversation\n> 4. **CHECK IF ALREADY PROCESSED** - Before processing any email, check `processed_emails` in index.json\n> 5. **READ CONFIG FIRST** - Load and apply `ignore_patterns` and `auto_create_patterns` before presenting events\n> 6. **READ MEMORY.MD** - Check for user preferences stored from previous sessions\n> 7. **INCLUDE ALL CONFIGURED ATTENDEES** - When creating\u002Fupdating\u002Fdeleting events, always include attendees from config with `--attendees` flag (and `--send-updates all` if supported)\n> 8. **CHECK TRACKED EVENTS FIRST** - Use `lookup_event.sh --email-id` to find existing events before calendar search (faster, more reliable)\n> 9. **TRACK ALL CREATED EVENTS** - The `create_event.sh` script automatically tracks events; use tracked IDs for updates\u002Fdeletions\n> 10. **SHOW DAY-OF-WEEK** - Always include the day of week when presenting events for user verification\n\n> ⛔ **FORBIDDEN: DO NOT USE `gog` COMMANDS DIRECTLY** ⛔\n>\n> **WRONG:** `gog calendar create ...` or `gog gmail ...`\n> **RIGHT:** `\"$SCRIPTS_DIR\u002Fcreate_event.sh\" ...` or `\"$SCRIPTS_DIR\u002Femail_read.sh\" ...`\n>\n> Direct CLI calls bypass event tracking, break duplicate detection, and cause duplicate events.\n> ALL operations MUST go through the wrapper scripts in `scripts\u002F`.\n\n# Email to Calendar Skill\n\nExtract calendar events and action items from emails, present them for review, and create\u002Fupdate calendar events with duplicate detection and undo support.\n\n**First-time setup:** See [SETUP.md](SETUP.md) for configuration options and smart onboarding.\n\n## Reading Email Content\n\n**IMPORTANT:** Before you can extract events, you must read the email body. Use the wrapper scripts.\n\n```bash\nSCRIPTS_DIR=\"$HOME\u002F.openclaw\u002Fworkspace\u002Fskills\u002Femail-to-calendar\u002Fscripts\"\n\n# Get a single email by ID (PREFERRED)\n\"$SCRIPTS_DIR\u002Femail_read.sh\" --email-id \"\u003CmessageId>\"\n\n# Search with body content included\n\"$SCRIPTS_DIR\u002Femail_search.sh\" --query \"in:inbox is:unread\" --max 20 --include-body\n```\n\n**Note on stale forwards:** Don't use `newer_than:1d` because it checks the email's original date header, not when it was received. Process all UNREAD emails and rely on the \"already processed\" check.\n\n## Workflow\n\n### 0. Pre-Processing Checks (MANDATORY)\n\n```bash\nSCRIPTS_DIR=\"$HOME\u002F.openclaw\u002Fworkspace\u002Fskills\u002Femail-to-calendar\u002Fscripts\"\nCONFIG_FILE=\"$HOME\u002F.config\u002Femail-to-calendar\u002Fconfig.json\"\nINDEX_FILE=\"$HOME\u002F.openclaw\u002Fworkspace\u002Fmemory\u002Femail-extractions\u002Findex.json\"\n\n# Start activity logging\n\"$SCRIPTS_DIR\u002Factivity_log.sh\" start-session\n\n# Check email mode\nEMAIL_MODE=$(jq -r '.email_mode \u002F\u002F \"forwarded\"' \"$CONFIG_FILE\")\n\n# Check if email was already processed\nEMAIL_ID=\"\u003Cthe email message ID>\"\nif jq -e \".extractions[] | select(.email_id == \\\"$EMAIL_ID\\\")\" \"$INDEX_FILE\" > \u002Fdev\u002Fnull 2>&1; then\n    \"$SCRIPTS_DIR\u002Factivity_log.sh\" log-skip --email-id \"$EMAIL_ID\" --subject \"Subject\" --reason \"Already processed\"\n    exit 0\nfi\n\n# Load ignore\u002Fauto-create patterns\nIGNORE_PATTERNS=$(jq -r '.event_rules.ignore_patterns[]' \"$CONFIG_FILE\")\nAUTO_CREATE_PATTERNS=$(jq -r '.event_rules.auto_create_patterns[]' \"$CONFIG_FILE\")\n```\n\n### 1. Find Emails to Process\n\n**DIRECT mode:** Scan all unread emails for event indicators (dates, times, meeting keywords).\n\n**FORWARDED mode:** Only process emails with forwarded indicators (Fwd:, forwarded message headers).\n\n### 2. Extract Events (Agent does this directly)\n\nRead the email and extract events as structured data. Include for each event:\n- **title**: Descriptive name (max 80 chars)\n- **date**: Event date(s)\n- **day_of_week**: For verification\n- **time**: Start\u002Fend times (default: 9 AM - 5 PM)\n- **is_multi_day**: Whether it spans multiple days\n- **is_recurring**: Whether it repeats (and pattern)\n- **confidence**: high\u002Fmedium\u002Flow\n- **urls**: Any URLs found in the email (REQUIRED - always look for registration links, info pages, ticketing sites, etc.)\n- **deadline_date**: RSVP\u002Fregistration\u002Fticket deadline date (if found)\n- **deadline_action**: What user needs to do (e.g., \"RSVP\", \"get tickets\", \"register\")\n- **deadline_url**: Direct link for taking action (often same as event URL)\n\n**URL Extraction Rule:** ALWAYS scan the email for URLs and include the most relevant one at the BEGINNING of the event description.\n\n### 2.1 Deadline Detection\n\nScan the email for deadline patterns that indicate action is required before the event:\n\n**Common Deadline Patterns:**\n- \"RSVP by [date]\", \"Please RSVP by [date]\"\n- \"Register by [date]\", \"Registration closes [date]\"\n- \"Tickets available until [date]\", \"Get tickets by [date]\"\n- \"Early bird ends [date]\", \"Early registration deadline [date]\"\n- \"Must respond by [date]\", \"Respond by [date]\"\n- \"Sign up by [date]\", \"Sign up deadline [date]\"\n- \"Deadline: [date]\", \"Due by [date]\"\n- \"Last day to [action]: [date]\"\n\nWhen a deadline is found:\n1. Extract the deadline date\n2. Determine the required action (RSVP, register, buy tickets, etc.)\n3. Find the URL for taking that action\n4. Flag the event for special handling (see sections below)\n\n### 3. Present Items to User and WAIT\n\nApply event rules, then present with numbered selection:\n\n```\nI found the following potential events:\n\n1. ~~ELAC Meeting (Feb 2, Monday at 8:15 AM)~~ - SKIP (matches ignore pattern)\n2. **Team Offsite (Feb 2-6, Sun-Thu)** - PENDING\n3. **Staff Development Day (Feb 12, Wednesday)** - AUTO-CREATE\n\nReply with numbers to create (e.g., '2, 3'), 'all', or 'none'.\n```\n\n**STOP AND WAIT for user response.**\n\nAfter presenting, record pending invites for follow-up reminders:\n```bash\n# Record pending invites using add_pending.sh\n\"$SCRIPTS_DIR\u002Fadd_pending.sh\" \\\n    --email-id \"$EMAIL_ID\" \\\n    --email-subject \"$EMAIL_SUBJECT\" \\\n    --events-json '[{\"title\":\"Event Name\",\"date\":\"2026-02-15\",\"time\":\"14:00\",\"status\":\"pending\"}]'\n```\n\n### 4. Check for Duplicates (MANDATORY)\n\n**ALWAYS check before creating any event:**\n\n```bash\n# Step 1: Check local tracking first (fast)\nTRACKED=$(\"$SCRIPTS_DIR\u002Flookup_event.sh\" --email-id \"$EMAIL_ID\")\nif [ \"$(echo \"$TRACKED\" | jq 'length')\" -gt 0 ]; then\n    EXISTING_EVENT_ID=$(echo \"$TRACKED\" | jq -r '.[0].event_id')\nfi\n\n# Step 2: If not found, try summary match\nif [ -z \"$EXISTING_EVENT_ID\" ]; then\n    TRACKED=$(\"$SCRIPTS_DIR\u002Flookup_event.sh\" --summary \"$EVENT_TITLE\")\nfi\n\n# Step 3: Fall back to calendar search using wrapper script\nif [ -z \"$EXISTING_EVENT_ID\" ]; then\n    \"$SCRIPTS_DIR\u002Fcalendar_search.sh\" --calendar-id \"$CALENDAR_ID\" --from \"${EVENT_DATE}T00:00:00\" --to \"${EVENT_DATE}T23:59:59\"\nfi\n```\n\nUse LLM semantic matching for fuzzy duplicates (e.g., \"Team Offsite\" vs \"Team Offsite 5-6pm\").\n\n### 5. Create or Update Calendar Events\n\n**Use create_event.sh (recommended)** - handles date parsing, tracking, and changelog:\n\n```bash\n# Create new event\n\"$SCRIPTS_DIR\u002Fcreate_event.sh\" \\\n    \"$CALENDAR_ID\" \\\n    \"Event Title\" \\\n    \"February 11, 2026\" \\\n    \"9:00 AM\" \\\n    \"5:00 PM\" \\\n    \"Description\" \\\n    \"$ATTENDEE_EMAILS\" \\\n    \"\" \\\n    \"$EMAIL_ID\"\n\n# Update existing event (pass event_id as 8th parameter)\n\"$SCRIPTS_DIR\u002Fcreate_event.sh\" \\\n    \"$CALENDAR_ID\" \\\n    \"Updated Title\" \\\n    \"February 11, 2026\" \\\n    \"10:00 AM\" \\\n    \"6:00 PM\" \\\n    \"Updated description\" \\\n    \"$ATTENDEE_EMAILS\" \\\n    \"$EXISTING_EVENT_ID\" \\\n    \"$EMAIL_ID\"\n```\n\nFor direct gog commands and advanced options, see [references\u002Fgog-commands.md](references\u002Fgog-commands.md).\n\n### 6. Email Disposition (Automatic)\n\nEmail disposition (mark as read and\u002For archive) is handled **automatically** by `create_event.sh` based on config settings. No manual step needed - emails are dispositioned after event creation.\n\nTo manually disposition an email:\n```bash\n\"$SCRIPTS_DIR\u002Fdisposition_email.sh\" --email-id \"$EMAIL_ID\"\n```\n\nTo process calendar reply emails (accepts, declines, tentatives):\n```bash\n\"$SCRIPTS_DIR\u002Fprocess_calendar_replies.sh\"           # Process all\n\"$SCRIPTS_DIR\u002Fprocess_calendar_replies.sh\" --dry-run # Preview only\n```\n\n```bash\n# End activity session\n\"$SCRIPTS_DIR\u002Factivity_log.sh\" end-session\n```\n\n## Event Creation Rules\n\n### Date\u002FTime Handling\n- **Single-day events**: Default 9:00 AM - 5:00 PM\n- **Multi-day events** (e.g., Feb 2-6): Use `--rrule \"RRULE:FREQ=DAILY;COUNT=N\"`\n- **Events with specific times**: Use exact time from email\n\n### Event Descriptions\n\n**Format event descriptions in this order:**\n\n1. **ACTION WARNING** (if deadline exists):\n   ```\n   *** ACTION REQUIRED: [ACTION] BY [DATE] ***\n   ```\n\n2. **Event Link** (if URL found):\n   ```\n   Event Link: [URL]\n   ```\n\n3. **Event Details**: Information extracted from the email\n\n**Example WITH deadline:**\n```\n*** ACTION REQUIRED: GET TICKETS BY FEB 15 ***\n\nEvent Link: https:\u002F\u002Fexample.com\u002Ftickets\n\nSpring Concert at Downtown Theater\nDoors open at 7 PM\nVIP meet & greet available\n```\n\n**Example WITHOUT deadline:**\n```\nEvent Link: https:\u002F\u002Fexample.com\u002Fevent\n\nSpring Concert at Downtown Theater\nDoors open at 7 PM\n```\n\n### Duplicate Detection\nConsider it a duplicate if:\n- Same date AND similar title (semantic matching) AND overlapping time\n\nAlways update existing events rather than creating duplicates.\n\n### Creating Deadline Events\n\nWhen an event has a deadline (RSVP, registration, ticket purchase, etc.), create TWO calendar events:\n\n**1. Main Event** (as normal, but with warning in description):\n```bash\n\"$SCRIPTS_DIR\u002Fcreate_event.sh\" \\\n    \"$CALENDAR_ID\" \\\n    \"Spring Concert\" \\\n    \"March 1, 2026\" \\\n    \"7:00 PM\" \\\n    \"10:00 PM\" \\\n    \"*** ACTION REQUIRED: GET TICKETS BY FEB 15 ***\n\nEvent Link: https:\u002F\u002Fexample.com\u002Ftickets\n\nSpring Concert at Downtown Theater\nDoors open at 7 PM\" \\\n    \"$ATTENDEE_EMAILS\" \\\n    \"\" \\\n    \"$EMAIL_ID\"\n```\n\n**2. Deadline Reminder Event** (separate event on the deadline date):\n```bash\n# Use create_event.sh for deadline reminders too (ensures tracking)\n\"$SCRIPTS_DIR\u002Fcreate_event.sh\" \\\n    \"$CALENDAR_ID\" \\\n    \"DEADLINE: Get tickets for Spring Concert\" \\\n    \"2026-02-15\" \\\n    \"09:00\" \\\n    \"09:30\" \\\n    \"Action required: Get tickets\n\nEvent Link: https:\u002F\u002Fexample.com\u002Ftickets\n\nMain event: Spring Concert on March 1, 2026\" \\\n    \"\" \\\n    \"\" \\\n    \"$EMAIL_ID\"\n```\n\n**Deadline Event Properties:**\n- **Title format**: `DEADLINE: [Action] for [Event Name]`\n- **Date**: The deadline date\n- **Time**: 9:00 AM (30 minute duration)\n- **Reminders**: Email 1 day before + popup 1 hour before\n- **Description**: Action required, URL, reference to main event\n\n### Email Notifications for Deadlines\n\nWhen creating events with deadlines, send a notification email to alert the user:\n\n```bash\n# Load config\nCONFIG_FILE=\"$HOME\u002F.config\u002Femail-to-calendar\u002Fconfig.json\"\nUSER_EMAIL=$(jq -r '.deadline_notifications.email_recipient \u002F\u002F .gmail_account' \"$CONFIG_FILE\")\nNOTIFICATIONS_ENABLED=$(jq -r '.deadline_notifications.enabled \u002F\u002F false' \"$CONFIG_FILE\")\n\n# Send notification if enabled (using wrapper script)\nif [ \"$NOTIFICATIONS_ENABLED\" = \"true\" ]; then\n    \"$SCRIPTS_DIR\u002Femail_send.sh\" \\\n        --to \"$USER_EMAIL\" \\\n        --subject \"ACTION REQUIRED: Get tickets for Spring Concert by Feb 15\" \\\n        --body \"A calendar event has been created that requires your action.\n\nEvent: Spring Concert\nDate: March 1, 2026\nDeadline: February 15, 2026\nAction Required: Get tickets\n\nLink: https:\u002F\u002Fexample.com\u002Ftickets\n\nCalendar events created:\n- Main event: Spring Concert (March 1)\n- Deadline reminder: DEADLINE: Get tickets for Spring Concert (Feb 15)\n\n---\nThis notification was sent by the email-to-calendar skill.\"\nfi\n```\n\n**When to send notifications:**\n- Only when `deadline_notifications.enabled` is `true` in config\n- Only for events that have action-required deadlines\n- Include the deadline date, action, URL, and event details\n\n## Activity Log\n\n```bash\n# Start session\n\"$SCRIPTS_DIR\u002Factivity_log.sh\" start-session\n\n# Log skipped emails\n\"$SCRIPTS_DIR\u002Factivity_log.sh\" log-skip --email-id \"abc\" --subject \"Newsletter\" --reason \"No events\"\n\n# Log events\n\"$SCRIPTS_DIR\u002Factivity_log.sh\" log-event --email-id \"def\" --title \"Meeting\" --action created\n\n# End session\n\"$SCRIPTS_DIR\u002Factivity_log.sh\" end-session\n\n# Show recent activity\n\"$SCRIPTS_DIR\u002Factivity_log.sh\" show --last 3\n```\n\n## Changelog and Undo\n\nChanges can be undone within 24 hours:\n\n```bash\n# List recent changes\n\"$SCRIPTS_DIR\u002Fchangelog.sh\" list --last 10\n\n# List undoable changes\n\"$SCRIPTS_DIR\u002Fundo.sh\" list\n\n# Undo most recent change\n\"$SCRIPTS_DIR\u002Fundo.sh\" last\n\n# Undo specific change\n\"$SCRIPTS_DIR\u002Fundo.sh\" --change-id \"chg_20260202_143000_001\"\n```\n\n## Pending Invites\n\nEvents not immediately actioned are tracked for reminders:\n\n```bash\n# Add pending invites (after presenting events to user)\n\"$SCRIPTS_DIR\u002Fadd_pending.sh\" \\\n    --email-id \"$EMAIL_ID\" \\\n    --email-subject \"Party Invite\" \\\n    --events-json '[{\"title\":\"Birthday Party\",\"date\":\"2026-02-15\",\"time\":\"14:00\",\"status\":\"pending\"}]'\n\n# List pending invites (JSON)\n\"$SCRIPTS_DIR\u002Flist_pending.sh\"\n\n# Human-readable summary\n\"$SCRIPTS_DIR\u002Flist_pending.sh\" --summary\n\n# Update reminder tracking\n\"$SCRIPTS_DIR\u002Flist_pending.sh\" --summary --update-reminded\n\n# Auto-dismiss after 3 ignored reminders\n\"$SCRIPTS_DIR\u002Flist_pending.sh\" --summary --auto-dismiss\n```\n\n## Event Tracking\n\n```bash\n# Look up by email ID\n\"$SCRIPTS_DIR\u002Flookup_event.sh\" --email-id \"19c1c86dcc389443\"\n\n# Look up by summary\n\"$SCRIPTS_DIR\u002Flookup_event.sh\" --summary \"Staff Development\"\n\n# List all tracked events\n\"$SCRIPTS_DIR\u002Flookup_event.sh\" --list\n\n# Validate events exist (removes orphans)\n\"$SCRIPTS_DIR\u002Flookup_event.sh\" --email-id \"abc\" --validate\n```\n\n## File Locations\n\n| File | Purpose |\n|------|---------|\n| `~\u002F.config\u002Femail-to-calendar\u002Fconfig.json` | User configuration |\n| `~\u002F.openclaw\u002Fworkspace\u002Fmemory\u002Femail-extractions\u002F` | Extracted data |\n| `~\u002F.openclaw\u002Fworkspace\u002Fmemory\u002Femail-extractions\u002Findex.json` | Processing index |\n| `~\u002F.openclaw\u002Fworkspace\u002Fmemory\u002Femail-to-calendar\u002Fevents.json` | Event tracking |\n| `~\u002F.openclaw\u002Fworkspace\u002Fmemory\u002Femail-to-calendar\u002Fpending_invites.json` | Pending invites |\n| `~\u002F.openclaw\u002Fworkspace\u002Fmemory\u002Femail-to-calendar\u002Factivity.json` | Activity log |\n| `~\u002F.openclaw\u002Fworkspace\u002Fmemory\u002Femail-to-calendar\u002Fchangelog.json` | Change history |\n| `~\u002F.openclaw\u002Fworkspace\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002F` | Utility scripts |\n| `~\u002F.openclaw\u002Fworkspace\u002Fskills\u002Femail-to-calendar\u002FMEMORY.md` | User preferences |\n\n## References\n\n- **Setup Guide**: [SETUP.md](SETUP.md) - Configuration and onboarding\n- **CLI Reference**: [references\u002Fgog-commands.md](references\u002Fgog-commands.md) - Detailed gog CLI usage\n- **Extraction Patterns**: [references\u002Fextraction-patterns.md](references\u002Fextraction-patterns.md) - Date\u002Ftime parsing\n- **Workflow Example**: [references\u002Fworkflow-example.md](references\u002Fworkflow-example.md) - Complete example\n\n## Notes\n\n### Date Parsing\nHandles common formats:\n- January 15, 2026, Wednesday January 15\n- 01\u002F15\u002F2026, 15\u002F01\u002F2026\n- Date ranges like \"Feb 2-6\"\n\n### Time Zones\nAll times assumed local timezone. Time zone info preserved in descriptions.\n",{"name":5,"version":23,"description":7},"1.13.1","main","3641543f81ae80504027d6b012e0dadce4e2de40","skills\u002Femail-to-calendar","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills","https:\u002F\u002Fgithub.com\u002FSillyHippy","2026-09-18 11:42:22",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add SillyHippy\u002Fzo-skills --skill email-to-calendar",{"tool":36,"command":37},"bunx","bunx skills add SillyHippy\u002Fzo-skills --skill email-to-calendar",{"tool":39,"command":40},"pnpm","pnpm dlx skills add SillyHippy\u002Fzo-skills --skill email-to-calendar","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002FSKILL.md",true,[44,50,54,58,62,66,70,74,78,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156,160,164,168,172,176,180,184,188,192,196,200,204,208,211,215,219,223,227,231,235,239,243,247,251,255,259],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"_meta.json","REFERENCE","参考文档",137,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002F_meta.json",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"BOOT.md",4591,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002FBOOT.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"CHANGELOG.md",15801,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002FCHANGELOG.md",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"CONTRIBUTING.md",2212,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002FCONTRIBUTING.md",{"path":63,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":64,"sourceHtmlUrl":65},"package.json",701,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fpackage.json",{"path":67,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fextraction-patterns.md",4129,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Freferences\u002Fextraction-patterns.md",{"path":71,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fgog-commands.md",6133,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Freferences\u002Fgog-commands.md",{"path":75,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fworkflow-example.md",4983,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Freferences\u002Fworkflow-example.md",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"scripts\u002Factivity_log.sh","SCRIPT","脚本",2660,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Factivity_log.sh",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fadd_pending.sh",1679,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Fadd_pending.sh",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fcalendar_delete.sh",1016,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Fcalendar_delete.sh",{"path":93,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Fcalendar_search.sh",1261,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Fcalendar_search.sh",{"path":97,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fchangelog.sh",3618,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Fchangelog.sh",{"path":101,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fcheck_duplicate.sh",3099,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Fcheck_duplicate.sh",{"path":105,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":106,"sourceHtmlUrl":107},"scripts\u002Fcreate_event.sh",7253,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Fcreate_event.sh",{"path":109,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":110,"sourceHtmlUrl":111},"scripts\u002Fdelete_tracked_event.sh",871,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Fdelete_tracked_event.sh",{"path":113,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":114,"sourceHtmlUrl":115},"scripts\u002Fdisposition_email.sh",1950,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Fdisposition_email.sh",{"path":117,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002Femail_modify.sh",1368,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Femail_modify.sh",{"path":121,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":122,"sourceHtmlUrl":123},"scripts\u002Femail_read.sh",777,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Femail_read.sh",{"path":125,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":126,"sourceHtmlUrl":127},"scripts\u002Femail_search.sh",1146,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Femail_search.sh",{"path":129,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":130,"sourceHtmlUrl":131},"scripts\u002Femail_send.sh",1026,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Femail_send.sh",{"path":133,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":134,"sourceHtmlUrl":135},"scripts\u002Flist_pending.sh",1175,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Flist_pending.sh",{"path":137,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":138,"sourceHtmlUrl":139},"scripts\u002Flookup_event.sh",1721,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Flookup_event.sh",{"path":141,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":142,"sourceHtmlUrl":143},"scripts\u002Fprocess_calendar_replies.sh",4462,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Fprocess_calendar_replies.sh",{"path":145,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":146,"sourceHtmlUrl":147},"scripts\u002Frun_tests.sh",618,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Frun_tests.sh",{"path":149,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":150,"sourceHtmlUrl":151},"scripts\u002Ftests\u002F__init__.py",34,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Ftests\u002F__init__.py",{"path":153,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":154,"sourceHtmlUrl":155},"scripts\u002Ftests\u002Ftest_activity_ops.py",12755,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Ftests\u002Ftest_activity_ops.py",{"path":157,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":158,"sourceHtmlUrl":159},"scripts\u002Ftests\u002Ftest_changelog_ops.py",13124,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Ftests\u002Ftest_changelog_ops.py",{"path":161,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":162,"sourceHtmlUrl":163},"scripts\u002Ftests\u002Ftest_common.py",5994,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Ftests\u002Ftest_common.py",{"path":165,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":166,"sourceHtmlUrl":167},"scripts\u002Ftests\u002Ftest_date_parser.py",4497,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Ftests\u002Ftest_date_parser.py",{"path":169,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":170,"sourceHtmlUrl":171},"scripts\u002Ftests\u002Ftest_disposition_ops.py",9406,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Ftests\u002Ftest_disposition_ops.py",{"path":173,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":174,"sourceHtmlUrl":175},"scripts\u002Ftests\u002Ftest_event_tracking.py",9727,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Ftests\u002Ftest_event_tracking.py",{"path":177,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":178,"sourceHtmlUrl":179},"scripts\u002Ftests\u002Ftest_invite_ops.py",7297,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Ftests\u002Ftest_invite_ops.py",{"path":181,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":182,"sourceHtmlUrl":183},"scripts\u002Ftests\u002Ftest_json_store.py",6746,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Ftests\u002Ftest_json_store.py",{"path":185,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":186,"sourceHtmlUrl":187},"scripts\u002Ftests\u002Ftest_pending_ops.py",14952,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Ftests\u002Ftest_pending_ops.py",{"path":189,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":190,"sourceHtmlUrl":191},"scripts\u002Ftests\u002Ftest_undo_ops.py",9233,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Ftests\u002Ftest_undo_ops.py",{"path":193,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":194,"sourceHtmlUrl":195},"scripts\u002Ftrack_event.sh",1402,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Ftrack_event.sh",{"path":197,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":198,"sourceHtmlUrl":199},"scripts\u002Fundo.sh",6658,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Fundo.sh",{"path":201,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":202,"sourceHtmlUrl":203},"scripts\u002Fupdate_invite_status.sh",2329,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Fupdate_invite_status.sh",{"path":205,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":206,"sourceHtmlUrl":207},"scripts\u002Fupdate_tracked_event.sh",1000,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Fupdate_tracked_event.sh",{"path":209,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":150,"sourceHtmlUrl":210},"scripts\u002Futils\u002F__init__.py","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Futils\u002F__init__.py",{"path":212,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":213,"sourceHtmlUrl":214},"scripts\u002Futils\u002Factivity_ops.py",6372,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Futils\u002Factivity_ops.py",{"path":216,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":217,"sourceHtmlUrl":218},"scripts\u002Futils\u002Fcalendar_ops.py",10791,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Futils\u002Fcalendar_ops.py",{"path":220,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":221,"sourceHtmlUrl":222},"scripts\u002Futils\u002Fchangelog_ops.py",9023,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Futils\u002Fchangelog_ops.py",{"path":224,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":225,"sourceHtmlUrl":226},"scripts\u002Futils\u002Fcommon.py",2384,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Futils\u002Fcommon.py",{"path":228,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":229,"sourceHtmlUrl":230},"scripts\u002Futils\u002Fdate_parser.py",2903,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Futils\u002Fdate_parser.py",{"path":232,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":233,"sourceHtmlUrl":234},"scripts\u002Futils\u002Fdisposition_ops.py",5661,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Futils\u002Fdisposition_ops.py",{"path":236,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":237,"sourceHtmlUrl":238},"scripts\u002Futils\u002Femail_ops.py",7799,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Futils\u002Femail_ops.py",{"path":240,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":241,"sourceHtmlUrl":242},"scripts\u002Futils\u002Fevent_tracking.py",7430,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Futils\u002Fevent_tracking.py",{"path":244,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":245,"sourceHtmlUrl":246},"scripts\u002Futils\u002Finvite_ops.py",3152,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Futils\u002Finvite_ops.py",{"path":248,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":249,"sourceHtmlUrl":250},"scripts\u002Futils\u002Fjson_store.py",1393,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Futils\u002Fjson_store.py",{"path":252,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":253,"sourceHtmlUrl":254},"scripts\u002Futils\u002Fpending_ops.py",9220,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Futils\u002Fpending_ops.py",{"path":256,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":257,"sourceHtmlUrl":258},"scripts\u002Futils\u002Fundo_ops.py",4277,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002Fscripts\u002Futils\u002Fundo_ops.py",{"path":260,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":261,"sourceHtmlUrl":262},"SETUP.md",8879,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Femail-to-calendar\u002FSETUP.md",[264,271,278,285,292,299],{"skillNo":265,"name":266,"nameZh":6,"description":267,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":268,"categories":269,"keywords":270,"publishedAt":18},"01M7C4RK2ZCHPKQT393RVSC6ER","zopack","Export and import zo.space route setups as shareable .zopack.md files. Use when the user wants to package their zo.space routes for sharing, or when they receive a .zopack.md file to deploy. Triggers on \"export my zo.space\", \"create a zopack\", \"import this zopack\", or any mention of .zopack.md files.","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzopack\u002FSKILL.md",[],[],{"skillNo":272,"name":273,"nameZh":6,"description":274,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":275,"categories":276,"keywords":277,"publishedAt":18},"01M7C4REH5EJ22X3C1SF88X6KQ","zoho-mail-inbox","Full inbox management for Zoho Mail (info@justlegalsolutions.org) — list unread, mark all as read, delete by sender\u002Fkeyword, search, send from aliases, list folders. Fully self-contained — zero setup needed.","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-mail-inbox\u002FSKILL.md",[],[],{"skillNo":279,"name":280,"nameZh":6,"description":281,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":282,"categories":283,"keywords":284,"publishedAt":18},"01M7C4RAJF1N9R8ZRT25GMHFBF","weekly-meeting-reminder","Get an email every Sunday evening listing your meetings for the coming week.","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzo-weekly-meeting-reminder\u002FSKILL.md",[],[],{"skillNo":286,"name":287,"nameZh":6,"description":288,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":289,"categories":290,"keywords":291,"publishedAt":18},"01M7C4R65Q9T6TPBRFQPWJSW4Z","twitter","Let Zo use your X (Twitter) account","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzo-twitter\u002FSKILL.md",[],[],{"skillNo":293,"name":294,"nameZh":6,"description":295,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":296,"categories":297,"keywords":298,"publishedAt":18},"01M7C4R358YM59EZRM3SW763VK","zo-tools","Internal process tools for Zo and Hermes — local search, document processing, OCR, and embeddings. All services run on localhost, zero HTTP slots consumed.","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzo-tools\u002FSKILL.md",[],[],{"skillNo":300,"name":301,"nameZh":6,"description":302,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":303,"categories":304,"keywords":305,"publishedAt":18},"01M7C4R0J4C3RQWKZ5W5W3CZ3X","ssh-setup","Sets up secure remote access to your Zo Computer so you can connect from anywhere","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzo-ssh-setup\u002FSKILL.md",[],[]]