gws-calendar
Google Calendar: Manage calendars and events.
51
40%
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-calendar/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 vague to effectively guide skill selection. While 'Google Calendar' provides some distinctiveness as a product name, the description lacks specific actions, natural trigger terms users would say, and any explicit 'Use when...' guidance. It would benefit significantly from listing concrete capabilities and trigger scenarios.
Suggestions
List specific concrete actions such as 'Create, update, and delete calendar events, check availability, manage invitations, and set reminders.'
Add a 'Use when...' clause with trigger terms like 'Use when the user asks about scheduling, meetings, appointments, availability, calendar invites, or anything involving Google Calendar.'
Include common natural language variations users might say, such as 'schedule', 'meeting', 'appointment', 'free time', 'busy', 'invite', 'RSVP'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Manage calendars and events' which is extremely vague. It does not list any concrete actions like creating events, checking availability, deleting events, setting reminders, or handling recurring events. | 1 / 3 |
Completeness | The 'what' is only vaguely stated ('manage calendars and events') and there is no 'when' clause or explicit trigger guidance at all. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the weak 'what' brings this to 1. | 1 / 3 |
Trigger Term Quality | It includes 'Google Calendar', 'calendars', and 'events' which are relevant keywords users might say, but misses common variations like 'schedule', 'meeting', 'appointment', 'availability', 'invite', or 'reminder'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Calendar' is a specific product name which helps distinguish it from generic calendar or scheduling skills, but 'manage calendars and events' is broad enough that it could overlap with other calendar-related or scheduling skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill serves as a reasonable reference/index for the Google Calendar CLI tool with good progressive disclosure and organization. However, it's weakened by verbose API method descriptions that add little value, lack of concrete usage examples beyond discovery commands, and missing safety guidance for destructive operations like `calendars.clear`.
Suggestions
Add 2-3 concrete, copy-paste-ready examples of common operations (e.g., listing events, creating an event with --params/--json flags) to improve actionability.
Add a warning or confirmation guidance for destructive operations like `calendars.clear` and `calendars.delete` to improve workflow safety.
Trim the API resource descriptions to just method names (or very brief annotations only where non-obvious), since Claude can use `gws schema` for details — this would significantly improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The API resource listings are comprehensive but include verbose descriptions that Claude could infer from method names (e.g., 'delete — Deletes an access control rule'). The calendars.insert note about service accounts adds useful context, but many descriptions are redundant. Could be significantly tightened. | 2 / 3 |
Actionability | Provides concrete CLI commands for discovery (`gws calendar --help`, `gws schema`) and links to helper commands, but lacks executable examples of actual API calls (e.g., creating an event, listing calendars with specific flags). The skill tells you how to discover commands but doesn't show complete usage examples. | 2 / 3 |
Workflow Clarity | The 'Discovering Commands' section provides a two-step workflow (browse then inspect), but there's no validation or error handling guidance. For destructive operations like `calendars.clear` (which deletes all events on primary calendar), there are no warnings or confirmation steps, which is a significant gap. | 2 / 3 |
Progressive Disclosure | Well-structured with clear navigation: prerequisite reference to shared skill, helper command links to sub-skills, organized API resources by category, and a discovery section. References are one level deep and clearly signaled. | 3 / 3 |
Total | 9 / 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.