gws-events-subscribe
Google Workspace Events: Subscribe to Workspace events and stream them as NDJSON.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill gws-events-subscribe68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 technical niche (Google Workspace event streaming) but suffers from missing trigger guidance and limited natural language keywords. While distinctive, it fails to help Claude understand when to select this skill and doesn't include terms users would naturally use when needing this functionality.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when user wants to monitor Google Workspace activity', 'track calendar changes', 'watch Gmail events', or 'set up workspace notifications'
Include natural language variations users might say: 'Google calendar updates', 'Gmail notifications', 'Docs changes', 'workspace activity monitoring', 'real-time Google updates'
Expand specific capabilities: what types of events can be subscribed to (Calendar, Gmail, Drive, etc.) and what users can do with the streamed data
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Workspace Events) and two actions (subscribe, stream as NDJSON), but lacks comprehensive detail about what types of events, what can be done with them, or additional capabilities. | 2 / 3 |
Completeness | Describes what it does (subscribe and stream events) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Google Workspace', 'events', and 'NDJSON' which are relevant but technical. Missing natural variations users might say like 'Google calendar notifications', 'Gmail events', 'workspace webhooks', or 'real-time updates'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Google Workspace, event subscriptions, and NDJSON streaming. Unlikely to conflict with other skills due to the unique combination of these technical elements. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
87%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-crafted skill that efficiently documents a CLI command with clear examples and comprehensive flag documentation. The main weakness is the lack of explicit workflow guidance for the setup process and error handling scenarios, which would be valuable given this involves creating cloud resources.
Suggestions
Add a brief workflow section showing the typical setup flow: create subscription → verify → stream events → cleanup, with validation checkpoints
Include common error scenarios and how to handle them (e.g., permission issues, invalid target URIs)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, presenting only essential information. No unnecessary explanations of what Pub/Sub is or how event subscriptions work—assumes Claude's competence. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready bash commands with clear flag documentation. Examples cover common use cases with specific syntax. | 3 / 3 |
Workflow Clarity | While the command usage is clear, there's no explicit workflow for the multi-step process of setting up subscriptions. Missing validation steps for verifying subscription creation or handling common errors. | 2 / 3 |
Progressive Disclosure | Appropriately structured with clear references to shared skills and related commands. Content is well-organized with quick start examples and detailed flag table, with one-level-deep references to related documentation. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Reviewed
Table of Contents
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.