render-cron-jobs

Configures and troubleshoots scheduled tasks on Render using cron job services. Use when the user needs to run something on a schedule, write a cron expression, set up a periodic job, migrate from Heroku Scheduler, choose between cron jobs and background workers, or fix a cron that isn't firing. Trigger terms: cron job, scheduled task, periodic job, cron expression, schedule, run every, timer, Heroku Scheduler migration.

Quality

93%

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

Quality

Content

87%Weight 40%Scale 1-3

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

A lean, actionable reference with a complete Blueprint example and well-structured one-level-deep references. The main gap is the absence of an explicit sequenced workflow with validation checkpoints for setup or migration.

Suggestions

Add a short numbered setup/migration workflow (e.g., choose schedule → write expression in UTC → author Blueprint → deploy → verify first run fired) with an explicit validation checkpoint such as checking the Render dashboard run history.

For destructive patterns like 'Database cleanup', include a brief validate-before-act step (dry-run or backup) so batch operations have a feedback loop.

De-duplicate the Docker image-pull behavior, which is explained in both the Configuration 'Source' bullet and the Execution Behavior section.

Dimension	Reasoning	Score
Conciseness	The body is dense with platform-specific facts (UTC evaluation, 12-hour max, no disk, single-run guarantee, prorated billing) and avoids explaining general concepts Claude already knows; the one mild redundancy (Docker image-pull behavior restated across Configuration and Execution Behavior) is minor.	3 / 3
Actionability	Provides a complete, executable `render.yaml` blueprint with `type: cron`, quoted `schedule`, `buildCommand`, `startCommand`, and linked `envVars`, plus concrete cron-expression and YAML-quoting guidance — copy-paste ready.	3 / 3
Workflow Clarity	Concepts are grouped (When to Use, Configuration, Constraints, Blueprint) but there is no sequenced multi-step workflow with validation checkpoints; destructive/batch uses like 'Database cleanup' get no validate-then-act guidance in the body, capping this at 2.	2 / 3
Progressive Disclosure	SKILL.md is a tight overview that offloads expression cheat sheets, framework commands, and Heroku migration to two real, one-level-deep reference files signaled via a References table — clear navigation and appropriate splitting.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 specific, complete, and well-scoped, with a dedicated trigger-term list and an explicit 'Use when' clause in third-person voice. It cleanly distinguishes Render cron jobs from workers and workflows.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Configures and troubleshoots', 'write a cron expression', 'set up a periodic job', 'migrate from Heroku Scheduler', 'fix a cron that isn't firing' — matching the top anchor for naming several specific actions.	3 / 3
Completeness	Clearly answers both 'what' ('Configures and troubleshoots scheduled tasks on Render using cron job services') and 'when' ('Use when the user needs to run something on a schedule...') with explicit trigger guidance, matching the top anchor.	3 / 3
Trigger Term Quality	An explicit 'Trigger terms' line covers natural phrases users would say — 'cron job, scheduled task, periodic job, cron expression, schedule, run every, timer, Heroku Scheduler migration' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (Render cron job services) with distinct triggers and an explicit contrast ('choose between cron jobs and background workers'), making overlap with sibling skills unlikely.	3 / 3
	Total	12 / 12 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: openai/plugins
Path: plugins/render/skills/render-cron-jobs/SKILL.md
Commit: 11c74d6

Reviewed: 17 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.