어떤 스킬인가요?
내 일정과 회의 정보를 확인하고 조율하는 데 활용하는 스킬입니다. 날짜만 보는 것이 아니라 참석자와 시간대처럼 실제 약속에 필요한 정보를 함께 다룹니다.
대상 날짜와 회의 조건을 먼저 정해보세요. 일정 목록을 확인한 다음 행사 정보를 정리하거나 검토할 초안을 만드는 방식으로 사용할 수 있습니다.
google-calendar · Gemini CLI
연결한 캘린더의 일정을 확인하고 행사 정보를 관리합니다.
내 일정과 회의 정보를 확인하고 조율하는 데 활용하는 스킬입니다. 날짜만 보는 것이 아니라 참석자와 시간대처럼 실제 약속에 필요한 정보를 함께 다룹니다.
대상 날짜와 회의 조건을 먼저 정해보세요. 일정 목록을 확인한 다음 행사 정보를 정리하거나 검토할 초안을 만드는 방식으로 사용할 수 있습니다.
“다음 주 화요일의 일정을 확인해줘. 오후에 가능한 회의 시간을 정리하고 참석자에게 보여줄 일정 초안을 만들어줘.”
받을 수 있는 결과일정 목록 또는 행사 초안
Gemini CLI와 Google 로그인 또는 지원되는 API 인증이 필요해요. Google Workspace 계정의 필요한 앱 권한도 연결하세요.
Gemini CLI가 설치된 터미널에서 실행하세요. 확장을 확인한 뒤 Gemini CLI의 새 세션에서 작업을 요청하세요.
gemini extensions install https://github.com/gemini-cli-extensions/workspace
“google-calendar 스킬을 사용해줘. 입력 자료: 대상 날짜·참석자·시간대”처럼 요청하세요. 위의 예시를 내 자료에 맞게 바꿔도 좋아요.
예상 결과는 ‘일정 목록 또는 행사 초안’입니다. 필요한 내용이 포함됐는지 확인하세요. 입력 자료의 사실·숫자와 결과를 대조하고, 부족한 부분을 이어서 요청하세요.
제작자 원본 2026-10-04 확인 · 설치 안내 2026-10-04 확인 · 실제 설치·실행 미검증
모델 사용 요금과 연결 앱 요금은 이용 중인 서비스의 정책을 따릅니다.
설치 안내 출처--- name: google-calendar description: > CRITICAL: You MUST activate this skill BEFORE creating, querying, or managing calendar events. Always trigger this skill as the first step when the user mentions "calendar", "schedule", "meeting", "event", or checking availability. Contains strict behavioral mandates that override default calendar behavior. --- # Google Calendar Expert You are an expert at managing schedules and events through the Google Calendar API. Follow these guidelines when helping users with calendar tasks. ## Timezone-First Workflow **Always establish the user's timezone before any calendar operation:** 1. Call `time.getTimeZone()` (or `time.getCurrentTime()`) to get the user's local timezone 2. Use this timezone for all time displays and event creation 3. Always include the timezone abbreviation (EST, PST, etc.) when showing times > **Important:** ISO 8601 datetimes sent to the API must include a timezone > offset (e.g., `2025-01-15T10:30:00-05:00`) or use UTC (`Z`). Never send "bare"--- name: google-calendar description: > CRITICAL: You MUST activate this skill BEFORE creating, querying, or managing calendar events. Always trigger this skill as the first step when the user mentions "calendar", "schedule", "meeting", "event", or checking availability. Contains strict behavioral mandates that override default calendar behavior. --- # Google Calendar Expert You are an expert at managing schedules and events through the Google Calendar API. Follow these guidelines when helping users with calendar tasks. ## Timezone-First Workflow **Always establish the user's timezone before any calendar operation:** 1. Call `time.getTimeZone()` (or `time.getCurrentTime()`) to get the user's local timezone 2. Use this timezone for all time displays and event creation 3. Always include the timezone abbreviation (EST, PST, etc.) when showing times > **Important:** ISO 8601 datetimes sent to the API must include a timezone > offset (e.g., `2025-01-15T10:30:00-05:00`) or use UTC (`Z`). Never send "bare" > datetimes without an offset. ## Always Pass `calendarId` **You MUST pass `calendarId: "primary"` on every calendar tool call that accepts it.** Do not omit this parameter — while the API may default to the primary calendar, omitting it wastes an execution turn when the call fails or requires clarification. Always include it explicitly: - `calendar.listEvents({ calendarId: "primary", ... })` - `calendar.createEvent({ calendarId: "primary", ... })` - `calendar.getEvent({ eventId: "...", calendarId: "primary" })` - `calendar.updateEvent({ eventId: "...", calendarId: "primary", ... })` - `calendar.deleteEvent({ eventId: "...", calendarId: "primary" })` - `calendar.respondToEvent({ eventId: "...", calendarId: "primary", ... })` Only use a different `calendarId` when the user explicitly asks to work with a non-primary calendar (discovered via `calendar.list`). ## Understanding "Next Meeting" When asked about "next meeting", "today's schedule", or similar queries: 1. **Fetch the full day's context** — Use `calendar.listEvents` with `calendarId: "primary"`, start of day (`00:00:00`) to end of day (`23:59:59`) in the user's timezone 2. **Filter by response status** — Only show meetings where the user has: - Accepted the invitation - Not yet responded (needs to decide) - **DO NOT** show declined meetings unless explicitly requested 3. **Compare with current time** — Identify meetings relative to now 4. **Handle edge cases**: - If a meeting is in progress, mention it first - "Next" means the first meeting after the current time - Keep the full day context for follow-up questions ## Meeting Response Filtering Use the `attendeeResponseStatus` parameter on `calendar.listEvents` to filter events by the user's response: | Default Behavior | Show Only | | :-------------------- | :--------------------------------- | | Standard schedule | Accepted and pending (needsAction) | | "Show all meetings" | Include declined | | "What did I decline?" | Filter to declined only | This respects the user's time by not cluttering their schedule with irrelevant meetings. ## Creating Events Use `calendar.createEvent` to add new events. **Always preview the event before creating it and wait for user confirmation.** ### Preview Format ``` I'll create this event: 📅 Title: Weekly Standup 📆 Date: January 15, 2025 🕐 Time: 10:00 AM - 10:30 AM (EST) 👥 Attendees: alice@example.com, bob@example.com 📝 Description: Weekly team sync 🎥 Google Meet: Will be generated 📎 Attachments: Q1 Agenda (Google Doc) Should I create this event? ``` ### Key Parameters - **`calendarId`** — **Always pass `"primary"`**. Use `calendar.list` to discover other calendars when needed. - **`start` / `end`** — Two formats: - **Timed events**: `{ dateTime: "2025-01-15T10:00:00-05:00" }` — ISO 8601 with timezone offset - **All-day events**: `{ date: "2025-01-15" }` — YYYY-MM-DD format. The end date is exclusive (use the next day). - **`attendees`** — Array of email addresses - **`addGoogleMeet`** — Set to `true` to automatically generate a Google Meet link (available in response's `hangoutLink` field) - **`attachments`** — Array of Google Drive file attachments (fileUrl, title, optional mimeType). Providing attachments fully replaces any existing attachments. - **`sendUpdates`** — Controls email notifications: - `"all"` — Notify all attendees (default when attendees are provided) - `"externalOnly"` — Only notify non-organization attendees - `"none"` — No notifications - **`eventType`** — The type of event (see [Calendar Status Events](#calendar-status-events) below): - `"default"` — Regular event (default if omitted) - `"focusTime"` — Focus time block - `"outOfOffice"` — Out-of-office event - `"workingLocation"` — Working location indicator ### Example — Regular Timed Event ``` calendar.createEvent({ calendarId: "primary", summary: "Weekly Standup", start: { dateTime: "2025-01-15T10:00:00-05:00" }, end: { dateTime: "2025-01-15T10:30:00-05:00" }, attendees: ["alice@example.com", "bob@example.com"], description: "Weekly team sync", addGoogleMeet: true, attachments: [{ fileUrl: "https://drive.google.com/file/d/abc123/edit", title: "Q1 Agenda", mimeType: "application/vnd.google-apps.document" }], sendUpdates: "all" }) ``` ### Example — All-Day Event ``` calendar.createEvent({ calendarId: "primary", summary: "Team Offsite", start: { date: "2025-01-15" }, end: { date: "2025-01-17" }, description: "Two-day team offsite" }) ``` ## Calendar Status Events `calendar.createEvent` supports creating focus time, out-of-office, and working location events via the `eventType` parameter. These are all created through the same tool — there are no separate tools for each type. ### Focus Time Blocks concentrated work periods. Can auto-decline conflicting meetings. > **Constraint:** Focus time events **cannot be all-day events** — they must use > `dateTime`, not `date`. ``` calendar.createEvent({ calendarId: "primary", eventType: "focusTime", start: { dateTime: "2025-01-15T09:00:00-05:00" }, end: { dateTime: "2025-01-15T12:00:00-05:00" }, focusTimeProperties: { chatStatus: "doNotDisturb", autoDeclineMode: "declineOnlyNewConflictingInvitations", declineMessage: "In focus mode, will respond later" } }) ``` - **`summary`** defaults to `"Focus Time"` if omitted - **`focusTimeProperties.chatStatus`** — `"doNotDisturb"` (default) or `"available"` - **`focusTimeProperties.autoDeclineMode`** — `"declineOnlyNewConflictingInvitations"` (default), `"declineAllConflictingInvitations"`, or `"declineNone"` - **`focusTimeProperties.declineMessage`** — optional message sent when declining ### Out of Office Signals unavailability and auto-declines conflicting meetings. > **Constraint:** Out-of-office events **cannot be all-day events** — they must > use `dateTime`, not `date`. ``` calendar.createEvent({ calendarId: "primary", eventType: "outOfOffice", summary: "Vacation", start: { dateTime: "2025-01-15T00:00:00-05:00" }, end: { dateTime: "2025-01-19T00:00:00-05:00" }, outOfOfficeProperties: { autoDeclineMode: "declineAllConflictingInvitations", declineMessage: "I am on vacation until Jan 19" } }) ``` - **`summary`** defaults to `"Out of Office"` if omitted - **`outOfOfficeProperties.autoDeclineMode`** — `"declineOnlyNewConflictingInvitations"` (default), `"declineAllConflictingInvitations"`, or `"declineNone"` - **`outOfOfficeProperties.declineMessage`** — optional message sent when declining ### Working Location Indicates where the user is working from. Supports both timed and all-day events. ``` calendar.createEvent({ calendarId: "primary", eventType: "workingLocation", start: { date: "2025-01-15" }, end: { date: "2025-01-16" }, workingLocationProperties: { type: "homeOffice" } }) ``` - **`summary`** defaults to `"Working Location"` if omitted - **All-day working location events** must span **exactly one day**. Use the next day as the exclusive `end` date. - **`workingLocationProperties`** is **required** when `eventType` is `"workingLocation"` - **`workingLocationProperties.type`** — `"homeOffice"`, `"officeLocation"`, or `"customLocation"` - **`officeLocation`** — `{ buildingId?: string, label?: string }` (when type is `"officeLocation"`) - **`customLocation`** — `{ label: string }` (when type is `"customLocation"`) ### Listing Events by Type Use the `eventTypes` parameter on `calendar.listEvents` to filter by event type: ``` calendar.listEvents({ calendarId: "primary", timeMin: "2025-01-15T00:00:00-05:00", timeMax: "2025-01-17T23:59:59-05:00", eventTypes: ["focusTime", "outOfOffice", "workingLocation"] }) ``` Available types: `"default"`, `"focusTime"`, `"outOfOffice"`, `"workingLocation"`, `"birthday"`, `"fromGmail"`. ## Updating Events Use `calendar.updateEvent` for modifications. Only the fields you provide will be changed — everything else is preserved. - **Rescheduling**: Update `start` and `end` - **Adding attendees**: Provide the full attendee list (existing + new) - **Changing title/description**: Update `summary` or `description` - **Adding Google Meet**: Set `addGoogleMeet: true` to generate a Meet link - **Managing attachments**: Provide the full attachment list (replaces all existing). Pass `attachments: []` to clear all attachments. > **Important:** The `attendees` field is a full replacement, not an append. To > add a new attendee, include all existing attendees plus the new one. The same > applies to `attachments` — providing attachments fully replaces any existing > attachments on the event. ## Google Meet Integration When creating or updating events, you can automatically generate a Google Meet link by setting `addGoogleMeet: true`: ``` calendar.createEvent({ summary: "Team Standup", start: { dateTime: "2025-01-15T10:00:00-05:00" }, end: { dateTime: "2025-01-15T10:30:00-05:00" }, addGoogleMeet: true }) ``` The Meet URL will be available in the response's `hangoutLink` field: ```json { "hangoutLink": "https://meet.google.com/abc-defg-hij", "conferenceData": { ... } } ``` ## Google Drive Attachments You can attach Google Drive files (Docs, Sheets, Slides, PDFs, etc.) to calendar events: ``` calendar.createEvent({ summary: "Budget Review", start: { dateTime: "2025-01-16T14:00:00-05:00" }, end: { dateTime: "2025-01-16T15:00:00-05:00" }, attachments: [ { fileUrl: "https://drive.google.com/file/d/1ABC123xyz/edit", title: "Q1 Budget Report", mimeType: "application/vnd.google-apps.document" } ] }) ``` **CRITICAL:** Attachments use **replacement semantics**, not append semantics. When you provide attachments, any existing attachments on the event are fully replaced. To add more attachments, include all desired attachments in your update. ## Deleting Events Use `calendar.deleteEvent` to remove an event. **This is a destructive action — always confirm with the user before executing.** | Role | Effect | | :-------- | :-------------------------------------- | | Organizer | Cancels the event for **all** attendees | | Attendee | Removes it from **your** calendar only | ## Responding to Events Use `calendar.respondToEvent` to accept, decline, or tentatively accept meeting invitations: - **`responseStatus`** — `"accepted"`, `"declined"`, or `"tentative"` - **`sendNotification`** — Whether to notify the organizer (default: `true`) - **`responseMessage`** — Optional message to include with your response ``` calendar.respondToEvent({ eventId: "abc123", responseStatus: "accepted", sendNotification: true, responseMessage: "Looking forward to it!" }) ``` ## Finding Free Time Use `calendar.findFreeTime` to find available slots across multiple people's calendars. This is ideal for scheduling new meetings. - **`attendees`** — Email addresses of all participants - **`timeMin` / `timeMax`** — The search window (ISO 8601 with timezone) - **`duration`** — Meeting length in minutes ``` calendar.findFreeTime({ attendees: ["alice@example.com", "bob@example.com"], timeMin: "2025-01-15T09:00:00-05:00", timeMax: "2025-01-17T17:00:00-05:00", duration: 30 }) ``` ## Working with Multiple Calendars Users may have multiple calendars (personal, work, shared team calendars). 1. Use `calendar.list` to discover all available calendars 2. Pass the appropriate `calendarId` to other tools 3. If no `calendarId` is provided, tools default to the **primary** calendar ## Tool Quick Reference | Tool | Action | Key Parameters | | :------------------------ | :------------------------------- | :----------------------------------------------------------------------------------- | | `calendar.list` | List all calendars | _(none)_ | | `calendar.listEvents` | List events (filterable by type) | `calendarId`, `timeMin`, `timeMax`, `eventTypes` | | `calendar.getEvent` | Get event details | `eventId`, `calendarId` | | `calendar.createEvent` | Create event (all types) | `calendarId`, `summary`, `start`, `end`, `eventType`, `addGoogleMeet`, `attachments` | | `calendar.updateEvent` | Modify an existing event | `eventId`, `summary`, `start`, `end`, `attendees`, `addGoogleMeet`, `attachments` | | `calendar.deleteEvent` | Delete an event | `eventId`, `calendarId` | | `calendar.respondToEvent` | Accept/decline an invite | `eventId`, `responseStatus` | | `calendar.findFreeTime` | Find available meeting time | `attendees`, `timeMin`, `timeMax`, `duration` |
Original skill: gemini-cli-extensions/workspace/skills/google-calendar/SKILL.md
Source: https://github.com/gemini-cli-extensions/workspace/blob/089927ead01433f38c65c12cdcd2ed9a18165277/skills/google-calendar/SKILL.md
License: Apache-2.0
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.SKILL.md 본문입니다. 원문에서 참조하는 스크립트·보조 파일은 원본 패키지에 포함되어 있습니다.