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 action 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', 'webhook', 'Google Drive notifications', 'Calendar updates', 'Workspace push notifications'.
List specific concrete actions such as 'Create push notification channels for Google Drive, Calendar, and Gmail events; manage subscription lifecycles; handle webhook callbacks'.
Include natural user-facing keywords and file/service names users might mention, e.g., 'Google Calendar', 'Google Drive', 'Gmail', 'real-time notifications', 'event subscriptions'.
| 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 outcomes are produced. | 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 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.
The skill serves as a reasonable reference/index for the Google Workspace events API with good progressive disclosure and navigation to related skills. However, it lacks concrete usage examples and any workflow guidance for common tasks like creating a subscription and handling its lifecycle. The API descriptions are somewhat verbose, copying documentation text that doesn't add actionable value.
Suggestions
Add at least one concrete end-to-end example showing how to create a subscription with specific --params/--json flags
Add a workflow section with sequenced steps for common tasks (e.g., create subscription → verify with get → handle errors → renew when needed)
Trim the API resource descriptions to just the method name and a brief phrase, removing the 'To learn how to use this method, see [link]' boilerplate that Claude doesn't need
| 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 schema discovery commands, but lacks concrete executable examples of actual subscription creation or event streaming. The API resource listing describes methods but doesn't show how to invoke them with specific flags/params. | 2 / 3 |
Workflow Clarity | There is no clear workflow for subscribing to events — no sequenced steps, no validation checkpoints, no error handling guidance. For a task like creating and managing subscriptions (which involves create, monitor, renew, reactivate), the absence of any workflow sequence is a significant gap. | 1 / 3 |
Progressive Disclosure | Well-structured with clear references to prerequisite shared skill, helper commands linking to separate skill files for subscribe and renew, and a discovery section. 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 | |
a3768d0
Table of Contents
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.