gws-calendar

Google Calendar: Manage calendars and events.

Quality

40%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/gws-calendar/SKILL.md

Quality

Content

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 API reference catalog for Google Calendar via the gws CLI, with good progressive disclosure through helper command links and prerequisite references. However, it lacks concrete usage examples with actual flag values, and the verbose API method descriptions add bulk without proportional value. The absence of safety warnings for destructive operations (especially calendars.clear) is a notable gap.

Suggestions

Add 2-3 concrete executable examples showing common operations (e.g., listing events, patching an event) with actual --params/--json flag usage

Add explicit warnings or confirmation guidance before destructive operations like 'calendars.clear' and 'calendars.delete'

Trim API method descriptions to just the method name and any non-obvious behavior (e.g., remove descriptions like 'Deletes an event' which are self-evident)

Dimension	Reasoning	Score
Conciseness	The API resource listings are comprehensive but include verbose descriptions that Claude likely doesn't need (e.g., explaining what 'delete' does for ACL rules, or the note about service accounts for calendar insertion). Some descriptions could be trimmed significantly.	2 / 3
Actionability	Provides the CLI pattern and schema discovery commands, but lacks concrete executable examples of actual API calls (e.g., how to list events, create a calendar, or patch an event with specific --params/--json flags). The helper command references are useful but the main content is more of a reference catalog than actionable guidance.	2 / 3
Workflow Clarity	The 'Discovering Commands' section provides a two-step discovery 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 should cap this at 2.	2 / 3
Progressive Disclosure	Well-structured with clear navigation: references the shared skill for prerequisites, links to helper commands (insert, agenda) in separate files, and organizes API resources by category. The 'Discovering Commands' section appropriately teaches self-service exploration rather than inlining all details.	3 / 3
	Total	9 / 12 Passed

Description

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. It names the domain (Google Calendar) but fails to enumerate specific capabilities and entirely lacks a 'Use when...' clause. The description would benefit significantly from listing concrete actions and adding explicit trigger terms.

Suggestions

Add specific concrete actions such as 'Create, update, and delete calendar events, check availability, manage invitations, and list upcoming schedules.'

Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks about scheduling, meetings, appointments, availability, gcal, or Google Calendar events.'

Include common user-facing synonyms and variations such as 'schedule', 'meeting', 'appointment', 'invite', 'gcal', and 'free/busy' to improve trigger term coverage.

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, etc.	1 / 3
Completeness	The 'what' is very weak ('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 it down 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 'gcal'.	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 skills.	2 / 3
	Total	6 / 12 Passed

Validation

90%

Warnings & errors only

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: a3768d0

Reviewed: 3 months ago

Table of Contents

Discovery Implementation Validation

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.