convex-crons

Add recurring scheduled jobs (crons) to the Convex app.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/convex-crons/SKILL.md

Quality

Content

72%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 exceptionally concise and well-organized for a simple skill, but actionability suffers from the absence of an executable cron-definition example, and the workflow lacks an error-recovery feedback loop for a recurring operation.

Suggestions

Add a short executable example showing an actual cronJobs() definition (e.g., cronJobs.interval / cronJobs.cron syntax) so guidance is copy-paste ready.

Turn step 4 into a feedback loop: "If the job does not appear in the dashboard schedule, re-check the cron definition and internal function export, then redeploy."

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows; every line earns its place, matching the "lean and efficient" anchor.	5 / 5
Actionability	References concrete APIs ("cronJobs()", "internal.*") and the file path, but provides no executable cron-definition example and leaves "at the right interval" vague, fitting the "some concrete guidance but incomplete" anchor.	3 / 5
Workflow Clarity	Four sequenced steps with a verify step (#4), but no fix-and-retry feedback loop for a recurring/batch operation, triggering the workflow_clarity cap at 3.	3 / 5
Progressive Disclosure	Under 50 lines with no need for external references and well-organized sections (Workflow, Rules), qualifying for the simple-skill exception at 5.	5 / 5
	Total	16 / 20 Passed

Description

57%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 is concise and specific to a clear niche (Convex crons), but it lacks any explicit "when to use" trigger guidance, which caps completeness and limits its discoverability.

Suggestions

Add a "Use when…" clause naming concrete triggers (e.g., "Use when adding recurring jobs, scheduled tasks, or cron definitions to a Convex app").

Include a few more natural synonyms ("scheduled tasks", "recurring jobs", "timers") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	"Add recurring scheduled jobs (crons) to the Convex app" names the domain (Convex, crons) and one concrete action; not comprehensive enough for a 4, but more concrete than the generic score-2 anchor.	3 / 5
Completeness	Clearly states what the skill does, but there is no "Use when…" or equivalent trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural terms ("recurring", "scheduled jobs", "crons") but misses common synonyms a user might say, fitting the "some relevant keywords but missing variations" anchor.	3 / 5
Distinctiveness Conflict Risk	"Convex" + "crons" is a clear, narrow niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	14 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openclaw/clawhub
Path: .agents/skills/convex-crons/SKILL.md
Commit: 0180b56

Reviewed: 3 days 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.