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 list of alternatives.

Suggestions

List specific concrete actions the skill performs, e.g., 'Creates Google Calendar events from Gmail emails, syncs Google Sheets data to Google Docs templates, 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 wants to connect or automate tasks across multiple Google services, mentions Google automation, or asks to sync data between Gmail, Sheets, Calendar, or Drive.'

Specify which Google services are involved (Gmail, Sheets, Docs, Calendar, Drive, etc.) to make the skill distinctive and reduce conflict risk with individual Google service 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. Terms like 'cross-service' and 'productivity workflows' are abstract jargon, not things users naturally request.	1 / 3
Distinctiveness Conflict Risk	'Cross-service productivity workflows' is so generic it could overlap with virtually any Google-related skill or any productivity/workflow automation skill. There are no distinct triggers to differentiate it.	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 skill is well-structured as a hub/index page, with excellent conciseness and progressive disclosure to sub-skills. However, it lacks concrete executable examples of running workflow commands and doesn't demonstrate how the cross-service workflows actually compose, which limits its actionability and workflow clarity.

Suggestions

Add at least one complete executable example showing a workflow command with `--params`/`--json` flags (e.g., `gws workflow calendar list --params '{"timeMin": "..."}'`) to improve actionability.

Include a brief sequenced example showing how helper commands compose for a cross-service workflow (e.g., 'To prepare for standup: 1. Run +standup-report, 2. Review output, 3. Share via +file-announce') to improve workflow clarity.

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, 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 actually running a workflow command with `--params` or `--json` flags. The skill tells you how to discover but doesn't show a complete end-to-end example.	2 / 3
Workflow Clarity	There's a clear two-step discovery pattern (browse then inspect), but no explicit workflow sequence for executing cross-service operations. For a skill titled 'Cross-service productivity workflows,' the lack of a sequenced multi-step workflow with validation checkpoints is a gap. The helper commands are listed but there's no guidance on how they compose together.	2 / 3
Progressive Disclosure	Excellent progressive disclosure: concise overview with well-signaled one-level-deep references to five helper command skills and a shared prerequisite skill. Navigation is clear via the table format and explicit links.	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: a3768d0

Reviewed: about 1 month 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.