CtrlK
BlogDocsLog inGet started
Tessl Logo

cron

Schedule reminders and recurring tasks.

58

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./bot/workspace/skills/cron/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is an efficient, well-structured tool wrapper with concrete examples and a useful time-expression mapping. Its main weakness is the destructive remove operation lacking any validation or confirmation guidance, which caps workflow clarity.

Suggestions

Add a validation step before removal, e.g. 'Run cron(action="list") first to confirm the job_id, then remove.'

Clarify the one-time `at` parameter with a concrete computed ISO datetime example rather than a placeholder.

Note that one-time jobs auto-delete after running so users know no cleanup is needed.

DimensionReasoningScore

Conciseness

The body is lean: it states the three modes, gives concrete tool calls, and a compact time-expression table without explaining what cron is or padding with concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Examples are concrete, copy-paste tool calls covering add/list/remove and the common time patterns; the `at="<ISO datetime>"` placeholder is a minor gap that keeps it just below fully executable 5.

4 / 5

Workflow Clarity

The skill includes the destructive 'remove' operation (`cron(action="remove", job_id="abc123")`) with no validation step such as listing first or confirming the job_id; per the judging guidelines, missing validation in a destructive operation caps workflow_clarity at 3 despite the otherwise simple single-purpose design.

3 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained with no external references needed, and well-organized into clear sections (Three Modes, Examples, Time Expressions); per the simple-skill guidance this qualifies for 5 on well-organized sections alone.

5 / 5

Total

17

/

20

Passed

Description

53%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 concrete capabilities, but it lacks any explicit 'Use when...' trigger guidance, which caps completeness and limits trigger-term coverage. It is reasonably distinct from other skills but could benefit from natural user phrasing.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to schedule reminders, set up recurring tasks, or automate time-based actions.'

Include natural user phrasings like 'remind me to', 'set a recurring reminder', or 'cron-style schedule' to broaden trigger-term coverage.

Mention one-shot/specific-time scheduling in the description to reflect the third mode and improve completeness.

DimensionReasoningScore

Specificity

Names the domain ('Schedule') and two concrete actions ('reminders and recurring tasks'), matching the anchor for 1-2 concrete actions without comprehensive coverage; not score 4 because no additional specific actions are enumerated.

3 / 5

Completeness

The what is clear ('Schedule reminders and recurring tasks') but there is no 'Use when...' clause or equivalent trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

'reminders' and 'recurring tasks' are natural user phrases, but common variations like 'remind me', 'schedule', 'cron', or 'set a timer' are absent; matches the 'some relevant keywords but missing variations' anchor rather than the comprehensive coverage of 5.

3 / 5

Distinctiveness Conflict Risk

Scheduling reminders/recurring tasks is a fairly distinct niche with only minor overlap risk against generic todo or calendar skills; fits 'mostly distinct; minor overlap risk' better than the broad 3 anchor.

4 / 5

Total

13

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
volcengine/OpenViking
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.