convex-cron-jobs

Scheduled function patterns for background tasks including interval scheduling, cron expressions, job monitoring, retry strategies, and best practices for long-running tasks

Quality

53%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/convex-cron-jobs/SKILL.md

Quality

Content

64%

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

This is a solid, actionable skill with excellent executable code examples covering the full range of Convex cron job patterns. The main weaknesses are some verbosity through repetitive examples, and missing explicit validation/verification workflows for production deployment. The content would benefit from tighter organization and explicit checkpoints for testing cron configurations.

Suggestions

Add explicit validation workflow: how to test cron jobs locally, verify they're registered in the dashboard, and confirm execution logs

Consolidate similar interval examples - the multiple interval patterns (5 min, 2 hours, 30 seconds) could be shown in a single code block with comments

Add a troubleshooting section with explicit steps: check dashboard -> verify logs -> common error patterns -> fix and redeploy cycle

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some redundancy - multiple similar examples for interval scheduling, and the cron expression reference is standard knowledge Claude likely has. The complete examples section repeats patterns already shown.	2 / 3
Actionability	Excellent executable code throughout with complete, copy-paste ready TypeScript examples. Every pattern includes working code with proper imports, type annotations, and realistic use cases.	3 / 3
Workflow Clarity	Steps are clear for individual patterns, but lacks explicit validation checkpoints. The batching section mentions avoiding timeouts but doesn't provide verification steps. No feedback loops for error recovery in the main workflows.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections, but it's a monolithic document that could benefit from splitting detailed examples into separate files. The References section points to external docs but internal content organization could be improved.	2 / 3
	Total	9 / 12 Passed

Description

42%

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 effectively lists specific capabilities around scheduled tasks and background processing, demonstrating good technical specificity. However, it critically lacks explicit trigger guidance ('Use when...') which would help Claude know when to select this skill, and could benefit from more natural user-facing keywords beyond technical jargon.

Suggestions

Add a 'Use when...' clause with trigger scenarios like 'Use when the user needs to run code on a schedule, set up recurring jobs, or implement background task processing'

Include natural language variations users might say: 'timer', 'recurring', 'periodic tasks', 'run every X minutes/hours', 'scheduled jobs'

Clarify the technology context (e.g., 'serverless functions', 'Node.js', specific platforms) to reduce overlap with other task-related skills

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'interval scheduling, cron expressions, job monitoring, retry strategies, and best practices for long-running tasks' - these are distinct, actionable capabilities.	3 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains relevant technical terms like 'cron expressions', 'scheduled function', 'background tasks', but missing common user variations like 'timer', 'recurring jobs', 'task scheduler', or 'periodic tasks' that users might naturally say.	2 / 3
Distinctiveness Conflict Risk	The combination of 'scheduled function patterns' and 'cron expressions' provides some distinctiveness, but 'background tasks' and 'long-running tasks' could overlap with general async programming or task queue skills.	2 / 3
	Total	8 / 12 Passed

Validation

68%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (605 lines); consider splitting into references/ and linking	Warning
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	11 / 16 Passed

Repository: waynesutton/convexskills
Commit: 8ef49c9

Reviewed: 5 months ago

Table of Contents

Discovery Implementation Validation

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.