automation

Schedule cron jobs and automate recurring tasks

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/automation/SKILL.md

Quality

Content

80%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and well-organized with copy-paste-ready commands and no padding, but it lacks validation/verification checkpoints for its destructive and batch operations, which caps workflow clarity. Progressive disclosure is appropriate for a simple self-contained skill.

Suggestions

Add validation/verification steps for destructive and batch operations, e.g. 'After creating a job, run `/auto list` to confirm it appears' and 'Confirm the job ID via `/auto list` before running `/auto remove`.'

Consider trimming the Examples section or making it distinct from the Commands/Presets sections to remove mild redundancy and push conciseness toward 5.

Optionally note error-recovery guidance (e.g. what to do if a cron expression is rejected) to strengthen the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations of what cron is, but the Examples section partly re-states the Commands and Presets sections, a minor redundancy; this fits the 4 anchor (efficient with minor trimmable instances) rather than 5 (every token earns its place) and well above 3 (no padded explanations).	4 / 5
Actionability	Copy-paste-ready commands with full argument syntax, a cron-expression table, named presets, and concrete examples with realistic job IDs cover the common cases, matching the 5 anchor; it is not a 4 because guidance is fully executable rather than having minor gaps.	5 / 5
Workflow Clarity	Although single-purpose, cron scheduling is a batch/recurring operation and `remove`/`disable` are destructive, yet no validation or verification steps exist (e.g. list-after-create, confirm-before-remove), so per the rubric cap workflow clarity cannot exceed 3; it is not a 2 because commands are clearly sequenced and labeled, and not a 4 because the validation checkpoints are missing rather than minor.	3 / 5
Progressive Disclosure	No bundle files exist and none are needed for this compact, single-purpose skill; the body is organized into clearly labeled sections (Commands, Cron Expressions, Presets, Examples) with no nested references, matching the 5 anchor for a simple skill with well-organized sections.	5 / 5
	Total	17 / 20 Passed

Description

61%Weight 40%Scale 1-5

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 concise and names a clear niche with concrete actions, but it omits any explicit "Use when" trigger guidance, which caps completeness. Trigger-term coverage is decent but lacks synonyms.

Suggestions

Add a 'Use when ...' clause naming concrete triggers (e.g. 'Use when the user wants to schedule, automate, or run recurring/periodic tasks on a cron schedule').

Include synonyms and natural phrasings users might say, such as 'recurring', 'periodic', 'timed', or 'scheduled jobs', to broaden trigger coverage.

Optionally enumerate a couple more concrete actions (e.g. list, enable/disable, remove jobs) to lift specificity above 3.

Dimension	Reasoning	Score
Specificity	"Schedule cron jobs and automate recurring tasks" names the domain and two concrete actions (schedule, automate) but offers no comprehensive list of capabilities, matching the 3 anchor; it is not a 2 because the actions are concrete rather than generic, and not a 4 because no additional specific actions are enumerated.	3 / 5
Completeness	There is a clear "what" (schedule cron jobs, automate recurring tasks) but no "Use when..." clause or equivalent trigger guidance, so per the rubric completeness is capped at 3; it is not a 4 because the "when" is entirely absent rather than weakly implied.	3 / 5
Trigger Term Quality	The phrase includes natural terms users would say ("cron jobs", "schedule", "automate recurring tasks") giving good keyword coverage; it is not a 5 because synonyms and variations (e.g. "recurring", "periodic", "timed tasks") are thin, and not a 3 because the terms present are natural rather than merely technical.	4 / 5
Distinctiveness Conflict Risk	Cron scheduling is a recognizable niche with distinct triggers, but the broad "automate recurring tasks" phrasing creates minor overlap with general task-automation skills, fitting the 4 anchor; not a 5 because of that overlap, not a 3 because cron is clearly more specific than generic document/file handling.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alsk1992/CloddsBot
Path: src/skills/bundled/automation/SKILL.md
Commit: 715fd4a

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.