gws-calendar-insert
Google Calendar: Create a new event.
72
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-calendar-insert/SKILL.mdQuality
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.
The description is extremely terse—it identifies the platform and a single action but lacks trigger guidance, natural keyword variations, and detail about what creating an event entails. It would benefit significantly from a 'Use when...' clause and additional trigger terms that match how users naturally request calendar actions.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user wants to schedule a meeting, add a calendar event, or book time on Google Calendar.'
Include natural keyword variations users would say, such as 'schedule', 'meeting', 'appointment', 'calendar invite', 'book time', 'set up a call'.
Expand the capability description to mention specific details like setting date/time, adding attendees, location, or recurrence to distinguish from other calendar skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Calendar) and one specific action (create a new event), but does not list multiple concrete actions or elaborate on capabilities. | 2 / 3 |
Completeness | Describes what it does (create a new event on Google Calendar) but has no 'Use when...' clause or explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also minimal—so this scores at 1. | 1 / 3 |
Trigger Term Quality | Includes 'Google Calendar' and 'event' which are natural terms users might say, but misses common variations like 'schedule a meeting', 'add appointment', 'calendar invite', 'book time'. | 2 / 3 |
Distinctiveness Conflict Risk | Specifying 'Google Calendar' and 'create a new event' provides some distinctiveness, but could overlap with other Google Calendar skills (e.g., update event, list events) or generic calendar/scheduling skills 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, concise skill that provides everything needed to create a Google Calendar event via the gws CLI. It excels at actionability with concrete examples and a complete flags table, maintains excellent token efficiency by avoiding unnecessary explanations, and includes appropriate safety guardrails for a write operation. The progressive disclosure is well-handled with clear references to shared infrastructure and related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a purpose—flags table, examples, and a safety caution. No unnecessary explanations of what Google Calendar is or how events work. The tips section is minimal and relevant. | 3 / 3 |
Actionability | Provides fully executable bash commands with concrete flag values, a complete flags table with required/optional markers and defaults, and multiple usage examples covering different scenarios (basic, attendees, Meet link). | 3 / 3 |
Workflow Clarity | This is a single-command skill, so complex multi-step workflows aren't needed. The write operation includes an explicit caution to confirm with the user before executing, which is the appropriate validation checkpoint for a destructive/write operation. | 3 / 3 |
Progressive Disclosure | Clear structure with a prerequisite reference to shared auth/flags skill, well-organized sections (Usage, Flags, Examples, Tips), and appropriate 'See Also' links to related skills. References are one level deep and clearly signaled. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%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
c7c6646
- 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.