recipe-create-events-from-sheet
Read event data from a Google Sheets spreadsheet and create Google Calendar entries for each row.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-create-events-from-sheet81
Quality
77%
Does it follow best practices?
Impact
91%
15.16xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/recipe-create-events-from-sheet/SKILL.mdDiscovery
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 effectively communicates a specific integration task between Google Sheets and Google Calendar with concrete actions. However, it lacks explicit trigger guidance ('Use when...') which would help Claude know when to select this skill, and could benefit from additional natural keywords users might say when requesting this functionality.
Suggestions
Add a 'Use when...' clause with trigger terms like 'import events from spreadsheet', 'bulk create calendar events', 'schedule from sheets'
Include common variations users might say: 'calendar events', 'schedule', 'appointments', 'import to calendar'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists two concrete actions: 'Read event data from a Google Sheets spreadsheet' and 'create Google Calendar entries for each row'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (read sheets, create calendar entries) but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes natural terms like 'Google Sheets', 'spreadsheet', 'Google Calendar', and 'event data', but missing common variations like 'calendar events', 'schedule', 'import events', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Google Sheets reading with Google Calendar creation. The two-service integration makes it clearly distinguishable from general spreadsheet or calendar skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%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 recipe skill that provides clear, actionable commands for the task. Its main weakness is the lack of validation or error handling guidance for what is essentially a batch operation (creating multiple calendar events), which could fail silently or partially.
Suggestions
Add a validation step to verify events were created successfully (e.g., list calendar events after creation or check for API errors)
Include guidance on handling malformed row data or missing required fields in the spreadsheet
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations, assumes Claude knows how to iterate and use CLI tools. Every line serves a purpose. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready CLI commands with realistic example arguments (spreadsheet ID placeholder, actual date format, attendee emails). Fully executable guidance. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (read then create), but lacks validation checkpoints for a batch operation. No guidance on handling failures, malformed data, or verifying events were created successfully. | 2 / 3 |
Progressive Disclosure | For a simple two-step recipe under 20 lines, the structure is appropriate. Prerequisites are clearly stated upfront, and the skill appropriately references external skills rather than duplicating their content. | 3 / 3 |
Total | 11 / 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.