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 with NDJSON streaming), which makes it unlikely to conflict with other skills. However, it lacks an explicit 'Use when...' clause and could benefit from more specific capability details and natural trigger terms that users would actually say.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to listen for changes in Google Workspace apps like Drive, Calendar, or Gmail, or needs real-time event notifications.'

Include more natural trigger terms and variations users might say, such as 'Google Drive changes', 'Calendar updates', 'Gmail notifications', 'webhook', 'real-time updates', or specific Workspace app names.

Expand the capability list with more concrete actions, e.g., 'Create and manage event subscriptions, filter by resource type, handle subscription lifecycle (renewal, deletion), and stream events as NDJSON.'

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 beyond the high-level actions.	2 / 3
Completeness	Describes what the skill does (subscribe to Workspace events and stream them as NDJSON) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also fairly thin, bringing this closer to 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'Google Workspace', 'events', 'subscribe', 'NDJSON', and 'stream', but misses common variations users might say such as 'Google Docs notifications', 'Drive changes', 'webhook', 'event listener', or specific Workspace app names.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Google Workspace Events', 'subscribe', and 'NDJSON streaming' is highly specific and unlikely to conflict with other skills. This occupies a clear 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.

This is a well-structured CLI reference skill that is concise and properly organized with good cross-references. Its main weaknesses are ambiguity around which flags are required vs optional (the Required column shows '—' for all flags) and the lack of validation/error-handling guidance for an operation that creates persistent cloud resources.

Suggestions

Clarify which flags are required vs optional — currently all flags show '—' in the Required column, making it unclear what's needed for a minimal working invocation.

Add a brief workflow or validation step for confirming Pub/Sub resource creation succeeded, especially since --cleanup is optional and resources persist by default.

Show example output (even a brief NDJSON snippet) so Claude knows what to expect and can validate the command worked.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It documents flags in a clean table, provides concise examples, and doesn't explain concepts Claude already knows like what Pub/Sub is or how NDJSON works.	3 / 3
Actionability	The examples show concrete CLI invocations which is good, but there's no executable code or detailed output format shown. The flag table lists options but several have no default and no required marker (just '—'), making it unclear which flags are truly required for a working command.	2 / 3
Workflow Clarity	The skill involves creating Pub/Sub resources (a potentially destructive/persistent operation) but lacks explicit workflow steps for setup, validation, and teardown. The caution about write commands is present, but there's no feedback loop for verifying subscription creation succeeded or handling errors.	2 / 3
Progressive Disclosure	The skill appropriately references the shared skill for auth/global flags and links to related commands. Content is well-structured with clear sections and one-level-deep references via 'See Also'.	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 8 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.