gws-meet
by googleworkspacegws-meet is the Google Meet skill in googleworkspace/cli for managing conference records and meeting spaces through the gws CLI. It supports workflow automation for list, get, create, patch, and endActiveConference tasks when you have the right IDs, filters, and permissions.
This skill scores 78/100, which means it is a solid directory candidate: users get a clear trigger (`gws meet <resource> <method> [flags]`), a defined Google Meet API surface, and explicit guidance to inspect resources before calling methods. It is listable for agents that need Meet administration workflows, though users should expect some setup dependency on the shared gws skill and relatively sparse onboarding around real-world task flows.
- Clear command pattern and help reference make it easy for an agent to trigger correctly.
- Covers concrete Google Meet API resources and methods, including spaces and conferenceRecords operations.
- Includes a prerequisite and discovery step, reducing guesswork versus a generic prompt.
- Depends on `../gws-shared/SKILL.md` and the broader gws setup, so it is not fully self-contained.
- Lacks an install command and dedicated support files, which limits quick adoption and edge-case guidance.
Overview of gws-meet skill
gws-meet is the Google Meet-focused skill in googleworkspace/cli for managing Meet spaces and meeting artifacts through the gws CLI. It is best for users who need to automate Meet operations with a workflow agent instead of hand-coding API calls, especially when they care about conference records, recordings, transcripts, or space management.
This gws-meet skill is not a generic “chat about Meet” prompt. It maps to real API resources and expects structured intent: which resource you want, which method you need, and what identifiers or filters you can provide. That makes it useful for Workflow Automation, but only if you can supply clear meeting context.
What gws-meet is for
Use gws-meet when the job is to inspect or manage Meet data, such as listing conference records, fetching a specific record, working with participants or recordings, or updating a meeting space. It is also a good fit when you want a repeatable gws-meet usage pattern instead of ad hoc console clicks.
What matters before you install
The main adoption gate is environment readiness. gws-meet depends on the gws binary and on shared auth and security rules from ../gws-shared/SKILL.md. If your workspace cannot satisfy those prerequisites, the skill will not be reliable.
Why this skill is different
The value of gws-meet is its API-aligned structure: you discover methods first, then call the exact resource action you need. That reduces guesswork, but it also means the skill works best when you already know your target object, such as a conference ID, meeting space, or date range.
How to Use gws-meet skill
Install and verify prerequisites
For gws-meet install, use the repository’s skill workflow and confirm that gws is available in your environment. Then read ../gws-shared/SKILL.md before invoking any Meet method, because the shared file defines auth, global flags, and security constraints that this skill inherits.
A practical install check is to run the CLI help for the Meet surface, then confirm that your account has the permissions needed for the resources you plan to touch.
Start with the skill entrypoint
The skill entrypoint is SKILL.md. Read it first, then follow the method discovery pattern it recommends. For gws-meet usage, the most important habit is to inspect resources before you call them:
gws meet --help
gws meet <resource> --help
gws meet <resource> <method> --help
That prevents overfitting a prompt to the wrong resource or assuming a method exists when it does not.
Turn a rough goal into a good prompt
A strong prompt for gws-meet should name:
- the resource:
conferenceRecordsorspaces - the method:
get,list,create,patch, orendActiveConference - the identifier or filter you already know
- the output you want, such as a summary, a specific field set, or a follow-up action
For example, instead of “check my Google Meet data,” ask for something like: “Use gws-meet to list conference records from the last 7 days, then summarize the newest 5 by start time and participant count.”
Read the right files first
The repository is intentionally light, so the highest-signal path is:
SKILL.md../gws-shared/SKILL.md- CLI help from
gws meet --help
That order matters because the skill body is short, and the shared skill carries the rules that govern execution. If you skip the shared file, you may mis-handle auth or security-related behavior.
gws-meet skill FAQ
Is gws-meet only for administrators?
No. gws-meet is useful for any authorized user who needs to automate Meet operations, but access still depends on your account permissions and the specific API resource. If you cannot read or modify a meeting object in Google Workspace, the skill will not bypass that.
Should I use gws-meet instead of a plain prompt?
Use the gws-meet skill when you want repeatable, tool-backed actions with fewer assumptions. A plain prompt is fine for brainstorming, but gws-meet is better when the task needs exact API method selection, consistent CLI usage, and a path to automation.
What is the biggest limitation?
The skill is narrow by design. It focuses on Meet resources and does not provide broad workspace management. If your goal spans Calendar, Drive, or Chat in the same run, gws-meet is only one piece of the workflow.
Is gws-meet beginner-friendly?
Yes, if you already know the meeting object you want to work with. It is less beginner-friendly when you start from a vague question like “What happened in all my meetings?” because the skill works best with explicit resource names, IDs, and date ranges.
How to Improve gws-meet skill
Give the agent the exact Meet target
The fastest way to improve gws-meet results is to provide the concrete target up front: a conference ID, meeting space, date window, or filter condition. “Find the last conference record for team-sync between Monday and Friday” is much better than “look up my meetings.”
Ask for one API-shaped task at a time
The skill performs best when each request maps cleanly to one resource and one method. If you need a chain like list → inspect → update, split it into steps so the tool can validate each result before moving on.
Include output constraints
Tell the agent whether you want raw CLI output, a concise summary, or fields extracted into a table. This reduces unnecessary back-and-forth and helps gws-meet stay focused on the actual workflow, not on deciding the presentation format.
Watch for common failure modes
The most common errors are missing prerequisites, vague resource selection, and assuming a method supports data you have not confirmed. When the first attempt fails, improve the next prompt by adding the exact gws meet <resource> <method> shape, the identifier, and the date or ownership scope.