← 返回 Skills 市场
byungkyu

Google Calendar

作者 byungkyu · GitHub ↗ · v1.2.6 · MIT-0
cross-platform ✓ 安全检测通过
12464
总下载
21
收藏
0
当前安装
17
版本数
在 OpenClaw 中安装
/install google-calendar-api
功能描述
Google Calendar API integration with managed OAuth. Create events, list calendars, check availability, and manage schedules. Use this skill when users want to interact with Google Calendar. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Calendar connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Calendar action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Calendar examples; they add no Google Calendar capability - Google Calendar is not an event source, a trigger cannot read Google Calendar data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
安全使用建议
Install only if you trust Maton and want an agent to work with your Google Calendar. Prefer OAuth login over API keys, choose the narrowest Google scopes and connection, confirm every calendar write, and review any function, trigger, or destination carefully because those can keep running or forwarding data until deleted.
能力评估
✓ Credentials
Network access, Google Calendar OAuth, and Maton gateway calls are necessary for the integration. Raw HTTP with MATON_API_KEY is limited to environments without the CLI and includes clear secret-handling guidance.
ℹ Install Mechanism
Installation uses pinned Maton CLI packages through npm or Homebrew and requires Maton OAuth login; this is disclosed and proportionate, though users must trust the Maton CLI and account connection.
ℹ Instruction Scope
The skill includes broad platform reference sections for functions, triggers, and other event-source catalogs, but repeatedly states they do not widen Google Calendar access and require user direction and explicit approval for writes, automations, destinations, and local --exec use.
ℹ Persistence & Privilege
The CLI stores tokens in the OS credential store, and optional hosted functions/triggers/destinations can persist and run automatically. The artifact discloses this clearly and requires separate approval, least privilege, DENY_ALL network policy by default, and cleanup.
✓ Purpose & Capability
The stated purpose is Google Calendar access via managed OAuth, and the documented capabilities fit that purpose: listing calendars/events, creating/updating/deleting events, checking availability, and optional Maton-hosted automation.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install google-calendar-api
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /google-calendar-api 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.2.6
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.5
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.4
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.3
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.2
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.1
Address security-audit findings: disclose the api passthrough in the access-scope and description text, warn on irreversible connection deletion, add response data-minimization guidance, and correct app-specific auth and request-body notes
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.8
- Removed the skill-card.md file from the project. - No changes to functionality or APIs. - Documentation and usage remain the same.
v1.0.7
- Added CLI command examples throughout for key workflows, including listing events and managing connections. - Added installation instructions for NPM and Homebrew. - Updated authentication and connection management sections with CLI usage alongside API examples. - Expanded quick start section with practical 'agenda' command examples. - Added CLI equivalents to API reference endpoints for easier usage. - Improved clarity and structure of setup and operational instructions.
v1.0.6
- Updated all endpoint URLs from gateway.maton.ai and ctrl.maton.ai to api.maton.ai. - Clarified connection management instructions and updated related endpoint examples. - Added a section on security and permissions, emphasizing user approval for write operations. - Removed the LICENSE.txt file from the repository.
v1.0.5
- Added a new `clawdbot` metadata section with an emoji and required `MATON_API_KEY` environment variable. - No changes to code, endpoints, or functionality.
v1.0.4
No changes detected in this version.
v1.0.3
- Replaced most curl command examples with Python command-line scripts using `urllib.request` for easier cross-platform usage. - Updated "Quick Start" and connection management sections to use Python snippets instead of curl. - Documentation now emphasizes Python as the main method for interacting with the API from the command line. - No changes to the API or endpoints; all updates are in documentation and examples only.
v1.0.2
- Added a note in the description directing users to use the api-gateway skill for other third party apps. - Improved curl and environment variable usage instructions, including new notes on using curl -g with bracketed parameters and caveats about environment variable expansion when piping to other commands.
v1.0.1
- Updated the base URL syntax to use `{native-api-path}` for clarity. - Expanded information and examples for specifying the Google Calendar connection with the `Maton-Connection` header. - Added new fields to connection response examples, such as `creation_time`, `last_updated_time`, and `metadata`. - Clarified instructions for obtaining an API key and managing multiple Google Calendar connections.
v1.0.0
Major update: Migrated implementation from local Python scripts to a managed cloud API with OAuth integration. - Replaced all Python scripts and local environment setup with Maton-hosted endpoints and OAuth flow. - Added detailed instructions for using the Maton API gateway and managing OAuth connections. - Updated authentication to use the Maton API key in request headers. - Provided comprehensive API reference and example code for JS and Python. - Included error handling guidelines and links to official Google Calendar API resources.
元数据
Slug google-calendar-api
版本 1.2.6
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 17
常见问题

Google Calendar 是什么?

Google Calendar API integration with managed OAuth. Create events, list calendars, check availability, and manage schedules. Use this skill when users want to interact with Google Calendar. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Calendar connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Calendar action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Calendar examples; they add no Google Calendar capability - Google Calendar is not an event source, a trigger cannot read Google Calendar data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 12464 次。

如何安装 Google Calendar?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install google-calendar-api」即可一键安装,无需额外配置。

Google Calendar 是免费的吗?

是的,Google Calendar 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Google Calendar 支持哪些平台?

Google Calendar 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Google Calendar?

由 byungkyu(@byungkyu)开发并维护,当前版本 v1.2.6。

💬 留言讨论