How to use the Google Meet Manager agent skill (gws-meet)

What the gws-meet skill lets the agent do

An agent skill is a folder containing a SKILL.md file that tells an agent how to handle a particular task. This one covers Google Meet. Once it is installed, the agent can work with Meet through the gws command line.

The skill is organised around two resources. Spaces covers creating a meeting space, getting its details, updating them, and ending a conference that is still running. Conference records covers past meetings: you can get or list conference records, which are ordered by start time in descending order by default, and look at their participants, recordings, transcripts and smart notes.

• Create a meeting space
• Get or update a meeting space's details
• End an active conference, if there is one
• List past conference records and their participants, recordings, transcripts and smart notes

What you need before installing

The skill cannot work on its own. It depends on the gws command-line tool being installed and authenticated with a Google account. Your account also needs a Google Workspace account with Google Meet API access.

The skill's SKILL.md begins by pointing to a gws-shared SKILL.md file, which holds authentication, global flags and security rules. If that file is missing, the source says to generate it with gws generate-skills.

• The gws command-line tool (Google Workspace CLI), installed and authenticated with a Google account
• A Google Workspace account with Google Meet API access
• The gws-shared SKILL.md file, created with gws generate-skills if it is missing

Install the gws-meet skill

The skill is distributed as a single file, SKILL.md. Download the ZIP from the agent-skills directory page, then choose one of two routes.

For Claude Code, unzip the download into ~/.claude/skills/ to make it available to you everywhere, or into a project's .claude/skills/ folder to limit it to that project.

If you use the Claude apps, upload the ZIP under Settings, then Capabilities, then Skills.

• Personal install: unzip into ~/.claude/skills/
• Project install: unzip into the project's .claude/skills/ folder
• Claude apps: Settings → Capabilities → Skills, then upload the ZIP

Trigger the skill with natural requests

You do not need to name the skill or type a command. Describe the Meet task in plain language and the agent should pick up the skill when the request matches its description, which is managing Google Meet conferences.

Before the agent calls any method, the skill tells it to check the available commands and their required parameters. You can ask it to do that check first if you want to see its plan.

• Create a Meet space for a 30-minute review with the design team and give me the join link.
• Show me the details of this meeting space and tell me whether a conference is active.
• List last week's conference records and summarise who attended each one.
• Pull the transcript from yesterday's 2pm call and list the action items.

How the agent finds the right commands

The skill tells the agent to look things up rather than guess. Two commands from the skill's documentation do this work. gws meet --help lists the resources and methods. gws schema shows a single method's required parameters, types and defaults.

The agent uses the schema output to build its --params and --json flags. You can run these yourself to check what the agent will do.

Safety notes: scripts and network access

This skill runs scripts and uses the network, because it calls the Google Meet API through gws. Anything the agent does is done with your authenticated account, so its permissions are your permissions.

Two actions deserve a check before you approve them. Ending an active conference stops a meeting that may still be running. Updating a meeting space changes its settings. Transcripts and recordings can contain private data, so treat them with the same care as the original call.

The skill is not for joining or recording a live call. It only calls the Meet API and does not control the call interface.

• Review any request that ends a conference or changes meeting settings before you approve it
• Do not use it on sensitive meetings without review
• Handle exported transcripts and recordings as private data

Tips for getting good results

Give the agent specific identifiers when you have them, such as a conference ID for a past call or a meeting space for an update. Specific requests reduce the chance that it works on the wrong record.

If a method fails or the agent seems unsure about a parameter, ask it to run the schema check for that method again. The gws meet --help page also shows the full list of methods, which can help you confirm what is available.

• Name the conference or space you mean
• Ask for a schema check when a parameter is unclear
• Start with read-only requests such as get and list before any change