CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vercel-schedules

Vercel Schedules guidance — run a private function, route, or Vercel Queues topic on a cron cadence or once at a set time. Covers static schedules in vercel.json, dynamic per-user schedules with @vercel/schedules, handleSchedule, the vercel schedules CLI, environments, jitter, and migrating from Cron Jobs. Use when adding scheduled or recurring work, one-time reminders, or replacing `crons`.

Quality

90%

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

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

Highly actionable, well-structured content: executable code and commands for every workflow, explicit local-test validation before deploy, error-recovery guidance, and anti-pattern checklists. The only deductions are mild repetition of the path-target warning and a single-file structure that is longer than ideal for a SKILL.md overview.

DimensionReasoningScore

Conciseness

The body is dense with product-specific facts (build-output-path rule, jitter defaults, plan limits, error codes) and assumes Claude's competence, explaining nothing the model already knows. It falls short of a 5 only because the path-target anti-pattern is restated in four sections ("Choose a target", "Path targets", "Migrate from Cron Jobs", "Never Do this") and could be trimmed.

4 / 5

Actionability

Fully executable throughout: install command, complete handleSchedule handler, full vercel.json configs, a local-test/deploy CLI sequence, complete Schedules.create examples including idempotent-create error handling, and a working CRON_SECRET check — copy-paste ready and covering the common static, dynamic, and migration cases.

5 / 5

Workflow Clarity

The quickstart is a clear sequence with explicit validation ("Test locally, then deploy" via `vercel dev` and `vercel schedules invoke cleanup --local`, then a post-deploy invoke), error-recovery feedback exists (SDK error codes with actions such as waiting `retryAfter` seconds), and "Rules that break deployments" plus "Never Do this" serve as checklists. Not a 4, since checkpoints are explicit rather than implicit.

5 / 5

Progressive Disclosure

Well-organized single-file skill with clear sections, comparison tables, and clearly signaled one-level cross-skill pointers (`⤳ skill: queues`). At ~250 lines with no bundle files, material such as the CLI command reference, property/error tables, and queue-consumer example could arguably live in reference files, so it fits the 4 anchor (good structure, minor organization gaps) rather than the split-out 5.

4 / 5

Total

18

/

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: concrete, third-person, and comprehensive on the "what", with an explicit "Use when" trigger clause covering recurring work, one-time reminders, and Cron Jobs migration. The only weakness is trigger-term coverage that omits a few natural synonyms users might say.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — "run a private function, route, or Vercel Queues topic on a cron cadence or once at a set time", static vercel.json schedules, dynamic per-user schedules with @vercel/schedules, handleSchedule, the CLI, environments, jitter, and Cron Jobs migration — comprehensively covering the skill's scope with no real gaps.

5 / 5

Completeness

It clearly answers both "what" (run a private function, route, or queue topic on a cron cadence or at a set time, with the enumerated coverage list) and "when" with an explicit trigger clause: "Use when adding scheduled or recurring work, one-time reminders, or replacing `crons`" — a direct match for the 5 anchor, not merely the 4 anchor's less-specific "when".

5 / 5

Trigger Term Quality

Natural phrases like "scheduled or recurring work", "one-time reminders", "cron cadence", and "migrating from Cron Jobs" are present, but common user variations such as "scheduled job/task", "nightly", or "run every hour/day" are missing. Good coverage, a few natural terms absent — matches the 4 anchor rather than the synonym-comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The description is anchored to a clear niche via Vercel-specific triggers ("Vercel Schedules", "vercel.json", "@vercel/schedules", "vercel schedules CLI", "migrating from Cron Jobs"), giving it minimal overlap risk with generic cron or scheduler skills.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

vercel/vercel-plugin

Path

skills/vercel-schedules/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.