gws-events
Subscribe to Google Workspace events.
55
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
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 severely underdeveloped, providing only a minimal action statement without explaining capabilities, use cases, or trigger conditions. It fails to help Claude understand when to select this skill over others and lacks the detail needed for effective skill selection from a large pool.
Suggestions
Add specific capabilities: list what types of events can be subscribed to (e.g., 'calendar changes, Drive file updates, Gmail notifications') and what actions the skill performs
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when the user wants to monitor changes in Google Drive, receive calendar updates, or set up webhooks for Workspace apps'
Include natural trigger terms users would say: 'watch files', 'notifications', 'alerts', 'webhooks', 'monitor changes', and specific app names like 'Gmail', 'Drive', 'Calendar'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names a single vague action 'Subscribe to' without explaining what subscribing entails, what events are available, or what outcomes result. No concrete actions are listed. | 1 / 3 |
Completeness | Only partially addresses 'what' (subscribe to events) with no detail, and completely missing 'when' guidance. No 'Use when...' clause or trigger scenarios are provided. | 1 / 3 |
Trigger Term Quality | Contains 'Google Workspace' and 'events' which are relevant domain terms, but lacks natural variations users might say like 'calendar notifications', 'Gmail alerts', 'webhook', 'watch', or specific Workspace apps. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Workspace events' provides some specificity to the Google ecosystem, but 'events' is generic and could overlap with calendar skills, notification skills, or other Google-related integrations. | 2 / 3 |
Total | 6 / 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 skill is well-organized and concise, serving as an effective reference/overview for the events API. However, it lacks concrete executable examples showing actual subscription creation or event handling, making it more of a reference document than an actionable guide. The progressive disclosure is excellent with clear links to related skills.
Suggestions
Add a concrete example showing how to create a subscription with actual --params values (e.g., `gws events subscriptions create --params '{...}'`)
Include a brief workflow example for a common task like 'subscribe to calendar events' with the complete command sequence
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary information without explaining concepts Claude already knows. No verbose explanations of what events or subscriptions are. | 3 / 3 |
Actionability | Provides command structure and schema inspection commands, but lacks concrete executable examples showing actual usage with real parameters. The API resource descriptions are informational rather than instructional. | 2 / 3 |
Workflow Clarity | The 'Discovering Commands' section provides a basic workflow for exploring APIs, but there's no clear multi-step workflow for common tasks like creating a subscription with validation checkpoints. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear references to prerequisite shared skill, helper commands linking to separate skill files, and organized sections. Navigation is straightforward with one-level-deep references. | 3 / 3 |
Total | 10 / 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.