Gws Meet

Manage Google Meet conferences.

Security Scan

The skill is a thin wrapper around a 'gws' CLI (which matches its stated purpose) but it directs the agent to rely on an external shared auth file that is not included or described, so credential and filesystem behavior is unclear.

Purpose & Capability

The skill's name/description align with the required binary (gws) and the SKILL.md instructs the agent to run gws CLI commands to manage Google Meet resources — the requested binary is appropriate for the stated purpose.

Instruction Scope

The runtime instructions tell the agent to read ../gws-shared/SKILL.md for auth, global flags, and security rules; that file is not present in this bundle. If missing, the instructions tell the agent to run `gws generate-skills` which will create files. Directing the agent to read or generate files outside the skill directory expands its file-system scope and may create or rely on credentials/configuration not visible in the package.

Install Mechanism

No install spec and no code files — instruction-only skill. This is lower-risk from an install mechanism perspective because nothing in this package will be written to disk by the skill itself.

Credentials

The skill declares no required environment variables, yet it defers auth to an external shared SKILL.md and the gws CLI. That implies credentials or configuration are expected but not declared, so the exact credential access (where keys live, whether the CLI reads OAuth tokens, config files under the user's home, etc.) is unclear.

Persistence & Privilege

The skill does not request always: true and has no explicit persistence or changes to other skills' configs. Autonomous invocation is allowed (default), which is normal; nothing else in the package requests elevated persistence.

What to consider before installing

This skill is essentially an instruction sheet for the external 'gws' CLI to manage Google Meet and is otherwise empty. Before installing or enabling it: 1) Verify you trust the 'gws' binary (where it comes from, its version, and how it authenticates). 2) Inspect the referenced ../gws-shared/SKILL.md (if present) to see exactly how auth and security rules are handled; if it doesn't exist, be cautious about running `gws generate-skills` because that will create files on disk and may store credentials. 3) Determine where the gws CLI stores credentials (home dir, system keyring, or env vars) and whether those locations are acceptable. 4) If the skill's publisher/source is unknown, consider running gws and any skill operations in an isolated test environment and avoid supplying high-privilege credentials until you confirm behavior. 5) If you need more certainty, ask the publisher for the shared auth SKILL.md or documentation that explains authentication and what files the CLI will create or read.

meet (v2)

PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to create it.

gws meet <resource> <method> [flags]

API Resources

conferenceRecords

• get — Gets a conference record by conference ID.
• list — Lists the conference records. By default, ordered by start time and in descending order.
• participants — Operations on the 'participants' resource
• recordings — Operations on the 'recordings' resource
• smartNotes — Operations on the 'smartNotes' resource
• transcripts — Operations on the 'transcripts' resource

spaces

• create — Creates a space.
• endActiveConference — Ends an active conference (if there's one). For an example, see End active conference.
• get — Gets details about a meeting space. For an example, see Get a meeting space.
• patch — Updates details about a meeting space. For an example, see Update a meeting space.

Discovering Commands

Before calling any API method, inspect it:

# Browse resources and methods
gws meet --help

# Inspect a method's required params, types, and defaults
gws schema meet.<resource>.<method>

Use gws schema output to build your --params and --json flags.