Create recurring focus time blocks on Google Calendar to protect deep work hours.
81
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/recipe-block-focus-time/SKILL.mdQuality
Discovery
54%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 identifies a specific niche (focus time blocks on Google Calendar for deep work) with good natural trigger terms, making it distinctive. However, it lacks an explicit 'Use when...' clause, which significantly hurts completeness, and it only describes a single action rather than a fuller set of capabilities.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to schedule focus time, protect deep work hours, or block off recurring calendar time for concentration.'
Expand the capability list to include related actions such as modifying, removing, or reviewing existing focus time blocks to improve specificity.
| 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 listing multiple concrete capabilities like modifying, deleting, or querying focus blocks. | 2 / 3 |
Completeness | Describes what the skill does but has no explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent (only implied), this scores a 1. | 1 / 3 |
Trigger Term Quality | Contains strong natural trigger terms users would say: 'focus time', 'deep work', 'Google Calendar', 'recurring', and 'time blocks' are all phrases users naturally use when requesting this kind of scheduling help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche combining Google Calendar with recurring focus time blocks for deep work — unlikely to conflict with other skills due to the narrow, well-defined scope. | 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 a well-crafted, concise skill that provides fully executable commands for a single-purpose task. It correctly assumes Claude's competence, includes a verification step, and clearly states its prerequisite dependency. The only minor note is that the hardcoded date (2025-01-20) may need adjustment, but the recurrence rule makes the specific start date less critical.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations about what Google Calendar is or how focus time works. Every line serves a purpose. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready commands with all necessary parameters (recurrence rule, timezone, transparency setting). The JSON payload is complete and specific. | 3 / 3 |
Workflow Clarity | For this simple two-step skill, the sequence is clear: create the event, then verify it. The verification step (checking it shows as busy) serves as a validation checkpoint. This is a non-destructive, easily reversible operation so no feedback loop is needed. | 3 / 3 |
Progressive Disclosure | For a simple skill under 50 lines with a single task, the content is well-organized with a clear prerequisite callout and numbered steps. No external references are needed. | 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 | |
a3768d0
Table of Contents
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.