← Search

Email: Calendar Events
Development 🧪 Install ran in our test sandbox · Nov 18, 2026 📌 Pinned version: commit f3656c6
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a Caffeine AI project (backend Motoko canister on…

Email: Calendar Events

Manage events and send iCalendar invitations by email

At a glance
What
Manage events and send iCalendar invitations by email
Cost
Free
Needs
a Caffeine AI project (backend Motoko canister on the Internet Computer); a Caffeine AI Plus or Pro subscription (required by the skill's frontmatter — caffeineai-subscription: [plus, pro]; there is no free tier for this skill); install the caffeinelabs-extension-email skill first, because caffeineai-email is a dependency of this package. The mops dependencies at this version are caffeineai-email-calendar-events ~0.4.0, caffeineai-email ~0.4.0 and caffeineai-authorization ~1.0.1. No API key of mine is pasted anywhere: the mail gateway settings (INTEGRATIONS_GATEWAY_URL / INTEGRATIONS_GATEWAY_API_KEY) are injected by the Caffeine platform on every deploy where the gateway is enabled — I do not supply them myself.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

C
Created by: Caffeine Labs
✓ Signed build — exact code hash-verified View the manifest

Quick answer

Email: Calendar Events is a free Muse skill listing, the calendar-events extension for Caffeine AI apps, but it requires a paid Caffeine AI Plus or Pro subscription, with no free tier. It offers full CRUD for events and meetings plus iCalendar invitation delivery by email, building and attaching the .ics file per attendee.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit f3656c6

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Caffeine AI project (backend Motoko canister on the Internet Computer); a Caffeine AI Plus or Pro subscription (required by the skill's frontmatter — caffeineai-subscription: [plus, pro]; there is no free tier for this skill); install the caffeinelabs-extension-email skill first, because caffeineai-email is a dependency of this package. The mops dependencies at this version are caffeineai-email-calendar-events ~0.4.0, caffeineai-email ~0.4.0 and caffeineai-authorization ~1.0.1. No API key of mine is pasted anywhere: the mail gateway settings (INTEGRATIONS_GATEWAY_URL / INTEGRATIONS_GATEWAY_API_KEY) are injected by the Caffeine platform on every deploy where the gateway is enabled — I do not supply them myself. Install "Email: Calendar Events" for me. It gives my agent caffeinelabs' skill (from the caffeinelabs/skills repository, Apache-2.0 licensed) for adding calendar events and meetings to a Caffeine AI app and sending iCalendar invitations by email: full CRUD over events (add, update, addAttendees, removeAttendees, cancel, delete, get, iter, reverse) through the prefabricated, unmodifiable Motoko module mo:caffeineai-email-calendar-events/calendarEvents.mo, with attendee roles (chair / required / optional / notParticipating), sequence numbers that bump on every change so attendees' calendars apply updates and cancellations, UUID generation for event ids, and sendCalendarEvent, which builds an iCalendar (.ics) file for an event and emails one copy to each attendee from <fromUsername>@<app domain>, the organizer's own mailbox. The organizer is modelled only as a display name — attendees are the only mailboxes that carry addresses. Use it when I am building a Caffeine AI app that needs events, meetings or emailed calendar invitations. Repository: https://raw.githubusercontent.com/caffeinelabs/skills/f3656c69d957a43a920fc21d9c3a6ef0c74dca21/skills/extension-email-calendar-events/SKILL.md (the skill is the single file skills/extension-email-calendar-events/SKILL.md at that commit — it has no helper files) Pinned version: install the code at commit f3656c69d957a43a920fc21d9c3a6ef0c74dca21 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. [FINGERPRINTS] Files at the pinned commit, from Skill Harbor's review of 2026-10-20: - SKILL.md: SHA-256 00bb36905e9d5df03042ebc0936886a578a9a8dd19d0c7d7813bbcea2189ff2e, 13,602 bytes, 13,600 characters If it does not match, it changed since the review: do not install it yet, tell me what you found and let me decide. Updated October 20, 2026: Skill Harbor regenerated this install prompt from the current upstream file. The skill moved from version 0.3.0 to 0.4.1 (its mops dependencies moved to caffeineai-email-calendar-events ~0.4.0 and caffeineai-email ~0.4.0), and the change that matters in use is about how invitations are sent. Before, sendCalendarEvent sent through the mail gateway when the canister had the gateway key and fell back to a transport canister otherwise. That fallback is gone: invitations now always go through the mail gateway, using the settings the platform injects on every deploy, and when those settings are missing sendCalendarEvent returns #err instead of falling back. The file also states plainly now that a failed send never throws — it returns #err(error) with the error text — and the example for sending an invitation was hardened to match: it switches on the result and traps with "Failed to send the invitation: " plus the error on #err, instead of ignoring the awaited result as the old example did. Upgrading an app built on 0.3.x takes no app-code changes: re-pin with mops add [email protected] and mops add [email protected]. Everything else is unchanged: the event types and CRUD operations, the organizer-as-display-name model, the roles, the sequence rules, and the stated limit that receiving RSVPs from attendees is not supported yet. What is sent and executed, and when: nothing is sent anywhere and nothing is executed during installation itself — installing only downloads the pinned SKILL.md from GitHub and copies it. Sending happens later, in use, when the app calls sendCalendarEvent: one email per attendee leaves through the Caffeine mail gateway, from <fromUsername>@<app domain>, carrying the event's summary, description, location, start and end times, the organizer display name and the attendees' names and email addresses, with the .ics file built by the module attached. No other data leaves, and the gateway key is the platform's injected setting, never a secret of mine pasted in chat. 1. Fetch SKILL.md at the pinned commit into a temporary folder, then compare it with the fingerprint from Skill Harbor's review of 2026-10-20 (see [FINGERPRINTS] above). If it does not match, do not install it yet, tell me what you found and let me decide. 2. Safety check: read SKILL.md and review it for anything suspicious (unexpected network calls, shell commands, credential harvesting); STOP on any red flag and tell me. Tell me in plain words what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Confirm these points from the file: - The skill is a single SKILL.md of guidance plus Motoko code blocks — it ships no bundled scripts, no shell commands and no background service, and nothing runs on its own. Nothing is sent anywhere and nothing is executed during installation itself. Everything below happens in use, inside a Caffeine AI app built with this skill. - The module it tells the app to use, mo:caffeineai-email-calendar-events/calendarEvents.mo, is prefabricated and cannot be modified. Its operations are local state changes on the canister: add, update, addAttendees, removeAttendees and cancel store the change with the next sequence number and return the stored record; delete removes; get, iter and reverse read. The organizer carries only a display name ({ name = ?Text }) — never model the organizer as a user with an email address, never pass a full sender address, and never read or guess the app domain in the app; fromUsername is the local part only, such as events or no-reply. - Sending: sendCalendarEvent(fromUsername, event) sends one invitation copy per attendee through the mail gateway only — there is no transport-canister fallback anymore at this version. The gateway settings (INTEGRATIONS_GATEWAY_URL / INTEGRATIONS_GATEWAY_API_KEY) are injected by the platform on every deploy; without them the call returns #err. It returns #ok once the invitation was accepted for every attendee, otherwise #err(error) with the error text, and a failed send never throws — app code should switch on the result and handle #err, as the file's example does, rather than ignoring the result. - Data that leaves in use: the invitation emails themselves — event summary, description, location, start and end times, organizer display name, and each attendee's name and email address — sent to the attendees through the mail gateway, with an iCalendar (.ics) attachment the module builds. caffeineai-email is a dependency of this package but the app does not call it for calendar mail. The skill does not support receiving RSVPs: invitations go out, replies do not come back through it. - The example app in the file gates every endpoint behind the caffeineai-authorization component (admin permission), registers users with a name and email stored on the canister, and makes every registered user a required attendee of new events; the migration file starts from empty state. That is the example's design, shown in the file — not something the skill does silently. 3. Confirmation: before installing, give me a short summary of what the skill does plus your safety findings, and wait for my explicit "yes, install". 4. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "caffeinelabs-extension-email-calendar-events". 5. Verify with no network calls: frontmatter valid, files in place, and the copied SKILL.md still matches its fingerprint above. 6. Report what was installed, where, and what I still need to do myself (e.g. have a Caffeine AI Plus or Pro project, install caffeinelabs-extension-email first, and know that invitations only send when the platform has injected the mail gateway settings on deploy — otherwise sendCalendarEvent returns #err and there is no fallback). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit f3656c6 · 2026-10-20
🧪 Install ran in our test sandbox · Nov 18, 2026
👁 Observed during the install test · Nov 18, 2026 : registry.npmjs.org
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
f3656c6 · 2026-10-20
Sandbox install test
Install ran in our test sandbox · Nov 18, 2026 · Observed during the install test: registry.npmjs.org
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.