CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/cron-job-test-author

Use when cron jobs, Kubernetes CronJobs, BullMQ repeat jobs, Sidekiq schedules or any time-based job need tests: cron expression validation, DST and leap-day edge cases, catch-up after downtime, overlapping-run locks with stale-lock recovery, and time zones.

Quality

87%

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

Overview
Quality
Evals
Security
Files

Quality

Content

75%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 well-built workflow skill: a clear step sequence, abundant executable test patterns, a real and useful one-level-deep reference file, and a closing checklist. It sits just below excellent on every dimension — trimmable primers and duplicate references, a non-executable Kubernetes downtime test, no failure-handling guidance, and heavy inline detail that could move to reference files.

Suggestions

Trim the 5-field cron-format diagram and the editorial overview paragraph, and deduplicate the References section (crontab(5) and BullMQ URLs are each listed twice) to tighten conciseness.

Replace the bash-comment Kubernetes downtime 'test' with an executable test (e.g., a kind-based CI script or a deadline-arithmetic assertion) so Step 3, an advertised capability, has runnable code like the other steps.

Add brief failure-path guidance (what to do when the DST, overlap, or timezone test fails) to satisfy the feedback-loop expectation for workflow clarity.

Consider moving the Kubernetes CronJob traps and BullMQ job-scheduler sections into separate reference files like lock-patterns.md to slim the main SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense and mostly earns its tokens, but the 5-field cron-format primer (field ranges Claude already knows), the editorializing overview ('Cron jobs are universally underspecified. Most teams ship cron expressions, never test them'), and duplicate reference listings (crontab(5) and BullMQ URLs each appear twice) are minor over-explanation that could be trimmed.

4 / 5

Actionability

Mostly executable, copy-paste-ready code (parametrized croniter validity tests, DST test with zoneinfo offset assertions, tz test, upsertJobScheduler TypeScript, fcntl lock tests in references/lock-patterns.md), but the Kubernetes missed-run 'test' is bash comments describing a manual procedure and the BullMQ tests are prose directives — Step 3 lacks executable test code.

4 / 5

Workflow Clarity

A clear 7-step sequence in 'How to use' is cross-referenced to numbered steps and capped by an explicit per-job checklist (Step 7) wired into CI, but there are no feedback loops — nothing instructs what to do when a DST or overlap test fails, which keeps it below the top anchor.

4 / 5

Progressive Disclosure

Good structure with a well-signaled, one-level-deep references/lock-patterns.md (linked four times, delivers what it promises, no nested references), but the ~320-line body inlines substantial per-technology detail (Kubernetes traps, BullMQ migration) that could be split into reference files; only one bundle file exists.

4 / 5

Total

16

/

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 names the exact scheduler technologies a user would mention, gives a comprehensive capability list, and pairs them with an explicit 'Use when' trigger clause. The only gap is a few missing natural synonyms (Quartz, Hangfire, APScheduler, 'scheduled jobs') that the body actually supports.

DimensionReasoningScore

Specificity

Lists five-plus concrete capabilities ('cron expression validation, DST and leap-day edge cases, catch-up after downtime, overlapping-run locks with stale-lock recovery, and time zones'), giving comprehensive coverage of the cron-testing domain with no gaps.

5 / 5

Completeness

Explicitly answers 'when' with concrete triggers ('Use when cron jobs, Kubernetes CronJobs, BullMQ repeat jobs, Sidekiq schedules or any time-based job need tests') and 'what' via the colon-delimited capability list; both are explicit and specific.

5 / 5

Trigger Term Quality

Natural trigger terms users would say are present ('cron jobs', 'Kubernetes CronJobs', 'BullMQ repeat jobs', 'Sidekiq schedules', 'time-based job'), but a few natural terms are missing — the body covers APScheduler, Quartz, and Hangfire, and synonyms like 'scheduled jobs/tasks' are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (testing time-scheduled jobs) with technology-specific triggers that are unlikely to fire for general test-authoring or monitoring skills; minimal conflict risk.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page