gws-workflow

Google Workflow: Cross-service productivity workflows.

Quality

36%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/gws-workflow/SKILL.md

Quality

Discovery

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is critically underspecified. It provides no concrete actions, no trigger terms, and no guidance on when Claude should select this skill. It would be nearly impossible for Claude to reliably choose this skill from a pool of alternatives.

Suggestions

List specific concrete actions the skill performs, e.g., 'Creates Google Calendar events from Gmail threads, syncs Google Sheets data to Google Docs, automates cross-service tasks between Google Drive, Gmail, Calendar, and Sheets.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about automating tasks across Google services, syncing data between Google apps, or creating workflows involving Gmail, Sheets, Calendar, or Drive.'

Specify which Google services are covered to improve distinctiveness and reduce conflict risk with other Google-specific skills.

Dimension	Reasoning	Score
Specificity	The description says 'Cross-service productivity workflows' which is extremely vague. No concrete actions are listed—there's no mention of what specific tasks or operations this skill performs.	1 / 3
Completeness	The 'what' is extremely vague ('cross-service productivity workflows') and there is no 'when' clause at all. Neither question is meaningfully answered.	1 / 3
Trigger Term Quality	'Google Workflow' in the title provides some keyword value, but the description itself contains no natural trigger terms a user would say. 'Cross-service productivity workflows' is abstract jargon, not something a user would type.	1 / 3
Distinctiveness Conflict Risk	'Cross-service productivity workflows' is so generic it could overlap with virtually any productivity or automation skill. There are no distinct triggers to differentiate it from other Google-related or workflow-related skills.	1 / 3
	Total	4 / 12 Passed

Implementation

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured, concise hub skill that effectively organizes cross-service workflow commands with clear navigation to sub-skills. Its main weakness is the lack of concrete, executable examples showing actual workflow invocations with real parameters, and the absence of explicit multi-step workflow sequencing with validation for what is inherently a multi-step, cross-service task.

Suggestions

Add at least one complete, executable example showing a full `gws workflow <resource> <method> --params '{...}'` invocation with realistic parameters to improve actionability.

Include a brief explicit workflow sequence (e.g., 1. Discover → 2. Inspect schema → 3. Execute → 4. Verify output) with a validation/verification step to improve workflow clarity for cross-service operations.

Dimension	Reasoning	Score
Conciseness	Very lean content. No unnecessary explanations—assumes Claude knows what workflows, APIs, and CLI tools are. Every line serves a purpose: prerequisite, syntax, helper commands table, and discovery commands.	3 / 3
Actionability	Provides concrete CLI commands for discovery (`gws workflow --help`, `gws schema`) and links to helper command skills, but lacks executable examples of actual workflow invocations. There's no example showing a complete `gws workflow <resource> <method> --params ...` call with real parameters.	2 / 3
Workflow Clarity	The discovery flow (browse → inspect → build params) is present but implicit rather than explicitly sequenced. There are no validation checkpoints or error-handling guidance for multi-step cross-service workflows, which is the skill's stated purpose.	2 / 3
Progressive Disclosure	Excellent progressive disclosure: concise overview with a well-organized table linking to five separate helper command skills, plus a clear prerequisite reference to shared auth/security. All references are one level deep and clearly signaled.	3 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	10 / 11 Passed

Repository: googleworkspace/cli
Commit: c7c6646

Reviewed: about 7 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.