gws-gmail-watch

Gmail: Watch for new emails and stream them as NDJSON.

Quality

56%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

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

Quality

Discovery

40%

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

The description is concise and identifies a clear, distinctive niche (Gmail email watching with NDJSON streaming), but it lacks an explicit 'Use when...' clause and misses common natural language trigger terms users might employ. The technical term 'NDJSON' may not match how users naturally describe their needs.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to monitor a Gmail inbox, watch for incoming emails, or stream email data.'

Include more natural trigger terms users would say, such as 'inbox', 'email notifications', 'monitor emails', 'incoming mail', or 'email feed'.

Consider briefly explaining NDJSON or adding a natural-language equivalent like 'stream them as newline-delimited JSON records' to improve clarity for non-technical contexts.

Dimension	Reasoning	Score
Specificity	Names the domain (Gmail) and two specific actions (watch for new emails, stream as NDJSON), but the scope is narrow and doesn't list multiple concrete capabilities beyond these two.	2 / 3
Completeness	Describes what it does (watch for new emails and stream as NDJSON) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'when' is entirely missing, not just implied, bringing it to 1.	1 / 3
Trigger Term Quality	Includes 'Gmail', 'new emails', and 'NDJSON' as keywords. However, it misses common user variations like 'inbox', 'email notifications', 'email monitoring', 'email stream', or 'watch inbox'. 'NDJSON' is fairly technical jargon most users wouldn't naturally say.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Gmail', 'watch for new emails', and 'NDJSON streaming' creates a very specific niche that is unlikely to conflict with other skills. The Gmail + streaming + NDJSON combination is highly distinctive.	3 / 3
	Total	8 / 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 CLI reference skill with good progressive disclosure and cross-references. Its main weaknesses are the lack of workflow sequencing for the setup process (especially around Pub/Sub resource creation and permission granting) and missing details about output format and error handling. For a command that involves infrastructure setup and streaming, more explicit validation steps would strengthen it.

Suggestions

Add a brief workflow sequence showing the setup flow: verify GCP project → create/verify Pub/Sub resources → start watch → consume output, with validation checkpoints (e.g., how to verify the watch was established).

Include a sample of the NDJSON output format so Claude knows what to expect and can help users parse or process the streamed messages.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. Every section serves a purpose — flags table, examples, tips — with no unnecessary explanation of what Gmail or Pub/Sub is. Assumes Claude's competence throughout.	3 / 3
Actionability	Provides concrete CLI examples and a clear flags table, but lacks detail on what the NDJSON output looks like, how to handle errors, or what happens during the setup flow. The examples are copy-paste ready commands but the overall workflow of setting up and consuming the watch stream is underspecified.	2 / 3
Workflow Clarity	The skill describes flags and examples but doesn't clearly sequence the multi-step process (e.g., ensuring GCP project setup, granting permissions, starting the watch, consuming output). There are no validation checkpoints — for instance, no guidance on verifying Pub/Sub resources were created correctly or that the watch was established successfully.	2 / 3
Progressive Disclosure	Clear prerequisite reference to shared skill, well-organized sections (Usage, Flags, Examples, Tips, See Also), and appropriate one-level-deep cross-references to related skills. Content is appropriately scoped for this single command.	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.