CtrlK
BlogDocsLog inGet started
Tessl Logo

schedules

MUST use when configuring schedules.

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 ./system_prompts/auto-generated/skills/schedules/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The content is lean, concrete, and well-structured, with executable examples and an explicit guard around the destructive deploy operation. The only minor gap is the absence of a full validate-fix-retry feedback loop, which keeps workflow clarity just below the top anchor.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no padding or basic-concept lecturing; every section (file naming, the 6-field cron diagram, CLI commands) earns its place.

5 / 5

Actionability

It provides a concrete file-naming pattern with an example, a full cron format diagram, five copy-paste cron examples, and three executable wmill commands with comments covering the common cases.

5 / 5

Workflow Clarity

The destructive deploy operation is explicitly guarded with an explicit-confirmation gate and a `sync pull --dry-run` preview checkpoint, so the destructive-operation cap does not apply; it stops short of a full validate-fix-retry loop.

4 / 5

Progressive Disclosure

A simple, under-50-line skill with clear section headers and a single clearly-signaled one-level reference (AGENTS.wmill.md); no bundle files exist, and the content is appropriately scoped inline.

5 / 5

Total

19

/

20

Passed

Description

40%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 provides a clear trigger but omits what the skill does and lacks specific capabilities, leaving it too sparse for a strong match. Adding concrete actions (create, edit, deploy cron schedules) and a 'what' clause would substantially raise completeness and specificity.

Suggestions

Add a 'what' clause stating concrete actions, e.g. 'Create, edit, and deploy cron-based schedules for Windmill scripts and flows.'

Include natural trigger variations and synonyms such as 'cron', 'automated runs', or 'recurring jobs' alongside 'schedules'.

Keep third person and avoid over-claiming, but list 1-2 more specific capabilities to lift the specificity score above 2.

DimensionReasoningScore

Specificity

The description names the domain ("schedules") but only offers the generic action "configuring" with no concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

A clear 'when' trigger is present ("MUST use when configuring schedules") but the 'what' — what the skill actually does — is absent, matching the 'only when is present without what' anchor.

2 / 5

Trigger Term Quality

"configuring schedules" includes the natural term users would say, but only one generic keyword with no synonyms or variations like "cron" or "automated runs".

3 / 5

Distinctiveness Conflict Risk

"schedules" is a fairly distinct niche with only minor overlap risk against closely related timing/automation skills, though no concrete action list sharpens the niche further.

4 / 5

Total

11

/

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
windmill-labs/windmill
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.