Gws Workflow

Google Workflow: Cross-service productivity workflows.

Security Scan

The skill's behavior generally matches a CLI wrapper for Google Workspace workflows, but it references an external shared SKILL.md for auth and security rules (not included) and does not declare any credentials, creating ambiguity about required secrets and scope.

Purpose & Capability

The skill is an instruction-only wrapper that calls a 'gws' CLI to run Google Workspace workflows; requiring the 'gws' binary is coherent with the described purpose. There are no unexpected binaries or unrelated installs declared.

Instruction Scope

SKILL.md stays focused on using the gws CLI and inspecting schemas. However it explicitly instructs the agent to 'Read ../gws-shared/SKILL.md for auth, global flags, and security rules' — that reference to a sibling/shared file outside this skill's directory creates scope ambiguity because the shared file likely contains authentication steps or secrets that are not visible here.

Install Mechanism

No install spec is provided (instruction-only), so nothing will be downloaded or written by the skill itself. This minimizes installation risk but transfers trust to the existing 'gws' binary on the host.

Credentials

The skill declares no required environment variables or credentials, yet delegates auth to a separate ../gws-shared/SKILL.md. That suggests required credentials or tokens exist but are not declared here. Absence of explicit credential requirements prevents a clear assessment of whether requested access would be proportionate.

Persistence & Privilege

The skill does not request always:true and is not declaring persistent or system-wide changes. It is user-invocable and can be called autonomously (platform default), which is expected.

What to consider before installing

This skill appears to be a thin wrapper that runs a 'gws' CLI to interact with Google Workspace, which is coherent — but before installing, do the following: 1) Inspect the referenced ../gws-shared/SKILL.md (or ask the author) to see what authentication method and credentials are required and where tokens are stored; the shared file may require OAuth tokens, service account keys, or environment variables that are not declared here. 2) Verify the origin and trustworthiness of the 'gws' binary on your system (is it an official Google tool or a third-party utility?). 3) Check the helper SKILL.md files linked from this skill for any additional credential or network access. 4) If you cannot inspect the shared auth file or confirm the gws binary origin, treat the skill as potentially unsafe because it may require access to sensitive Google Workspace data without making those requirements explicit.

workflow (v1)

PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to create it.

gws workflow <resource> <method> [flags]

Helper Commands

Command	Description
+standup-report	Today's meetings + open tasks as a standup summary
+meeting-prep	Prepare for your next meeting: agenda, attendees, and linked docs
+email-to-task	Convert a Gmail message into a Google Tasks entry
+weekly-digest	Weekly summary: this week's meetings + unread email count
+file-announce	Announce a Drive file in a Chat space

Discovering Commands

Before calling any API method, inspect it:

# 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.