Google Workflow: Prepare for your next meeting: agenda, attendees, and linked docs.
Install with the open skills CLI (global, non-interactive — available in every Claude Code session):
npx skills add googleworkspace/cli --skill "gws-workflow-meeting-prep" -g -a claude-code -yOr manually — copy the SKILL.md below into:
~/.claude/skills/gws-workflow-meeting-prep-googleworkspace/SKILL.md---
name: gws-workflow-meeting-prep
description: "Google Workflow: Prepare for your next meeting: agenda, attendees, and linked docs."
metadata:
version: 0.22.5
openclaw:
category: "productivity"
requires:
bins:
- gws
cliHelp: "gws workflow +meeting-prep --help"
---
# 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
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints