Menu
Delete ONE calendar event by id
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Create a new contact (person or business) with ALL its channels and address in one call.
Fetch the full body and metadata of a single email by message_id.
Record a new bill / recurring expense
Create a new calendar event in Yorik's local calendar
Attach a postal address (home, work, billing, shipping) to an existing contact.
Attach a channel (email, phone, whatsapp, signal, sms, website, social) to a contact.
| name | delete_calendar_event |
| description | Delete ONE calendar event by id |
| when_to_use | - User cancels a meeting: "der Termin am Dienstag fällt aus" - User asks to clean up: "lösch den Test-Termin" Always call check_calendar first to get the event_id — never guess. IMPORTANT: this skill deletes exactly ONE event per call. If the user asks to delete multiple events, call this skill multiple times — once per event_id. Never combine. |
| inputs | {"event_id":{"type":"integer","required":true,"description":"The single event id to delete. NOT a list. NOT a wildcard. Exactly one positive integer."}} |
| outputs | {"deleted_event_id":{"type":"integer"},"event":{"type":"object","description":"The row that was deleted (so it can be quoted in the reply)."},"pending":{"type":"boolean","description":"True if user confirmation is required before the delete lands."}} |
| permissions | ["admin","member","restricted"] |
| tags | ["calendar","event","mutation","destructive"] |
Hard safety constraint: exactly one event per call. The backend rejects anything else (list, missing, zero, negative). This is deliberate — the LLM cannot mass-delete calendar entries even if it tries to.
Beta safety: when confirm_mutations=true, deletion is deferred until
the user confirms via the modal. The modal shows the full event so the
user can verify they're deleting the right one.
