Google Calendar: Show upcoming events across all calendars.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill gws-calendar-agenda76
Quality
66%
Does it follow best practices?
Impact
100%
1.63xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-calendar-agenda/SKILL.mdDiscovery
32%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 identifies a clear domain (Google Calendar) but is too narrow in scope, mentioning only one capability (showing events). It critically lacks explicit trigger guidance ('Use when...') and misses natural user phrases like 'schedule', 'meetings', or 'what's on my calendar' that would help Claude select this skill appropriately.
Suggestions
Add a 'Use when...' clause with trigger terms like 'check my calendar', 'what meetings do I have', 'schedule', 'appointments', 'agenda'
Expand the capability list to include other actions if supported (e.g., 'create events', 'check availability', 'find free time')
Include natural user phrases and variations like 'gcal', 'my schedule', 'what's coming up'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Calendar) and one action (show upcoming events), but lacks comprehensive actions like creating events, modifying events, or managing calendars. | 2 / 3 |
Completeness | Describes what it does (show upcoming 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 | Includes 'Google Calendar' and 'upcoming events' which are natural terms, but misses common variations like 'schedule', 'appointments', 'meetings', 'what's on my calendar', or 'agenda'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Calendar' is specific enough to distinguish from generic document or code skills, but could overlap with other calendar-related skills or scheduling tools without clearer trigger boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that exemplifies good documentation practices. It's concise, provides actionable examples, and appropriately references shared documentation for auth and related commands. The read-only nature is clearly communicated, and the flag table provides all necessary details without verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and efficient with no unnecessary explanations. Every section serves a purpose - usage, flags, examples, and tips are all essential information without padding. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands with multiple practical examples showing different flag combinations. The flag table gives specific details needed for execution. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose read-only command. The workflow is unambiguous - run the command with optional flags. No multi-step process or validation needed since it's read-only. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear overview, well-organized sections, and one-level-deep references to related skills (gws-shared for auth, gws-calendar for related commands). Prerequisite is clearly signaled at the top. | 3 / 3 |
Total | 12 / 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 | |
Table of Contents
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.