Skill: hith3sh/google-calendar-scheduling (version 0.1.1)

--- name: google-calendar-scheduling description: Review calendars, inspect events, find free time, and coordinate calendar changes with confirmation — powered by ClawLink. --- # Google Calendar via ClawLink Work with Google Calendar from chat — review calendars, inspect events, find free time, and coordinate event changes when needed. Powered by [ClawLink](https://claw-link.dev), an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Google Calendar API access yourself. This skill is a setup and usage guide for the existing ClawLink plugin. It does not bundle executable code or ask the user to paste raw credentials into chat. ## Quick start 1. Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin` 2. Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet 3. If ClawLink is not configured, call `clawlink_begin_pairing` 4. Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device 5. After the user confirms approval, call `clawlink_get_pairing_status` 6. Tell the user to connect Google Calendar at [claw-link.dev/dashboard?add=google-calendar](https://claw-link.dev/dashboard?add=google-calendar) 7. When the user confirms Google Calendar is connected, call `clawlink_list_integrations` and then `clawlink_list_tools` with the `google-calendar` integration slug ## Setup details ### Installing the plugin If the ClawLink plugin is not installed yet, tell the user to run: ``` openclaw plugins install clawhub:clawlink-plugin ``` If the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog. ### Pairing ClawLink If ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet. 1. Call `clawlink_begin_pairing`. 2. Tell the user to open the returned pairing URL in their browser. 3. The user signs in to ClawLink if needed and approves the OpenClaw device. 4. After the user confirms approval, call `clawlink_get_pairing_status` to finish local setup. Pairing stores a local ClawLink credential in OpenClaw's plugin config so future tool calls can work. The user should not paste raw credentials into chat. ### Connecting Google Calendar Tell the user to open https://claw-link.dev/dashboard?add=google-calendar and connect Google Calendar there. The page opens the add-connection panel filtered to Google Calendar. ClawLink's hosted page runs the Google account connection flow — the user clicks through Google sign-in and consent. When they confirm it is done, call `clawlink_list_integrations` to verify, then call `clawlink_list_tools` with integration `google-calendar`. ## Using Google Calendar tools ClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance. ### Discovery 1. Call `clawlink_list_integrations` to confirm Google Calendar is connected. 2. Call `clawlink_list_tools` with integration `google-calendar`. 3. Treat the returned list as the source of truth. Do not guess or assume what tools exist. 4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `google-calendar`. 5. If no Google Calendar tools appear, direct the user to https://claw-link.dev/dashboard?add=google-calendar. ### Execution 1. Call `clawlink_describe_tool` before using an unfamiliar tool, before any write, or when the request is ambiguous. 2. Use the returned schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups`. 3. Prefer read, list, search, and availability operations before writes. 4. For event changes or other high-impact actions, call `clawlink_preview_tool` first, then confirm with the user. 5. Execute with `clawlink_call_tool`. 6. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion. ## What you can do Typical Google Calendar tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog): - List the calendars available to the connected account - Show event details for a given day, date range, or event ID - Find recurring event instances - Search for events by title, time, or attendee context - Find free time slots across one or more calendars - Create events from structured details or natural-language requests after confirmation - Adjust existing events after confirmation, and treat moves or deletions as especially sensitive - Check timezone-aware current date and time before scheduling ## Rules - Always use ClawLink tools for Google Calendar. Do not ask the user for separate Google credentials. - Do not claim a capability is missing without checking the live ClawLink catalog in the current turn. - Do not invent slash commands or ask the user to paste raw credentials. - Ask for confirmation before creating, editing, moving, or deleting events, especially when attendees could be affected. - If Google Calendar is not connected, direct the user to https://claw-link.dev/dashboard?add=google-calendar. - Never echo or repeat the user's ClawLink credential. ## Resources - ClawLink: https://claw-link.dev - ClawLink Docs: https://docs.claw-link.dev/openclaw - ClawLink Verification: https://claw-link.dev/verify - ClawLink Source: https://github.com/hith3sh/clawlink - Google Calendar API: https://developers.google.com/workspace/calendar/api/guides/overview


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)