Create, update, and organize Google Calendar events and schedules. Check availability, book time, and manage calendars. Use when asked to schedule a meeting, set up an appointment, book a call, check gcal, or manage calendar events.
94
94%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
100%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 is a strong skill description that covers all key dimensions well. It provides specific capabilities, includes natural trigger terms users would actually say (including the colloquial 'gcal'), and has an explicit 'Use when...' clause with diverse trigger scenarios. The description is concise, uses third person voice correctly, and is clearly distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create, update, and organize Google Calendar events and schedules', 'Check availability, book time, and manage calendars'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (create, update, organize events; check availability; book time; manage calendars) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user terms: 'schedule a meeting', 'set up an appointment', 'book a call', 'check gcal', 'manage calendar events'. These are phrases users would naturally say, including the informal 'gcal' abbreviation. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Google Calendar specifically, with distinct triggers like 'gcal', 'calendar events', 'book a call', and 'schedule a meeting'. Unlikely to conflict with other skills due to the specific Google Calendar domain. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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-structured skill with excellent actionability and progressive disclosure. The commands are concrete and copy-paste ready, error handling guidance is clear and specific, and detailed content is appropriately delegated to reference files. Minor verbosity in setup verification and troubleshooting sections prevents a top conciseness score, but overall the skill is effective and well-organized.
Suggestions
Trim the 'Setup Verification' section — the bullet list of what 'check' verifies is unnecessary since the command itself reports issues. A single line like 'Run `check` to verify dependencies, auth, and API connectivity' suffices.
Remove or condense the 'Model Guidance' and 'Troubleshooting' sections — the model guidance is not actionable for Claude, and the troubleshooting tips (verify event ID, use RFC3339) are already covered elsewhere in the document.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary sections like 'Setup Verification' that repeats what 'check' does, the 'Model Guidance' section adds little value, and the troubleshooting section explains fairly obvious things. The dependency check list is redundant given the check command exists. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready commands throughout. Every example includes complete CLI invocations with realistic arguments, time formats, and flags. The script usage section serves as a comprehensive quick reference. | 3 / 3 |
Workflow Clarity | Clear sequencing from installation → setup verification → authentication → usage. Error handling section explicitly distinguishes retryable vs non-retryable errors with specific guidance. The declined events guidance includes a clear feedback loop (inform user, offer to re-run with flag). Authentication setup has a clear sequence with verification step. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear one-level-deep references: command-reference.md for full argument details, permissions.md for read/write classification, and external OAuth/GCP setup guides. The main file stays focused on overview and common examples while pointing to detailed resources. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents