gws-events
Subscribe to Google Workspace events.
46
33%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-events/SKILL.mdQuality
Discovery
22%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 too terse and lacks both concrete capability details and explicit trigger guidance. While it identifies a specific platform (Google Workspace), it fails to explain what subscribing involves, what event types are supported, or when Claude should select this skill. It would be easily overlooked or misapplied in a multi-skill environment.
Suggestions
Add a 'Use when...' clause with trigger terms like 'watch for changes', 'Google Workspace notifications', 'webhook', 'subscribe to calendar/drive/Gmail events'.
List specific concrete actions such as 'Create and manage push notification subscriptions for Google Drive, Calendar, and Gmail events using the Google Workspace Events API'.
Include common user-facing terms and file/service names (e.g., 'Google Drive changes', 'Calendar updates', 'Gmail notifications', 'push notifications') to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a single vague action ('Subscribe') in a specific domain ('Google Workspace events') but provides no concrete details about what subscribing entails, what types of events, or what operations are supported. | 1 / 3 |
Completeness | The 'what' is minimal (subscribe to events) and there is no 'when' clause at all. The absence of a 'Use when...' clause caps this at 2 per the rubric, but the 'what' is also very weak, so it scores a 1. | 1 / 3 |
Trigger Term Quality | It includes 'Google Workspace' and 'events' and 'subscribe' which are somewhat relevant keywords, but misses common variations like 'webhook', 'notifications', 'watch', 'calendar events', 'drive changes', or specific Workspace product names. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Workspace events' is somewhat specific and narrows the domain, but 'subscribe' is vague enough that it could overlap with other Google API or event/notification skills without clearer scoping. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
44%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill serves primarily as an API reference index for the Google Workspace events CLI, with good progressive disclosure to helper commands and shared docs. However, it lacks concrete usage examples and any workflow guidance for the core task of subscribing to events, making it more of a catalog than an actionable skill. The verbose API method descriptions could be trimmed significantly.
Suggestions
Add a concrete example showing a complete subscription creation command with actual --params values, e.g., `gws events subscriptions create --params '{...}'`
Include a basic workflow sequence: 1) discover schema, 2) create subscription, 3) verify with get/list, 4) handle errors/reactivate if needed
Trim the API method descriptions to just the method name and a brief phrase — remove the 'To learn how to use this method' boilerplate and lengthy explanations like the reactivate description
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some verbose descriptions copied from API docs (e.g., the full reactivate description). The subscription method descriptions could be trimmed since they mostly just say 'to learn how to use this method, see [link]'. | 2 / 3 |
Actionability | Provides the CLI syntax and a discovery workflow (`gws schema`), but lacks concrete executable examples of actual subscription creation or event streaming commands with real parameters. The content describes what methods exist rather than showing how to use them. | 2 / 3 |
Workflow Clarity | There is no clear workflow for subscribing to events — no sequenced steps, no validation checkpoints. For a skill about subscribing to Workspace events (which involves creating subscriptions, handling errors, reactivating), the absence of any multi-step process guidance is a significant gap. | 1 / 3 |
Progressive Disclosure | Well-structured with clear references to helper commands (subscribe, renew) in separate skill files, a prerequisite reference to shared auth docs, and a clean table-based organization. Navigation is one level deep and clearly signaled. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
90%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
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.