cron
Schedule reminders and recurring tasks.
78
Quality
66%
Does it follow best practices?
Impact
100%
1.81xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./nanobot/skills/cron/SKILL.mdDiscovery
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 is too brief and lacks critical components for effective skill selection. While it identifies the core domain (reminders and recurring tasks), it fails to provide explicit trigger guidance and misses natural keyword variations users would employ. The absence of a 'Use when...' clause significantly limits Claude's ability to reliably select this skill.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks to be reminded, wants to set up recurring tasks, mentions alarms, or needs scheduled notifications.'
Expand trigger terms to include natural variations: 'remind me', 'set a reminder', 'daily/weekly/monthly tasks', 'notify me', 'alarm', 'scheduled'.
Add more specific capabilities such as 'set one-time or recurring reminders, manage scheduled notifications, create repeating task schedules'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (reminders/tasks) and two actions (schedule reminders, recurring tasks), but lacks comprehensive detail about specific capabilities like notification methods, time formats, or task management features. | 2 / 3 |
Completeness | Describes what it does (schedule reminders and recurring tasks) 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 natural terms 'reminders' and 'recurring tasks' that users might say, but misses common variations like 'alarm', 'notify me', 'remind me', 'scheduled', 'daily/weekly tasks', or 'to-do'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to scheduling/reminders domain, but 'tasks' is generic and could overlap with task management, to-do list, or project management skills without clearer boundaries. | 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 skill file that demonstrates strong conciseness and actionability. It provides clear, executable examples for all use cases without over-explaining concepts Claude already understands. The structure is logical and the time expressions table is particularly useful for translating user intent to parameters.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, with no unnecessary explanations of what cron is or how scheduling works. Every section provides direct, actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable code examples for all modes (reminder, task, one-time, cron expression). The time expressions table gives concrete parameter mappings that are copy-paste ready. | 3 / 3 |
Workflow Clarity | For this simple, single-purpose skill, the three modes are clearly distinguished and each has unambiguous usage. List/remove operations are shown for job management, completing the workflow. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized with clear sections (modes, examples, time expressions, timezone) that are easy to navigate. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.