DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to skip one Google Calendar event with Undo with Mojito

Ask in chat to remove a single recurring meeting from your Google Calendar.

Credentials. Calendar write access lets the agent delete events, so limit this to one occurrence and check the result before relying on it.

Who it is forA professional with a recurring meeting that is off this week and who wants it removed without editing the whole series.

The problemEditing a recurring series by hand is slow, and deleting the whole series removes meetings you still want.

The outcomeOnly the chosen occurrence is removed from Google Calendar, and you can undo the change in the app.

What you need first

  • A Mac or Mac mini where Claude Code runs, as the README describes
  • A server you control to host the hub (FastAPI and SQLite), with HTTPS and a few tokens
  • Access to the model provider you choose (the README says Anthropic today)
  • Comfort with self-hosting, per docs/SETUP.md

Steps

  1. Connect your Google Calendar to your self-hosted Mojito instance as the setup guide describes.
  2. In chat, name the recurring meeting and the single occurrence you want to skip.
  3. Check the change in your calendar.
  4. If the removal is wrong, use the Undo that the app shows for the change.

Prompt for your agent

In the TimeLovercc/mojito repo, remove only the occurrence of '<event-name>' on <date> from the connected Google Calendar. Expected output: confirmation that one occurrence was removed and the series is otherwise unchanged. Verify in Google Calendar that the other occurrences still exist.

Caveat. The README gives this as an example request, and calendar setup details are only in docs/SETUP.md, so confirm the connection works in your own instance first.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page