Schedule cron jobs and automate recurring tasks
61
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/automation/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 brief and identifies the domain (cron jobs and recurring tasks) but lacks the depth needed for reliable skill selection. It omits explicit trigger guidance ('Use when...'), lists no specific concrete actions beyond 'schedule' and 'automate', and misses common keyword variations that users would naturally use.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about cron jobs, crontab entries, scheduled tasks, periodic automation, or recurring job configuration.'
List more specific concrete actions such as 'Create, edit, and list crontab entries, set up periodic scripts, configure job intervals and logging.'
Include natural keyword variations like 'crontab', 'scheduled tasks', 'periodic jobs', 'timer', and 'task scheduler' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (cron jobs, recurring tasks) and a couple of actions (schedule, automate), but doesn't list specific concrete actions like creating crontab entries, editing schedules, listing existing jobs, or managing task intervals. | 2 / 3 |
Completeness | Describes what the skill does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is also quite thin, warranting a score of 1. | 1 / 3 |
Trigger Term Quality | Includes 'cron jobs' and 'recurring tasks' which are relevant keywords, but misses common variations users might say like 'crontab', 'scheduled tasks', 'periodic', 'timer', 'cronjob', or 'automation schedule'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Cron jobs' is fairly specific, but 'automate recurring tasks' is broad enough to overlap with general automation, scripting, or task scheduling skills that aren't cron-specific. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%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-structured, concise reference for cron scheduling commands with good organization and token efficiency. However, it lacks context about what system these commands run in, what output to expect, and has no validation/error handling guidance. The skill reads more like a command reference card than an actionable guide.
Suggestions
Add brief context about what system/tool these commands target and any setup requirements so Claude knows when and how to use them.
Include example output for at least one command (e.g., what `/auto list` returns) so Claude knows what to expect and can verify success.
Add error handling guidance: what happens with invalid cron expressions, duplicate job names, or non-existent job IDs, and how to recover.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. No unnecessary explanations of what cron is or how scheduling works. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | Commands and presets are clearly listed with concrete syntax, but there's no indication of what actually executes these commands (is this a CLI tool? a bot? what system?), no setup/installation steps, and no output examples showing what responses look like. The commands are specific but not fully executable without understanding the underlying system. | 2 / 3 |
Workflow Clarity | The examples section shows a logical sequence (create, list, trigger, disable, remove), but there are no explicit validation steps—no guidance on what happens if a cron expression is invalid, no error handling, and no confirmation/verification steps after creating or modifying jobs. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized into logical sections (Commands, Cron Expressions, Presets, Examples) with clear headers. No need for external file references given the scope. | 3 / 3 |
Total | 10 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
e71a5f6
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.