cron
Schedule reminders and recurring tasks.
78
66%
Does it follow best practices?
Impact
100%
1.81xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./nanobot/skills/cron/SKILL.mdQuality
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 is too brief and lacks explicit trigger guidance ('Use when...'), which is critical for skill selection. While it names a recognizable domain, it doesn't enumerate specific capabilities or provide enough natural language keywords to reliably distinguish it from related skills like calendar management or task tracking.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks to set a reminder, create a recurring task, or schedule a notification.'
Include more natural trigger terms and variations such as 'alarm', 'notification', 'daily', 'weekly', 'to-do', 'scheduled task'.
Expand the capability list with specific actions like 'create, edit, delete, and list reminders and recurring tasks' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (reminders and tasks) and two actions (schedule reminders, recurring tasks), but lacks detail on specific capabilities like editing, deleting, listing, or notification methods. | 2 / 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. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also thin, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes natural keywords like 'reminders' and 'recurring tasks' that users might say, but misses common variations such as 'alarm', 'notification', 'to-do', 'scheduled', 'repeat', or 'daily/weekly'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to scheduling reminders and recurring tasks, but could overlap with general task management, calendar, or to-do list 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, lean skill that efficiently teaches cron tool usage through concrete examples and a well-structured reference table. It assumes Claude's competence, avoids unnecessary explanation, and covers all key use cases (recurring, one-time, timezone-aware) with copy-paste-ready invocations. The organization is clean and scannable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. No unnecessary explanations of what cron is or how scheduling works. The table format for time expressions is efficient and informative. | 3 / 3 |
Actionability | Provides concrete, copy-paste-ready tool invocations covering all modes (add, list, remove) with specific parameter examples. The time expressions table maps natural language to exact parameters. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose skill with clear modes enumerated upfront. The three modes are unambiguous, and list/remove operations are shown for management. No destructive batch operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into logical sections (modes, examples, time expressions, timezone) that are easy to scan and 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.
- Repository
- HKUDS/nanobot
- Commit
04a41e3
- 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.