Skip to content
TrustedSkillsbeta
Back to all skills

Gws Calendar

Checked
googleworkspace·vlatest·productivity·Apache-2.0

Gws Calendar seamlessly integrates Google Workspace calendars, enabling you to schedule meetings and events directly within this AI agent for effortless productivity.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add googleworkspace/cli --skill gws-calendar -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

googleworkspace

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned googleworkspace/cli at a3768d0e82.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
a3768d0e82
Manifest
skills/gws-calendar/SKILL.md
Scanned
1 file, 106 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The gws-calendar skill allows AI agents to interact with Google Workspace calendars, enabling tasks such as creating, updating, and retrieving calendar events. It provides access to calendar data through the Google Calendar API, making it useful for managing schedules, setting reminders, and synchronizing event details across platforms.

When to use it

  • Automating recurring meeting scheduling for a team based on availability
  • Syncing personal or team calendars with external systems or applications
  • Generating daily summaries of upcoming events from a user's calendar

Key capabilities

  • Create and modify calendar events
  • Retrieve calendar data and event details
  • Access calendar permissions and settings

Example prompts

  • "Create a meeting event for 10 AM tomorrow with the marketing team."
  • "Show me all my scheduled meetings this week."
  • "Update the project kickoff meeting to 2 PM on Thursday."

Tips & gotchas

  • Ensure that the AI agent has proper authentication and calendar access permissions.
  • Be mindful of time zone settings when scheduling or retrieving events.