More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Email to Calendar: Events from Your Inbox

    1

    Extract events and deadlines hiding in email into calendar entries — with confidence levels, dedup against your log and calendar, deadline reminders, and confirmation before creating.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Email to Calendar: Events from Your Inbox

    Email to Calendar: Events from Your Inbox

    Example session with this skill installed

    Today is Friday, October 23, 2026. Scan these four messages and show me what you'd put on my calendar. (1) "DataPipe Summit — March 4–5, 2027, Austin Convention Center. Early-bird registration ends November 15 — register on our site." (2) From my dentist's office: "Reminder: your cleaning is next Tuesday at 10:30 AM." (3) An automated "Accepted: Q4 Planning" notification from the calendar system. (4) A weekly industry newsletter whose footer mentions "our annual conference sometime next spring."

    • Read your context and instructions
    • Compiled the email to calendar

    Four messages processed through the pipeline. Tracking log checked first — none of these message IDs appear, so all four are new. Calendar notifications filtered before extraction: message 3 is an accept notice, a response to an existing event, archived separately and never extracted.

    Here's your confirmation list — nothing is created until you approve:

    1. DataPipe Summit (Mar 4–5, 2027, Thu–Fri), Austin Convention Center — high confidence — PENDING. Full date with year, organizer source, multi-day range captured as one event, not two.
    2. DEADLINE: Early-bird registration ends (Nov 15, 2026, Sun) — high confidence — PENDING. Found by the deadline pass. Approving item 1 with its deadline creates both: the summit event carrying an ACTION REQUIRED banner with the registration link, and this separate reminder on Nov 15.
    3. Dentist cleaning (Oct 27, 2026, Tue, 10:30 AM) — high confidence — PENDING. "Next Tuesday" resolved against today, Friday Oct 23: that's Oct 27, and the computed day of week confirms Tuesday. No end time given, so one hour is assumed and marked as assumed.
    4. Weekly industry newsletter — SKIP (no event intent). "Sometime next spring" is not a date; extracting it would manufacture a ghost event. If the conference dates get announced in a later issue, that message will extract cleanly.

    One conflict rule worth knowing: if a follow-up email moves the summit's venue, the existing event gets updated with the new details rather than duplicated — and if two emails ever disagree on a date, I present the conflict instead of averaging it. Reply with the numbers to create (e.g., "1, 2, 3") or tell me which to drop, and each created event will carry a back-reference to its source message so any of them can be undone by name.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Events hide in email: the conference announcement with an early-bird deadline, the appointment reminder in a thread, the "let's meet Thursday" that may or may not be real. The failure modes are just as familiar — duplicate events, ghost events created from newsletters, wrong dates, and things appearing on your calendar that nobody approved. This skill runs an eight-stage pipeline that prevents all of them: Collect → Extract → Filter → Deduplicate → Present → Confirm → Create → Track.

    Extraction is structured: title, dates resolved against an explicitly stated "today," a computed day of week for every date (the cheapest verification signal there is), times with assumed defaults clearly marked, locations and join links, and a dedicated deadline pass that scans for RSVP-by, register-by, early-bird-ends phrasing. A found deadline produces two entries — the event with an ACTION REQUIRED banner and its own DEADLINE reminder — because a deadline buried in a description is a deadline missed. Every candidate gets a confidence level from a five-signal rubric (date, time, title, source, corroboration), so ambiguity is labeled instead of hidden.

    Filtering kills newsletters and FYI noise before you ever see the list. Deduplication checks your tracking log first, then title-and-date matching, then calendar search — and updates the existing event when details evolve, instead of stacking versions. Then the pipeline stops: you get a numbered confirmation list and nothing is created until you approve it. Every creation is tracked (message ID → event ID) so rescans don't re-present decided items and undo actually works.

    Edge cases are handled in writing: the same event announced in three emails, a recurring series with one exception, invites you were only CC'd on, a passed deadline attached to a future event. And one rule has no exceptions: calendar notifications are responses, not events, and are never processed into new ones.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Productivity.

    The skill disciplines an agent that already has email and calendar access — it doesn't provide those connections itself. Extraction quality depends on the email: a date implied across a long thread ("same time as last week?") will be marked low confidence and presented as a question, not resolved by guessing. Handwritten or image-only invitations need OCR upstream. And the confirmation step is deliberate friction: if you want fully automatic creation with no review, this is the wrong tool by design — it will only auto-create narrow patterns you've approved in advance.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Permissions

    No special permissions declared or detected

    Listed24 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    Only for narrow, high-confidence patterns you explicitly approved beforehand — a flight itinerary from the airline is the canonical example. Everything else stops at the confirmation list, always. An auto-create rule that fires wrong is worse than no rule.

    Three checks in order: the tracking log (has this message already produced an event?), title-and-date matching, then a calendar search. Matches get updated with the newer details instead of duplicated — and an unmentioned field is never treated as a deleted one.

    The deadline gets its own DEADLINE reminder event on that date, and the main event carries an ACTION REQUIRED banner with the action and its link. Deadlines don't just live as a line in a description, because that's where they get missed.

    New in Productivity