gws-calendar

View, create, update, and delete Google Calendar events across all connected accounts. Find free time for meetings.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./apps/desktop/bundled-skills/gws-calendar/SKILL.md

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean, actionable, and well-organized, with concrete tool invocations and dense reference tables. The only gap is missing explicit verification/validation steps around destructive operations (delete, rsvp), which caps workflow clarity at 2.

Suggestions

Add a verification step to destructive operations (e.g., confirm the event via 'get <eventId>' after delete, or show the RSVP status after 'rsvp') to close the validation gap.

Include an explicit confirmation prompt before 'delete' (e.g., read back event title/time and confirm with the user) since deletion is irreversible.

Optionally split the detailed flags table into a reference file if the skill grows, keeping SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	Dense, reference-efficient tables for subcommands and flags with no padding or explanation of concepts Claude already knows; the lone overview sentence earns its place as context, matching the lean-and-efficient anchor.	3 / 3
Actionability	Provides copy-paste-ready, fully-specified tool calls (e.g., 'google_calendar(command: "create --title ... --start ... --end ... --attendees ...", account: "Work")') plus a concrete flags table and explicit RSVP values, matching the fully-executable anchor.	3 / 3
Workflow Clarity	The scheduling workflow is clearly sequenced with a user-confirmation checkpoint, but destructive operations (delete, rsvp) lack explicit validation/verification steps, which per the rubric caps workflow clarity at 2.	2 / 3
Progressive Disclosure	No external references are needed for this single-MCP-tool skill, and the body is well-organized into clearly headed sections (Overview, Subcommands, Account Routing, Flags, Workflow, Error Handling) with easy navigation and no nested references.	3 / 3
	Total	11 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and well-scoped to Google Calendar, with concrete CRUD and free-time actions. Its main weakness is the absence of an explicit 'Use when...' trigger clause and limited natural keyword coverage, which cap completeness and trigger-term quality at 2.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when scheduling, viewing, or managing Google Calendar events or finding free meeting time across connected accounts.').

Expand trigger-term coverage with natural phrasings users say ('schedule a meeting', 'book an appointment', 'check the calendar', 'send an invite').

Mention common entry points like recurring events, reminders, or multi-account selection to sharpen distinctiveness from generic scheduling skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('View, create, update, and delete Google Calendar events', 'Find free time for meetings'), matching the anchor for listing several specific actions rather than naming only some.	3 / 3
Completeness	Clearly states the 'what' but provides no 'Use when...' trigger clause or equivalent explicit 'when to use' guidance, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	Includes natural terms ('Google Calendar events', 'free time', 'meetings') but omits common variations users would say ('schedule', 'appointment', 'book', 'invite'), so it only partially covers natural phrasing.	2 / 3
Distinctiveness Conflict Risk	Scoped specifically to 'Google Calendar events across all connected accounts', a clear niche with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: accomplish-ai/coworker
Path: apps/desktop/bundled-skills/gws-calendar/SKILL.md
Commit: 2cf74d0

Reviewed: 1 day 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.