Skills extension-email-calendar-events
📦

extension-email-calendar-events

v0.1.5 Content revision r1 Medium Risk ⚙️ External commands🌐 Network access📁 Filesystem access

Build Email Calendar Invitations

Building calendar workflows and iCalendar email delivery requires coordinated storage, permissions, and message formatting. This skill provides Motoko patterns for event management and invitation sending.

Supports: Claude Codex Code(CC)
📊 72 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "extension-email-calendar-events" from https://skillstore.io/skills/caffeinelabs-extension-email-calendar-events.md and its manifest at https://skillstore.io/api/skills/caffeinelabs-extension-email-calendar-events/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/caffeinelabs-extension-email-calendar-events.md Signed manifest GET /api/skills/caffeinelabs-extension-email-calendar-events/manifest Signed lockfile GET /api/skills/caffeinelabs-extension-email-calendar-events/lockfile

Test it

Using "extension-email-calendar-events". Add a calendar event feature for administrator-managed team meetings.

Expected outcome:

  • A Motoko backend design with administrator-protected event operations.
  • Event records with unique identifiers, times, organizer details, and attendees.
  • An invitation flow using the Caffeine AI email client.

Using "extension-email-calendar-events". Review my invitation workflow before deployment.

Expected outcome:

  • Verify each recipient email before adding it to an event.
  • Validate that the end time follows the start time.
  • Handle delivery failures and prevent accidental duplicate invitations.

Using "extension-email-calendar-events". Explain the event lifecycle supported by this skill.

Expected outcome:

Events can be created, retrieved, listed, updated, canceled, deleted, and sent to attendees as iCalendar email invitations.

Security Audit

Medium Risk
v1 • 7/24/2026 Open versioned report

All 24 static findings are false positives caused by Markdown links, code fences, module references, and ordinary Motoko uid identifiers. Semantic review found a medium-severity invitation abuse risk because public registration accepts unverified email addresses that are later included as event attendees.

1
Files scanned
328
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
SKILL.md:175-195SKILL.md:226-233SKILL.md:307-324
Unverified Email Enrollment Enables Unwanted Invitations
Any caller can register an arbitrary unique email address without ownership verification. Registered addresses become event attendees and can later receive administrator-triggered invitations.
The example stores caller-supplied email addresses after only uniqueness checks, adds every stored profile to events, and provides an invitation-send operation.

Risk Factors

⚙️ External commands (6)
SKILL.md:28 SKILL.md:30-85 SKILL.md:85-92 SKILL.md:92-137 SKILL.md:137-141 SKILL.md:141-327
🌐 Network access (1)
SKILL.md:13
📁 Filesystem access (1)
SKILL.md:89
Audited by: codex
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/caffeinelabs-extension-email-calendar-events/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/caffeinelabs-extension-email-calendar-events/security.svg)](https://skillstore.io/skills/caffeinelabs-extension-email-calendar-events?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/caffeinelabs-extension-email-calendar-events?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/caffeinelabs-extension-email-calendar-events/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/caffeinelabs-extension-email-calendar-events.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

caffeinelabs. (2026). extension-email-calendar-events security audit report (audit version 1) [Author version 0.1.5]. Skillstore. https://skillstore.io/skills/caffeinelabs-extension-email-calendar-events/audits/1

BibTeX citation

@techreport{caffeinelabs-caffeinelabs-extension-email-calendar-events-2026, author = {caffeinelabs}, title = {extension-email-calendar-events security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/caffeinelabs-extension-email-calendar-events/audits/1}, note = {Author version 0.1.5} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "extension-email-calendar-events security audit report (audit version 1)" version: "0.1.5" type: report authors: - name: "caffeinelabs" date-released: "2026-07-24" url: "https://skillstore.io/skills/caffeinelabs-extension-email-calendar-events/audits/1" identifiers: - type: other value: "skillstore:caffeinelabs-extension-email-calendar-events:audit:1" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
100
Maintainability
87
Content
65
Community
91
Spec Compliance

What You Can Build

Add Scheduling to a Motoko Application

Implement stored events, attendee management, and emailed iCalendar invitations in a Caffeine AI backend.

Manage Internal Meeting Invitations

Create an administrator-controlled workflow for scheduling meetings and inviting registered users.

Review Calendar Integration Design

Assess authorization, identity, event lifecycle, and email delivery patterns before deployment.

Try These Prompts

Add Basic Calendar Events 
Add calendar event storage to my Motoko backend. Include create, get, list, update, cancel, and delete operations using the documented package.
Add Permission-Controlled Invitations 
Create an administrator-only flow that builds an event, adds selected verified attendees, and sends an iCalendar invitation through the email client.
Integrate Existing User Profiles 
Adapt the calendar event example to my existing user profile model. Preserve authorization and require verified email ownership before adding attendees.
Harden the Full Event Workflow 
Review my Motoko calendar workflow for authorization gaps, unverified recipients, invalid time ranges, duplicate sends, delivery failures, and event lifecycle errors.

Best Practices

  • Verify email ownership before making a profile eligible for invitations.
  • Keep every event mutation and invitation operation behind explicit authorization checks.
  • Validate times, attendee addresses, delivery results, and duplicate-send conditions.

Avoid

  • Do not add every registered address to every event without selection or consent.
  • Do not ignore invitation delivery failures or assume that a send always succeeds.
  • Do not expose event mutation methods without role-based authorization.

Frequently Asked Questions

What does this skill add?
It provides Motoko patterns for calendar event storage, lifecycle operations, attendee management, and iCalendar email invitations.
Which platforms does it target?
It targets Motoko backends built with Caffeine AI packages and works as guidance for Claude, Codex, and Claude Code.
Can attendees send RSVP responses?
No. The documented component does not receive or process RSVP responses.
Does it include authorization?
The example uses Caffeine AI authorization and restricts event administration and invitation sending to administrators.
Which dependencies are required?
The workflow depends on the Caffeine AI calendar events, authorization, and email components.
What should be added before production use?
Add email verification, input validation, selected attendee enrollment, delivery error handling, rate limits, and duplicate-send protection.

Developer Details

License

MIT

Author version

v0.1.5

Skillstore revision

r1

Repository

https://github.com/caffeinelabs/skills/tree/56c60e7a2cd2a8abebe0cc93eec429339fff42e2/skills/extension-email-calendar-events

Ref

a39a91716eadede5f4cdefd78178fed4e837a128

Maintenance freshness

7/24/2026

Usage

0 downloads · 0 views

File structure

📄 SKILL.md