recipe-create-vacation-responder
Enable a Gmail out-of-office auto-reply with a custom message and date range.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-create-vacation-responder77
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
50%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 clearly specifies what the skill does with concrete actions (enable auto-reply, custom message, date range) and targets a distinct niche (Gmail out-of-office). However, it lacks explicit trigger guidance ('Use when...') and misses common user terminology variations like 'vacation responder' or 'OOO', which limits Claude's ability to reliably select this skill.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user wants to set up an out-of-office message, vacation responder, or auto-reply in Gmail.'
Include common terminology variations users might say: 'vacation responder', 'OOO', 'away message', 'vacation reply', 'automatic reply'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Enable', 'out-of-office auto-reply', 'custom message', and 'date range'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Describes what the skill does 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 good terms like 'Gmail', 'out-of-office', 'auto-reply', but misses common variations users might say like 'vacation responder', 'OOO', 'away message', or 'vacation reply'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche - Gmail out-of-office functionality is distinct and unlikely to conflict with other skills. The combination of 'Gmail' + 'out-of-office' + 'auto-reply' creates a clear, unique trigger. | 3 / 3 |
Total | 9 / 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, well-crafted skill that demonstrates token efficiency while remaining fully actionable. It provides complete, executable commands with a clear workflow including verification, and appropriately scopes the content for its simple purpose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations about what vacation responders are or how Gmail works. Every line serves a purpose. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready commands with complete JSON payloads. Includes specific example values for subject, body, and settings. | 3 / 3 |
Workflow Clarity | Clear three-step sequence covering the full lifecycle: enable, verify, and disable. The verify step serves as a validation checkpoint. For this simple, non-destructive operation, this is sufficient. | 3 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is appropriately structured with a clear prerequisite callout and numbered steps. No need for external references. | 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.