Email To Calendar

**Judgment:** A well-designed, feature-rich email-to-calendar skill with strong safety and duplicate-prevention mechanisms, suitable as a primary way to turn email content into structured calendar events in an OpenClaw environment. **Strengths & Capabilities** - Enforces use of wrapper scripts (`create_event.sh`, `email_read.sh`, etc.) instead of raw `gog` commands, which preserves tracking and significantly reduces duplicate-event risk. - Comprehensive workflow: unread/forwarded email discovery, content reading, structured event extraction (including day-of-week, recurrence flags, links, deadlines), user review, creation/update, and automatic email disposition. - Deadline-aware: detects RSVP/registration/ticket deadlines and automatically creates a paired deadline reminder event, with optional notification email if enabled in config. - Good operations tooling: activity logging, pending invites tracking, tracked events index, and 24-hour undo support via changelog/undo scripts. - Safety measures: explicit confirmation before event creation (unless explicitly configured for auto-create patterns), ignoring reply-only calendar notifications, and mandatory duplicate checks. **Key Risks / Limitations** - Extraction accuracy depends on LLM parsing quality and the diversity of email formats; unusual phrasing or highly unstructured emails may lead to missed or mis-specified events that still require user review. - Performance may degrade with very large inboxes or memory files, since the design relies heavily on file-based JSON (via `jq`) and can involve multiple script calls and searches per email. - Requires a correctly configured environment (gog CLI, `jq`, config files, script paths); misconfiguration or missing dependencies will impair functionality and may be non-obvious to less technical users. - Auto-create patterns, if misconfigured, could reduce the protection provided by the explicit confirmation rule and may create unwanted events. **Recommended Scenarios** - Users who regularly receive meeting invites, school calendars, or event announcements by email and want a structured, review-first pipeline into their calendar with strong duplicate protection. - Power users comfortable with simple configuration files who want to tune ignore/auto-create patterns, attendee defaults, and deadline notifications. - Workflows where traceability and reversibility matter: teams that need logs of what was created from which email, and the ability to undo changes if an extraction or creation decision was wrong. **Not Ideal For** - Extremely high-volume mailbox processing where strict performance SLAs are required and file-based JSON plus shell tooling could become a bottleneck. - Users unwilling to perform a brief review/confirmation step before event creation (the safety model assumes user verification).