recipe-block-focus-time
Create recurring focus time blocks on Google Calendar to protect deep work hours.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-block-focus-time70
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
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 identifies a clear, specific use case (focus time blocks on Google Calendar) but lacks completeness due to missing trigger guidance. It would benefit from explicit 'Use when...' language and additional trigger terms that users naturally say when requesting this functionality.
Suggestions
Add a 'Use when...' clause with trigger terms like 'block time for focus', 'protect my calendar', 'schedule deep work', 'create focus blocks'
Include additional natural keywords users might say: 'calendar blocking', 'meeting-free time', 'do not disturb hours', 'productivity time'
Expand capabilities to mention related actions if applicable, such as modifying existing focus blocks or analyzing calendar availability
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Calendar) and a specific action (create recurring focus time blocks), but only describes one action rather than multiple concrete capabilities. Uses third person voice correctly. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes some natural keywords like 'focus time', 'Google Calendar', 'deep work', but missing common variations users might say like 'block time', 'do not disturb', 'meeting-free time', 'calendar blocking', or 'productivity blocks'. | 2 / 3 |
Distinctiveness Conflict Risk | Fairly specific to focus time/deep work scheduling on Google Calendar, but could overlap with general calendar management skills. The 'recurring' and 'focus time' aspects provide some distinction but aren't strongly differentiated. | 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 an excellent, well-crafted skill that demonstrates token efficiency while providing complete, actionable guidance. The prerequisite is clearly stated, commands are executable with realistic parameters, and the verification step ensures the user can confirm success. No improvements needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations about what Google Calendar is or how recurring events work. Every line serves a purpose. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready commands with complete JSON payloads. Specific parameters for timezone, recurrence pattern, and transparency are all included. | 3 / 3 |
Workflow Clarity | For this simple two-step skill, the sequence is clear: create the event, then verify it. The verification step serves as a validation checkpoint to confirm the event shows as busy. | 3 / 3 |
Progressive Disclosure | For a simple skill under 50 lines with a single task, the structure is appropriate. Clear prerequisite callout and well-organized sections without unnecessary 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.