CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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; 定时任务, 每天自动, 定时执行.

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

88%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 workflow-safe: concrete commands, complete payloads, and explicit error handling around destructive operations. Its main weaknesses are mild redundancy in the ordinary/secretary type-preservation rules repeated across sections and a single-file structure that inlines some reference-like material despite its length.

DimensionReasoningScore

Conciseness

The body is dense with Clacky-specific operational detail and assumes competence (no cron or REST tutorials), but the ordinary-vs-secretary type-preservation rules are restated across several sections ("PATCH preserves the target", "Neither owner_session_id nor target is editable", "Results return to the saved owner") and could be consolidated — minor over-explanation matching the 4 anchor rather than the 'every token earns its place' 5.

4 / 5

Actionability

Fully executable guidance: a copy-paste curl listing command, a complete endpoint table, ready JSON payloads for both ordinary and secretary tasks ("daily_file_summary", "morning_report"), PATCH examples, a cron expression table, and a precise POST procedure ("Serialize the selected payload into a temporary JSON file... --data-binary @<payload-file>") covering the common cases.

5 / 5

Workflow Clarity

A clear numbered sequence (list/select, create, edit, enable/disable, delete, history, run now) with explicit validation checkpoints and error-recovery loops: "Always inspect the response and handle errors before reporting success", "Do not claim completion from 202", 409 blocker handling, and ambiguity-clarification rules before mutating or deleting plans.

5 / 5

Progressive Disclosure

The single file is well organized with clear sections, tables, and numbered operations, and no bundle files exist to reference; however, at ~225 lines, content such as the cron template table and endpoint reference is inlined where it could arguably live in a separate file — good structure with minor organization gaps, matching the 4 anchor.

4 / 5

Total

18

/

20

Passed

Description

92%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 strong description: it enumerates concrete capabilities across the entire task lifecycle, gives an explicit "Use this skill when" clause with natural trigger phrases in two languages, and is clearly distinguishable from other skills. The only weakness is that a handful of common trigger synonyms (recurring, periodic) are missing.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the full lifecycle — "create a new automated task or cron job", "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", "run a task immediately via the WebUI" — comprehensive coverage matching the top anchor rather than the 'minor gaps' anchor below.

5 / 5

Completeness

Both halves are explicit: the what ("Create, manage, and run scheduled automated tasks (cron jobs) in Clacky") and the when ("Use this skill whenever the user wants to..." followed by concrete trigger phrases), exactly matching the anchor that clearly answers both with concrete triggers.

5 / 5

Trigger Term Quality

"Trigger on phrases like cron, scheduled task, run every day, automate this; 定时任务, 每天自动, 定时执行" provides good natural, bilingual keyword coverage, but a few common variations users would say (recurring, periodic, every morning/week) are absent — between the good-coverage and comprehensive anchors, so a 4.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche — scheduled cron jobs in Clacky including WebUI-specific operations — with distinct triggers like "cron" and "scheduled task" that are unlikely to fire for unrelated skills; minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

clacky-ai/openclacky

Path

lib/clacky/default_skills/cron-task-creator/SKILL.md

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.