Schedule cron jobs and automate recurring tasks
71
60%
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 identifies a clear domain (cron/scheduling) but is too brief and lacks explicit trigger guidance. It needs a 'Use when...' clause and more specific actions to help Claude distinguish this skill from general automation or scripting skills.
Suggestions
Add a 'Use when...' clause with trigger terms like 'cron', 'crontab', 'scheduled task', 'run daily', 'periodic job', 'background automation'
Expand specific actions: 'Create and edit crontab entries, configure job schedules, set up periodic scripts, manage scheduled task timing'
Include file/format references users might mention: 'crontab files', '/etc/cron.d', 'cron expressions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (cron jobs, recurring tasks) and implies actions (schedule, automate), but lacks specific concrete actions like 'create crontab entries, set up scheduled scripts, configure job timing'. | 2 / 3 |
Completeness | Describes what it does (schedule cron jobs, automate 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 'cron jobs' and 'recurring tasks' which are relevant keywords, but misses common variations users might say like 'crontab', 'scheduled tasks', 'timer', 'periodic', or 'background jobs'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Cron jobs' is fairly specific to Unix-like scheduling, but 'automate recurring tasks' is broad and could overlap with general automation, scripting, or workflow skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%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 reference skill that efficiently documents cron scheduling commands with excellent conciseness and actionability. The main weakness is the lack of workflow guidance around verification (how to confirm a job is running correctly) and error handling (what to do if a job fails).
Suggestions
Add a brief workflow section showing the typical create -> list -> verify pattern, e.g., 'After creating a job, use `/auto list` to confirm it appears with the correct schedule'
Consider adding a note about how to check job execution status or logs to verify jobs are running as expected
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what cron is or how scheduling works. Every line provides actionable reference information. | 3 / 3 |
Actionability | Fully concrete with copy-paste ready commands. Clear command syntax, preset names, and cron expression examples that can be used immediately. | 3 / 3 |
Workflow Clarity | Commands are listed but there's no guidance on typical workflows (e.g., create -> verify -> monitor). No validation steps mentioned for confirming jobs are scheduled correctly or troubleshooting failed jobs. | 2 / 3 |
Progressive Disclosure | For a simple reference skill under 50 lines, the content is well-organized with clear sections (Commands, Cron Expressions, Presets, Examples). No need for external file references given the scope. | 3 / 3 |
Total | 11 / 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 | |
2a8c94e
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.