CtrlK
BlogDocsLog inGet started
Tessl Logo

cron

Schedule reminders and recurring tasks.

66

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a tight, well-structured reference for a simple tool: concrete executable examples, clear mode enumeration, a useful time-expression mapping, and an explicit when-not-to-use guard, with no padding.

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows; every section (modes, examples, time-expression table, timezone) earns its place and assumes Claude's competence, matching the score-3 anchor.

3 / 3

Actionability

It provides copy-paste-ready executable calls such as `cron(action="add", message="...", every_seconds=1200)` plus list/remove examples and a concrete user-says-to-parameters table, matching the score-3 anchor of fully executable, specific examples.

3 / 3

Workflow Clarity

For this simple single-tool skill the action is unambiguous: three modes are enumerated, examples clarify each, and a clear "do not use" guard routes the wrong case to HEARTBEAT.md, satisfying the simple-skill allowance for a 3.

3 / 3

Progressive Disclosure

Under 50 lines with no external references needed, the content is well-organized into clear sections (Three Modes, Examples, Time Expressions, Timezone), meeting the simple-skill criterion for a 3 with well-organized sections.

3 / 3

Total

12

/

12

Passed

Description

57%

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 occupies a clear niche, but it is a single short clause with no explicit "Use when..." trigger guidance and limited keyword coverage, leaving it just above the vague-fluff floor.

Suggestions

Add a "Use when..." clause, e.g. "Use when the user asks to schedule reminders or recurring/automated tasks."

Broaden trigger terms to include natural variations like "schedule", "cron jobs", "alerts", and "daily/weekly tasks".

List more concrete actions (e.g. one-time vs. recurring, list and remove jobs) to raise specificity.

DimensionReasoningScore

Specificity

"Schedule reminders and recurring tasks" names the domain (scheduling) and two actions (reminders, recurring tasks), but is not a comprehensive list of multiple concrete actions, matching the score-2 anchor rather than the multi-action score-3 example.

2 / 3

Completeness

It answers "what" (schedule reminders and recurring tasks) but has no "Use when..." clause or explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

"reminders and recurring tasks" are natural user terms, but coverage is limited and omits common variations like "schedule", "cron", "alerts", or "daily/weekly", fitting the score-2 anchor of some relevant keywords with missing variations.

2 / 3

Distinctiveness Conflict Risk

Scheduling reminders/recurring tasks is a clear niche unlikely to overlap with other skills, matching the score-3 anchor of a clear niche with distinct triggers.

3 / 3

Total

9

/

12

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
HKUDS/nanobot
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.