gws-events-subscribe

Google Workspace Events: Subscribe to Workspace events and stream them as NDJSON.

Quality

56%

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-events-subscribe/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 identifies a clear and distinctive niche (Google Workspace event subscriptions streamed as NDJSON), which minimizes conflict risk. However, it lacks a 'Use when...' clause, limiting Claude's ability to know when to select it, and the capability description is thin without enumerating specific event types or use cases.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to monitor Google Workspace changes, subscribe to Drive/Calendar/Gmail events, or set up event streaming.'

Include natural trigger terms users might say, such as 'Google Drive changes', 'Calendar notifications', 'Gmail events', 'webhook', or 'real-time updates'.

Expand the capability list with specific actions like 'create subscriptions for Drive, Calendar, or Chat events, manage existing subscriptions, and parse incoming event payloads'.

Dimension	Reasoning	Score
Specificity	Names the domain (Google Workspace Events) and two actions (subscribe to events, stream as NDJSON), but doesn't elaborate on specific event types, filtering, or other concrete capabilities.	2 / 3
Completeness	Describes what the skill does (subscribe and stream events) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also thin, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'Google Workspace', 'events', 'subscribe', and 'NDJSON', but misses common user variations such as 'Google Docs notifications', 'Drive changes', 'webhook', 'event stream', or specific Workspace app names users might mention.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Google Workspace Events', 'subscribe', and 'NDJSON' is highly specific and unlikely to conflict with other skills. This is a clear, narrow niche.	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.

A well-structured, concise CLI skill reference that efficiently documents the subscribe command with good progressive disclosure to related skills. Its main weaknesses are the lack of explicit required flags or minimum viable usage guidance, and missing validation/error-handling steps for an operation that creates cloud resources.

Suggestions

Clarify which flags are required for a minimal invocation (e.g., --target + --event-types + --project seem necessary when not using --subscription) and mark them in the table.

Add a brief example of the NDJSON output format so Claude knows what to expect and can parse/validate results.

Add an error-handling or verification step (e.g., 'If subscription creation fails, check project permissions and ensure the Workspace Events API is enabled').

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. No unnecessary explanations of what Workspace events or Pub/Sub are—it assumes Claude knows these concepts. Every section serves a clear purpose: usage, flags, examples, tips.	3 / 3
Actionability	The examples show concrete CLI invocations which are copy-paste ready, but the skill lacks detail on what happens under the hood (e.g., how Pub/Sub topic/subscription are auto-created, what the NDJSON output looks like). The flag table marks nothing as required, leaving ambiguity about minimum viable invocations.	2 / 3
Workflow Clarity	This is a command that creates Pub/Sub resources (a write/destructive operation), yet there's no explicit workflow for verifying subscription creation succeeded, handling errors, or confirming cleanup. The caution box is good but the lack of a validation/verification step caps this at 2.	2 / 3
Progressive Disclosure	The skill is appropriately scoped as a single-command reference, with clear one-level-deep references to the shared skill for auth/global flags and to the parent events skill. Content is well-organized with distinct sections.	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.