cron

Use when the user asks to schedule recurring tasks, one-off reminders, timers, or cron-style jobs through the OpenSquilla cron tool.

Quality

90%

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

Quality

Content

93%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.

An exemplary short skill body: executable examples for every schedule shape, no concept over-explanation, and clean sectioning. The only gap is a missing verification step after scheduling.

Suggestions

Add a brief 'verify' step suggesting cron(action="list") after an add, so the workflow has an explicit checkpoint confirming the job was registered with the expected job_id.

Optionally note that remove is irreversible, prompting confirmation of the job_id before cancellation.

Dimension	Reasoning	Score
Conciseness	The body is lean: it assumes Claude knows what cron is, jumps straight to the structured schedule shapes, and every sentence (including the note that the tool rejects flat strings) earns its place with no padding.	5 / 5
Actionability	It gives fully formed, copy-paste-ready cron tool calls for each of the three schedule shapes plus list/run/remove, covering the common cases with real argument values.	5 / 5
Workflow Clarity	The translate-then-call sequence is clear and the structured-error note acts as an implicit feedback loop, but there is no explicit checkpoint to confirm a job was created (e.g. calling list afterward) for the add path.	4 / 5
Progressive Disclosure	At under 50 lines with no external bundle files, the content is organized into clean sections (schedule shapes, translation examples, other actions, format ref) that fully satisfy the simple-skill bar.	5 / 5
	Total	19 / 20 Passed

Description

87%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.

A tight, well-targeted description that names the tool, the actions, and explicit use-when triggers in one sentence. The only room for improvement is broadening natural-language trigger synonyms inside the description itself.

Suggestions

Fold one or two high-frequency natural phrasings (e.g. 'remind me' or 'every N minutes') directly into the description so the trigger surface matches the frontmatter trigger list.

Consider naming the complementary actions (list, run, cancel) so the 'what' covers the full tool surface, not just scheduling.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions — 'schedule recurring tasks, one-off reminders, timers, or cron-style jobs' — but they are all variants of one scheduling domain rather than a maximally comprehensive action set, so it sits just below the top anchor.	4 / 5
Completeness	The 'Use when the user asks to schedule...' clause explicitly states when to invoke the skill, and the same phrase enumerates what it does, cleanly answering both what and when with concrete trigger phrases.	5 / 5
Trigger Term Quality	It surfaces natural terms users say ('schedule', 'recurring tasks', 'reminders', 'timers', 'cron-style jobs') with good synonym coverage, though it omits some common phrasings like 'remind me' or 'every N minutes' that the frontmatter triggers actually capture.	4 / 5
Distinctiveness Conflict Risk	Scoping to 'the OpenSquilla cron tool' with cron/reminder-specific triggers gives it a clear niche and minimal overlap with unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: TokenRhythm/opensquilla
Path: src/opensquilla/skills/bundled/cron/SKILL.md
Commit: 94ac35e

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.