gws-workflow
by googleworkspacegws-workflow is a Google Workspace automation layer for the gws CLI. Use it to build repeatable cross-service workflows for meeting prep, standup summaries, email-to-task conversion, and Drive-to-Chat announcements. Install it with the shared auth layer and use schema discovery before execution.
This skill scores 68/100, which means it is list-worthy but best presented with caution: it gives agents a real command surface for Google Workspace workflows, but directory users will still need to inspect schemas and follow linked prerequisite instructions to use it confidently. For install decisions, it looks useful for workflow-oriented automation, though not yet fully self-contained.
- Defines a concrete trigger and invocation pattern: `gws workflow <resource> <method> [flags]` plus `gws workflow --help` and `gws schema` for discovery.
- Provides several real workflow entry points through helper commands like standup reports, meeting prep, email-to-task, weekly digest, and file announcements.
- Includes repository-linked guidance and prerequisite/security direction via the shared skill reference, improving agent execution compared with a generic prompt.
- Operational clarity depends on external discovery: users must inspect `gws schema` to learn required params and flag shapes, so there is some guesswork at runtime.
- The skill has no install command, scripts, references, or support files in this repo slice, which limits turn-key adoption and examples for edge cases.
Overview of gws-workflow skill
What gws-workflow does
The gws-workflow skill is a Google Workspace automation layer for the gws CLI. It helps you run cross-service workflows such as meeting prep, standup summaries, email-to-task conversion, and Drive-to-Chat announcements without guessing at raw API shapes first.
Who should install it
Install gws-workflow if you already use gws and want repeatable operational workflows instead of one-off prompts. It is a good fit for agents that need to stitch together Gmail, Calendar, Tasks, Drive, and Chat into a single outcome.
Why it is different
The main value of the gws-workflow skill is guidance on discovering commands and shaping inputs correctly before execution. That matters because workflow failures usually come from missing params, wrong resource-method pairs, or skipping the schema step rather than from the core task itself.
How to Use gws-workflow skill
Install and prerequisite setup
For gws-workflow install, use the CLI skill install flow and make sure the shared auth layer is present first. The skill explicitly depends on ../gws-shared/SKILL.md; if it is missing, run gws generate-skills so auth, global flags, and security rules are available before you attempt workflow calls.
Start by inspecting commands
The fastest gws-workflow usage pattern is: read SKILL.md, run gws workflow --help, then inspect the target method with gws schema workflow.<resource>.<method>. This is the safest way to discover required params, types, and defaults before building --params or --json.
Turn a rough goal into a usable prompt
A weak request like “prepare my meeting” is easier for the skill to execute if you specify the resource, desired output, and constraints: “Use gws workflow calendar.events list and related methods to prepare a meeting brief for tomorrow’s 1:1, including attendees, agenda context, and linked docs.” The more concrete your goal, the less likely the agent is to pick the wrong helper command.
Read these files first
Start with SKILL.md, then follow the linked helper commands under skills/gws-workflow-* when your task matches one of the bundled workflows. In practice, that means reading the helper skill closest to your job-to-be-done before trying to generalize from the top-level guide.
gws-workflow skill FAQ
Is gws-workflow only for advanced users?
No. The skill is useful even if you are not fluent in Google Workspace APIs, because it tells you how to discover commands and inspect schemas instead of assuming field names. Beginners benefit most when they follow the schema step rather than trying to improvise parameters.
When should I not use gws-workflow?
Do not use it if you just need a plain-language summary or a manual one-off response with no real Workspace action behind it. If your task does not require executing gws commands, the skill is unnecessary overhead.
How is it different from a generic prompt?
A generic prompt can describe the outcome, but gws-workflow is built around executable workflow discovery. It is better when you need a reproducible gws workflow call, especially across multiple Google services where the right method and flags matter.
Does it fit broader gws-workflow for Workflow Automation use cases?
Yes, but only when the automation is grounded in supported gws resources and methods. If your workflow requires custom business logic outside Google Workspace APIs, you will still need external scripting or orchestration.
How to Improve gws-workflow skill
Provide the exact workflow target
The best gws-workflow results come from naming the service, resource, and desired outcome up front: “Calendar event lookup for tomorrow’s client call” is much better than “help with calendar.” This narrows the command search space and improves the chance that the first output is usable.
Include the output shape you need
Say whether you want a summary, a task, a draft message, or a structured command invocation. For example, “return a standup summary with meetings, open tasks, and blockers” gives the helper a clearer target than “analyze my day.”
Verify schema before execution
A common failure mode is assuming a method accepts the same fields as another Google API. Use gws schema workflow.<resource>.<method> every time the input shape is unclear, especially for --params and --json; this reduces retries and prevents silent mismatches.
Iterate from helper workflows, not from scratch
If the first attempt is too broad, switch to the nearest helper command such as +meeting-prep or +email-to-task and refine from there. Those paths are usually better than inventing a new prompt because they encode the workflow intent more directly.