gws-calendar
Google Calendar: Manage calendars and 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 too minimal to effectively guide skill selection. It lacks specific actions, explicit trigger conditions, and natural user language variations. The 'Google Calendar' prefix helps with distinctiveness but the rest is too vague to be useful among many skills.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions Google Calendar, gcal, scheduling meetings, checking availability, or creating calendar events'
List specific concrete actions such as 'Create, update, and delete calendar events, check availability, send meeting invites, set reminders'
Include natural language variations users might say: 'schedule', 'meeting', 'appointment', 'book time', 'free/busy', 'gcal'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Manage calendars and events' which is vague and abstract. It doesn't list concrete actions like 'create events', 'check availability', 'schedule meetings', or 'set reminders'. | 1 / 3 |
Completeness | The description weakly addresses 'what' (manage calendars/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 | Contains 'Google Calendar', 'calendars', and 'events' which are relevant keywords, but misses common variations users might say like 'schedule', 'meeting', 'appointment', 'availability', 'book time', or 'gcal'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Calendar' provides some specificity to distinguish from generic calendar skills, but 'manage calendars and events' is generic enough to potentially conflict with other calendar or scheduling tools. | 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 for the Google Calendar CLI. Its main weakness is the lack of concrete, executable examples showing actual API calls with parameters, and missing validation guidance for destructive operations like calendar clearing.
Suggestions
Add 2-3 concrete executable examples showing common operations (e.g., listing events, creating an event with specific params)
Add a warning or validation checkpoint for destructive operations like 'calendars.clear' that deletes all events
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information. It assumes Claude knows how to use CLI tools and doesn't explain basic concepts like what calendars or APIs are. | 3 / 3 |
Actionability | Provides concrete CLI syntax and discovery commands, but lacks executable examples showing actual usage with real parameters. The API resource list describes methods but doesn't show how to call them with specific flags/params. | 2 / 3 |
Workflow Clarity | The 'Discovering Commands' section provides a workflow for exploring the API, but there's no validation or error handling guidance. For operations like 'calendars.clear' (destructive), there are no checkpoints or confirmation steps mentioned. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear references to prerequisite shared skill, helper command skills via links, and the schema discovery pattern. One-level-deep references are well-signaled and organized. | 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.