gws-calendar-insert
Google Calendar: Create a new event.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill gws-calendar-insert70
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
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.
This description is too minimal to effectively guide skill selection. While it correctly identifies the platform and a core action, it lacks the breadth of capabilities, natural trigger terms, and explicit 'Use when' guidance needed for Claude to reliably choose this skill from a large skill library.
Suggestions
Add a 'Use when...' clause with trigger terms like 'schedule', 'meeting', 'appointment', 'add to calendar', 'gcal', or 'book time'
Expand capabilities beyond just creating events - include actions like 'schedule meetings, set reminders, block time, add attendees'
Include file/format indicators if applicable, such as calendar invites or .ics files
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Calendar) and one specific action (create a new event), but only describes a single capability rather than multiple concrete actions. | 2 / 3 |
Completeness | Describes what it does (create calendar 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 'event' which are natural terms, but missing common variations like 'schedule', 'meeting', 'appointment', 'add to calendar', or 'gcal'. | 2 / 3 |
Distinctiveness Conflict Risk | Google Calendar is a specific platform which helps distinguish it, but 'create event' could overlap with other calendar or scheduling skills without clearer trigger terms. | 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 practices: it's concise, provides executable examples, includes appropriate safety warnings for write operations, and properly references shared documentation. The flags table format is efficient and the examples demonstrate real usage patterns without over-explaining.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and efficient with no unnecessary explanations. Every section serves a purpose - flags table is compact, examples are minimal but sufficient, and tips are brief. | 3 / 3 |
Actionability | Provides complete, copy-paste ready bash commands with concrete examples. The flags table clearly specifies required vs optional parameters with exact format expectations (ISO 8601). | 3 / 3 |
Workflow Clarity | For a single-action skill, the workflow is unambiguous. Includes an explicit validation checkpoint via the CAUTION callout requiring user confirmation before executing the write command. | 3 / 3 |
Progressive Disclosure | Excellent structure with prerequisite reference to shared auth/flags, clear 'See Also' section with one-level-deep references, and appropriate content split between this skill and related files. | 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 | |
- 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.