recipe-batch-invite-to-event
Add a list of attendees to an existing Google Calendar event and send notifications.
86
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 concise and specific about what the skill does—adding attendees to Google Calendar events and sending notifications. Its main weakness is the absence of an explicit 'Use when...' clause, which limits Claude's ability to know when to select it. Adding trigger guidance and a few more natural keyword variations would strengthen it significantly.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to invite people to a calendar event, add participants, or update a Google Calendar guest list.'
Include common keyword variations users might say, such as 'invite', 'participants', 'guest list', 'calendar invite', or 'add people to meeting'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists specific concrete actions: 'Add a list of attendees', 'existing Google Calendar event', and 'send notifications'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (add attendees to a calendar event and send notifications), but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes good natural terms like 'attendees', 'Google Calendar event', and 'notifications', but misses common variations users might say such as 'invite people', 'add participants', 'calendar invite', or 'guest list'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific niche: adding attendees to Google Calendar events with notifications. This is unlikely to conflict with other skills due to the narrow, well-defined scope combining Google Calendar, attendees, and notifications. | 3 / 3 |
Total | 10 / 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 an excellent, concise skill that provides clear, executable commands for a well-defined task. The three-step workflow (get, patch, verify) is appropriately structured with a validation step. The prerequisite callout properly signals the dependency on the gws-calendar skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. The prerequisite note is necessary, and every line serves a purpose. No unnecessary explanations of what Google Calendar is or how APIs work. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready CLI commands with specific flags and JSON payloads. The example attendee emails make the pattern clear and easy to adapt. | 3 / 3 |
Workflow Clarity | Clear 3-step sequence: get event, patch with attendees, verify. The verification step serves as an explicit validation checkpoint. For this simple, non-destructive operation (adding attendees), this level of workflow is appropriate. | 3 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with a clear prerequisite callout and numbered steps. No need for external references given the scope. | 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
a3768d0
- 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.