CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

convex-cron-jobs

Retired. Points to the skill that replaced convex-cron-jobs in builder-skills 3.0. Use when /convex-cron-jobs is invoked by name or the user asks where convex-cron-jobs went.

Quality

93%

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

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.

A model redirect stub: fully executable, extremely lean, and clearly sequenced for its single purpose of pointing users to the convex-crons replacement. The only minor gap is that the destructive cleanup instruction ("Delete this folder after you switch") relies on an implicit checkpoint instead of an explicit verification step.

DimensionReasoningScore

Conciseness

The body is 13 lean lines with zero padding and no explanations of concepts Claude already knows; every sentence contributes (redirect instruction, install command, setup URL, old-content link, cleanup note). Matches anchor 5.

5 / 5

Actionability

The install command "npx skills add convex/agent-skills --skill convex-crons" is copy-paste ready, both URLs are direct, and the instruction covers the common cases (replacement installed vs. not installed, plus a one-step alternative). Matches anchor 5; the only conditional ("if it is installed") is immediately resolved by the install path that follows.

5 / 5

Workflow Clarity

The redirect sequence is clear and unambiguous (tell the user, load the replacement if installed, otherwise install it or follow the setup URL), matching the simple-skill case. Not 5 because the trailing destructive step "Delete this folder after you switch" is gated only by an implicit condition rather than an explicit verification that the replacement works.

4 / 5

Progressive Disclosure

Per the simple-skill guideline (under 50 lines, single task, no external bundle files needed), the well-organized body with two clearly signaled one-level-deep external links scores 5. The assets/ folder contains only logos that are not needed for the redirect task.

5 / 5

Total

19

/

20

Passed

Description

90%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.

An exemplary retired-skill pointer description: it states exactly what it does and precisely when it should fire, with natural trigger phrasing and minimal conflict risk. The only soft spot is low action specificity, which is inherent to a redirect stub that has no capabilities of its own to list.

DimensionReasoningScore

Specificity

"Points to the skill that replaced convex-cron-jobs" names the domain plus one concrete action (redirecting to the replacement), matching anchor 3. It is not 4 because there is no list of several specific actions, and not 2 because the stated action is concrete rather than generic.

3 / 5

Completeness

It explicitly answers both questions: what ("Retired. Points to the skill that replaced convex-cron-jobs in builder-skills 3.0") and when ("Use when /convex-cron-jobs is invoked by name or the user asks where convex-cron-jobs went") with concrete trigger phrases. This matches anchor 5 rather than 4, where the 'when' would be less explicit.

5 / 5

Trigger Term Quality

"Use when /convex-cron-jobs is invoked by name or the user asks where convex-cron-jobs went" covers the complete natural trigger space for this stub (slash-command invocation and asking where the old skill went) with phrasing a user would actually say. It is not 4 because no natural terms are missing for its scope; adding broader terms like "cron jobs in Convex" would incorrectly pull triggers from the replacement skill.

5 / 5

Distinctiveness Conflict Risk

Triggers are pinned to the exact retired skill name, creating a clear niche with minimal conflict risk against the replacement or other skills. Not 4, because there is no meaningful overlap risk with closely related skills.

5 / 5

Total

18

/

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.

Repository

waynesutton/convexskills

Path

skills/convex-cron-jobs/SKILL.md

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.