@assemblyline-agents/google-calendar 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 OpenEve contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,21 @@
+# @assemblyline-agents/google-calendar
+
+Official Assembly Line Google Calendar connection plugin.
+
+It exposes calendars, events, and availability through a dedicated MCP connection. Calendar authorization stays independent from Gmail and Google Drive. The package exports `defineGoogleCalendarConnection(options)` and bundles focused Calendar guidance under `skills/`.
+
+## Install
+
+```sh
+npm install @assemblyline-agents/google-calendar
+```
+
+Configure `GOOGLE_CALENDAR_MCP_URL` and `GOOGLE_CALENDAR_MCP_TOKEN`, or pass the connection URL and authentication resolver directly. New connections scaffold read-only; event changes require explicit write access and the configured approval policy.
+
+## Part of Assembly Line
+
+This package is part of [Assembly Line](https://github.com/jasonbadeaux/openeve). See the [developer documentation](https://github.com/jasonbadeaux/openeve/tree/main/docs/developers) for setup, agent authoring, and deployment guides.
+
+## License
+
+MIT

package/dist/index.d.ts

@@ -0,0 +1,5 @@
+import { type McpPluginConnectionOptions } from "@assemblyline-agents/core";
+export type GoogleCalendarConnectionOptions = McpPluginConnectionOptions;
+export declare function defineGoogleCalendarConnection(options: GoogleCalendarConnectionOptions): import("@assemblyline-agents/core").McpHttpClientConnectionDefinition;
+export declare const openevePlugin: import("@assemblyline-agents/core").PluginModule;
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAIL,KAAK,0BAA0B,EAChC,MAAM,2BAA2B,CAAC;AAInC,MAAM,MAAM,+BAA+B,GAAG,0BAA0B,CAAC;AAEzE,wBAAgB,8BAA8B,CAAC,OAAO,EAAE,+BAA+B,yEAEtF;AAED,eAAO,MAAM,aAAa,kDAA0C,CAAC"}

package/dist/index.js

@@ -0,0 +1,7 @@
+import { connectionPluginMetadata, defineMcpPluginConnection, definePlugin } from "@assemblyline-agents/core";
+const PLUGIN = connectionPluginMetadata("google-calendar");
+export function defineGoogleCalendarConnection(options) {
+    return defineMcpPluginConnection(PLUGIN, options);
+}
+export const openevePlugin = definePlugin({ connections: [PLUGIN] });
+//# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,wBAAwB,EACxB,yBAAyB,EACzB,YAAY,EAEb,MAAM,2BAA2B,CAAC;AAEnC,MAAM,MAAM,GAAG,wBAAwB,CAAC,iBAAiB,CAAE,CAAC;AAI5D,MAAM,UAAU,8BAA8B,CAAC,OAAwC;IACrF,OAAO,yBAAyB,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;AACpD,CAAC;AAED,MAAM,CAAC,MAAM,aAAa,GAAG,YAAY,CAAC,EAAE,WAAW,EAAE,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC"}

package/package.json

@@ -0,0 +1,49 @@
+{
+  "name": "@assemblyline-agents/google-calendar",
+  "version": "0.1.0",
+  "type": "module",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "default": "./dist/index.js"
+    }
+  },
+  "dependencies": {
+    "@assemblyline-agents/core": "0.1.0"
+  },
+  "description": "Official OpenEve Google Calendar connection plugin.",
+  "files": [
+    "dist",
+    "skills"
+  ],
+  "engines": {
+    "node": ">=22.19.0"
+  },
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/jasonbadeaux/openeve.git",
+    "directory": "packages/google-calendar"
+  },
+  "bugs": {
+    "url": "https://github.com/jasonbadeaux/openeve/issues"
+  },
+  "homepage": "https://github.com/jasonbadeaux/openeve#readme",
+  "author": "OpenEve contributors",
+  "keywords": [
+    "openeve",
+    "ai",
+    "agents",
+    "google-calendar",
+    "calendar",
+    "connection",
+    "plugin"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "scripts": {
+    "build": "tsc -p tsconfig.json",
+    "check": "tsc -p tsconfig.json --noEmit"
+  }
+}

package/skills/google-calendar/SKILL.md

@@ -0,0 +1,13 @@
+---
+name: google-calendar
+description: Use a configured, independently authorized Google Calendar connection for events, availability, invitations, and scheduling.
+---
+# Google Calendar
+
+Use the `google-calendar` connection only for Calendar work. Its authorization is independent from Gmail and Google Drive; never assume either service is connected because Calendar is connected.
+
+Read the exact calendar and event state before proposing a change. Interpret relative dates in the user's timezone, preserve timezone information, and resolve ambiguous matching events before editing. The deployment owner configures the Calendar OAuth grant or MCP bridge. Never request, print, or store tokens or client secrets.
+
+The scaffold is read-only. Creating, updating, moving, deleting, or inviting through Calendar requires explicit write access and the configured approval gate. Attendee changes send real notifications, so never add attendees unless that intent is clear.
+
+Read `references/calendar.md` when the task needs event shapes, all-day rules, timezone handling, update safety, or confirmation details.

package/skills/google-calendar/references/calendar.md

@@ -0,0 +1,45 @@
+# Google Calendar
+
+Use the configured `google-calendar` connection for calendars, events, availability, event creation, and event updates.
+
+Official documentation:
+
+- https://developers.google.com/workspace/calendar/api/v3/reference
+- https://developers.google.com/workspace/calendar/api/v3/reference/events/insert
+- https://developers.google.com/workspace/calendar/api/guides/create-events
+
+## Event Reads
+
+For agenda questions, set an explicit time range when possible, use the user's local timezone, expand recurring instances when supported, and keep the result compact unless the user asks for a detailed agenda. The default calendar id is commonly `primary`.
+
+Important fields include the event id, title, status, start and end, timezone, location, organizer, attendees, recurrence, conference data, attachments, link, and event type.
+
+## Event Creation
+
+Create events only when the intent, date, start, duration or end, timezone, calendar, and attendee behavior are clear. A timed event body commonly includes:
+
+```json
+{
+  "summary": "Call with Maya",
+  "start": {
+    "dateTime": "2026-05-25T10:00:00-05:00",
+    "timeZone": "America/Chicago"
+  },
+  "end": {
+    "dateTime": "2026-05-25T10:30:00-05:00",
+    "timeZone": "America/Chicago"
+  }
+}
+```
+
+For all-day events, `end.date` is exclusive. A one-day event starts on the requested date and ends on the next date.
+
+## Event Updates
+
+Resolve the exact event id before an update. Preserve fields not being changed, and be careful with attendee, recurrence, and attachment arrays because including them can replace existing values.
+
+Do not clear calendars or mass-edit, delete, move, import, or quick-add events unless the user requested that exact action and the connection exposes a reviewed, approval-gated operation.
+
+## Timezones And Invitations
+
+Interpret “today,” “tomorrow,” and weekday names relative to the user's local date rather than UTC. Include the timezone in write confirmations. Attendee edits can send invitations or updates; do not silently invite people.