gws-workflow-meeting-prep
Google Workflow: Prepare for your next meeting: agenda, attendees, and linked docs.
npx skills add googleworkspace/cli --skill gws-workflow-meeting-prep --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# workflow +meeting-prep > **PREREQUISITE:** Read `../gws-shared/SKILL.md` for auth, global flags, and security rules. If missing, run `gws generate-skills` to create it. Prepare for your next meeting: agenda, attendees, and linked docs ## Usage ```bash gws workflow +meeting-prep ``` ## Flags | Flag | Required | Default | Description | |------|----------|---------|-------------| | `--calendar` | — | primary | Calendar ID (default: primary) | | `--format` | — | — | Output format: json (default), table, yaml, csv | ## Examples ```bash gws workflow +meeting-prep gws workflow +meeting-prep --calendar Work ``` ## Tips - Read-only — never modifies data. - Shows the next upcoming event with attendees and description. ## See Also - [gws-shared](../gws-shared/SKILL.md) — Global flags and auth - [gws-workflow](../gws-workflow/SKILL.md) — All cross-service productivity workflows commands
- Usage
- Flags
- Examples
- Tips
- See Also
gws workflow +meeting-prep gws workflow +meeting-prep --calendar Work
What does the gws-workflow-meeting-prep skill do?
Google Workflow: Prepare for your next meeting: agenda, attendees, and linked docs.
How do I install it?
Run `npx skills add googleworkspace/cli --skill gws-workflow-meeting-prep --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From googleworkspace/cli, a repository with 30,193 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.