recipe-schedule-recurring-event

Create a recurring Google Calendar event with attendees.

Quality

70%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/recipe-schedule-recurring-event/SKILL.md

Quality

Content

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 recipe-style skill. It provides a complete, executable command with all necessary parameters, includes a verification step, and clearly states its prerequisite dependency. The content is appropriately scoped for its single-purpose task.

Dimension	Reasoning	Score
Conciseness	Very lean — no unnecessary explanations of what Google Calendar is or how recurring events work. Every line serves a purpose.	3 / 3
Actionability	Provides a fully copy-paste-ready CLI command with concrete JSON payload including summary, recurrence rule, attendees, and timezone. The verification step is also a concrete command.	3 / 3
Workflow Clarity	This is a simple two-step skill: create then verify. The sequence is clear and includes an explicit verification step. For a non-destructive, simple operation this is sufficient.	3 / 3
Progressive Disclosure	For a simple, short skill under 50 lines, the content is well-organized with a prerequisite callout, clear steps section, and no need for external references. Structure is appropriate for the scope.	3 / 3
	Total	12 / 12 Passed

Description

40%

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 narrowly focused on a single specific action (creating recurring Google Calendar events with attendees), which gives it good distinctiveness but limits its usefulness as a comprehensive skill description. It lacks a 'Use when...' clause and misses common trigger term variations like 'meeting', 'schedule', or 'invite' that users would naturally use.

Suggestions

Add a 'Use when...' clause such as 'Use when the user wants to schedule a recurring meeting, set up a repeating calendar event, or invite attendees to a Google Calendar event.'

Include additional natural trigger terms users might say, such as 'meeting', 'schedule', 'invite', 'repeat', 'weekly', 'monthly'.

If the skill handles more Google Calendar actions beyond recurring events, list them (e.g., 'Create, update, and delete Google Calendar events, manage attendees, set up recurring schedules').

Dimension	Reasoning	Score
Specificity	Names the domain (Google Calendar) and a specific action (create a recurring event with attendees), but only describes a single action rather than listing multiple concrete capabilities.	2 / 3
Completeness	Describes what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric should cap completeness at 2, and the 'what' is also narrow enough that this lands at 1.	1 / 3
Trigger Term Quality	Includes natural keywords like 'Google Calendar', 'recurring', 'event', and 'attendees' which users would say, but misses common variations like 'meeting', 'schedule', 'repeat', 'invite', or 'calendar event'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Google Calendar', 'recurring event', and 'attendees' creates a very specific niche that is unlikely to conflict with other skills.	3 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

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: 2 months ago

Table of Contents

Discovery Implementation Validation

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.