CtrlK
BlogDocsLog inGet started
Tessl Logo

cron-scheduler

Schedule management with staggering, quiet hours, and wake-up override. Validates schedules, prevents collisions, and gates delivery during quiet hours.

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/cron-scheduler/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable with a clear, validated workflow and concrete copy-paste examples. It loses points for the verbose multi-source section and inline version chatter that could be extracted into a separate reference.

Suggestions

Move the multi-source-brains pattern (and its legacy/version details) into a separate reference file, leaving a one-line pointer in SKILL.md to improve progressive disclosure and conciseness.

Relocate version-specific notes (v0.40.3.0+, v0.11.0) into a clearly marked 'Deprecated/legacy' subsection so time-sensitive information does not penalize the active guidance.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but the multi-source section interleaves version chatter (v0.40.3.0+, v0.11.0) into active guidance and includes a verbose legacy-explanation paragraph that could be tightened — mostly efficient but not fully earning a 3.

2 / 3

Actionability

Provides copy-paste-ready guidance: the consolidated cron line 'gbrain sync --all --parallel 4 --workers 4 --skip-failed', an explicit slot list (:05–:50), the report path template, and the one-line thin-prompt template — matching the score-3 anchor.

3 / 3

Workflow Clarity

A clear five-phase sequence includes explicit validation (collision check) and a feedback loop ('If collision detected, suggest the next available slot'), plus idempotency and test-before-bulk verification for these batch operations — so it is not capped at 2.

3 / 3

Progressive Disclosure

References like cron-via-minions.md and plugin-handlers.md are well-signaled and one-level-deep, but the large inline multi-source-brains block is content that could be split into a separate reference, and no bundle files exist to verify structure — better organized than a 1 but not a clean 3.

2 / 3

Total

10

/

12

Passed

Description

67%

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 specific and distinctive, clearly conveying the skill's scheduling niche. Its main weakness is the missing 'Use when…' trigger guidance and reliance on the separate triggers list for natural user keywords.

Suggestions

Add an explicit 'Use when…' clause to the description (e.g., 'Use when scheduling recurring jobs, deconflicting cron entries, or setting quiet hours') to lift completeness to 3.

Surface natural trigger keywords like 'cron' and 'schedule a job' inside the description itself rather than only in the triggers list to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'staggering', 'Validates schedules', 'prevents collisions', and 'gates delivery' — matching the score-3 anchor for multiple specific concrete actions rather than the single-domain score-2 example.

3 / 3

Completeness

Clearly answers what the skill does, but contains no 'Use when…' clause or equivalent explicit trigger guidance in the description; the rubric caps completeness at 2 in that case, and it is above 1 because the 'what' is well stated.

2 / 3

Trigger Term Quality

'quiet hours' and 'Schedule' are natural user terms, but 'staggering' and 'wake-up override' are semi-technical and the common variations ('cron', 'schedule a job') appear only in the triggers list, not the description — missing common variations, so not a 3.

2 / 3

Distinctiveness Conflict Risk

Distinctive qualifiers — 'quiet hours', 'staggering', 'wake-up override', collision prevention — carve a clear niche unlikely to conflict with other skills, matching the score-3 anchor.

3 / 3

Total

10

/

12

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.

Validation15 / 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
garrytan/gbrain
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.