CtrlK
BlogDocsLog inGet started
Tessl Logo

cron-task-creator

Create, manage, and run scheduled automated tasks (cron jobs) in Clacky. Use this skill whenever the user wants to create a new automated task or cron job, set up recurring automation, schedule something to run daily/weekly/hourly, view all scheduled tasks, edit an existing task prompt or cron schedule, enable or disable a task, delete a task, check task run history or logs, or run a task immediately via the WebUI. Trigger on phrases like cron, scheduled task, run every day, automate this; 定时任务, 每天自动, 定时执行.

74

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong, actionable operations manual with concrete API commands and clear step sequencing. Weakest on conciseness (verbose confirmation/template blocks) and progressive_disclosure (all content inlined).

Suggestions

Move the eight-task template catalog and/or the cron expression quick reference into a separate references file referenced from SKILL.md to reduce inline weight and improve progressive disclosure.

Trim or collapse the repeated emoji confirmation blocks into a single reusable output-format convention to save tokens.

Add an explicit post-action verification step (e.g. re-LIST after DELETE/CREATE) to turn confirmation into a true validate-and-retry feedback loop, raising workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but the repeated emoji confirmation blocks and the eight-item template list could be trimmed slightly. Not a 5 because not every token earns its place.

4 / 5

Actionability

Every operation ships copy-paste-ready curl commands with headers and JSON payloads, plus a complete example task prompt and output formats covering the common cases.

5 / 5

Workflow Clarity

CREATE and EDIT use explicit numbered steps and DELETE carries a confirmation gate; however there is no validate-then-retry feedback loop after execution, leaving minor validation gaps.

4 / 5

Progressive Disclosure

The single SKILL.md is well-organized with clear section headers and no nested references; the cron table and templates list are reference material that could optionally live in a separate file, a minor organization gap.

4 / 5

Total

17

/

20

Passed

Description

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

An exemplary description: third-person voice, concrete action list, explicit trigger guidance, and a clear niche with multilingual triggers. No meaningful improvements needed.

DimensionReasoningScore

Specificity

The description lists many concrete actions (create, manage, run, view all, edit, enable/disable, delete, check history/logs, run immediately), giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

It explicitly answers both what ('Create, manage, and run scheduled automated tasks (cron jobs) in Clacky') and when ('Use this skill whenever… Trigger on phrases like…') with concrete trigger phrases.

5 / 5

Trigger Term Quality

It provides comprehensive natural trigger phrases including synonyms and file-style tokens ('cron, scheduled task, run every day, automate this') plus multilingual equivalents, matching the top anchor.

5 / 5

Distinctiveness Conflict Risk

The Clacky cron-task niche is clearly scoped with distinct triggers, so overlap with unrelated skills is minimal.

5 / 5

Total

20

/

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
clacky-ai/openclacky
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.