Gws Workflow
Chain Gmail, Calendar, Drive, Tasks, and Chat via the `gws` CLI into standup reports, meeting prep, email-to-task, weekly digests, and file announcements without leaving the terminal.
Overview
gws-workflow is an agent skill most often used in Operate (also Build integrations, Grow lifecycle) that runs cross-service Google Workspace productivity flows through the `gws workflow` CLI and documented helper command
Install
npx skills add https://github.com/googleworkspace/cli --skill gws-workflowWhat is this skill?
- Five helper workflows: +standup-report, +meeting-prep, +email-to-task, +weekly-digest, +file-announce
- Generic `gws workflow <resource> <method>` with `gws schema` for param discovery
- Requires `gws` binary and gws-shared auth/security rules
- OpenClaw productivity category v0.22.5 with documented CLI help paths
- 5 documented helper commands (+standup-report, +meeting-prep, +email-to-task, +weekly-digest, +file-announce)
- skill metadata version 0.22.5
Adoption & trust: 17.4k installs on skills.sh; 26.9k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You juggle Gmail, Calendar, Drive, Tasks, and Chat manually when a single CLI workflow could produce standups, digests, and task handoffs.
Who is it for?
Indie operators on Google Workspace who want agent-driven daily standups, meeting prep, and email-to-task without custom Apps Script.
Skip if: Teams on Microsoft 365 only, or builders who cannot install the `gws` CLI and complete gws-shared authentication.
When should I use this skill?
You need Google Workspace cross-service productivity (standup, meeting prep, email-to-task, digest, file announce) via `gws workflow` and have gws installed.
What do I get? / Deliverables
After auth and schema discovery, agents invoke named helpers (+standup-report, +meeting-prep, etc.) or raw workflow methods to produce summaries, tasks, and Chat announcements from live Workspace data.
- Standup or weekly digest text summaries
- Google Tasks entries from Gmail
- Chat announcements for Drive files
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Cross-service Workspace rituals (standup, digest, announce) map most naturally to running the business day-to-day after the product ships—where solo operators live in email, calendar, and shared files. Iterate subphase fits recurring operational loops (daily standup, weekly digest) rather than one-off build or launch spikes.
Where it fits
Start the day with +standup-report so your agent lists today’s meetings and open Tasks without opening four tabs.
Use `gws schema` output to teach an agent the correct params for a custom workflow.<resource>.<method> call.
Pull +weekly-digest to see meeting load and unread mail before planning outreach or content blocks.
How it compares
Workspace-native CLI workflow helpers, not a third-party Zapier-style GUI or a generic MCP Gmail-only bridge.
Common Questions / FAQ
Who is gws-workflow for?
Solo builders and small teams who use Google Workspace daily and want Claude or Codex to run standup reports, meeting prep, weekly digests, email-to-task, and Drive file announcements via the `gws` CLI.
When should I use gws-workflow?
Use it during Operate for recurring rituals (standup, weekly digest), during Build when wiring agent integrations against Workspace APIs, and during Grow when you need lifecycle signals from calendar and inbox counts—always after loading gws-shared auth rules.
Is gws-workflow safe to install?
It drives real Workspace APIs with your credentials; review the Security Audits panel on this Prism page and follow gws-shared guidance before bulk or destructive operations.
SKILL.md
READMESKILL.md - Gws Workflow
# workflow (v1) > **PREREQUISITE:** Read `../gws-shared/SKILL.md` for auth, global flags, and security rules. If missing, run `gws generate-skills` to create it. ```bash gws workflow <resource> <method> [flags] ``` ## Helper Commands | Command | Description | |---------|-------------| | [`+standup-report`](../gws-workflow-standup-report/SKILL.md) | Today's meetings + open tasks as a standup summary | | [`+meeting-prep`](../gws-workflow-meeting-prep/SKILL.md) | Prepare for your next meeting: agenda, attendees, and linked docs | | [`+email-to-task`](../gws-workflow-email-to-task/SKILL.md) | Convert a Gmail message into a Google Tasks entry | | [`+weekly-digest`](../gws-workflow-weekly-digest/SKILL.md) | Weekly summary: this week's meetings + unread email count | | [`+file-announce`](../gws-workflow-file-announce/SKILL.md) | Announce a Drive file in a Chat space | ## Discovering Commands Before calling any API method, inspect it: ```bash # Browse resources and methods gws workflow --help # Inspect a method's required params, types, and defaults gws schema workflow.<resource>.<method> ``` Use `gws schema` output to build your `--params` and `--json` flags.