cc-skill:vercel-cron-setup

Claude Code skill · anthropic · active

last 30 days

0 calls

0 of 30 days active

explain like I am new to this

what it does

This skill helps you set up scheduled tasks in Vercel that run your Next.js API routes on a timer. It provides the exact configuration format, security pattern, and advice on when to pick Vercel Cron versus other scheduling tools like Supabase or GitHub Actions.

who it is for

A developer building a Next.js app who needs to run tasks automatically on a schedule, like sending emails daily or collecting metrics every 6 hours.

when it fires

When you mention Vercel Cron, cron jobs, scheduled tasks, scheduled API routes, or say things like 'run every 6 hours' or 'daily at 2am'.

say something like

"Set up a Vercel Cron job to collect metrics every 6 hours"
"How do I schedule a task to run daily in my Next.js app?"
"Should I use Vercel Cron or GitHub Actions for this weekly cleanup job?"

what you might get back

You get a vercel.json config block with your cron schedule in UTC, a complete route handler template with security checks, and a clear recommendation on whether Vercel Cron fits your use case or if Supabase pg_cron or GitHub Actions would be better. For example: a metrics job every 6 hours gets the cron syntax '0 */6 * * *' plus a GET route with Authorization header validation.

how to know it worked

You will know it worked because you receive a ready-to-copy vercel.json block, a working API route template with the Bearer token check, and a clear answer about which tool (Vercel, Supabase, or GitHub Actions) is best for your job based on frequency and runtime.

is this skill working for me

never used

cloud runs

0 deployments

local fires

Claude Code (optional)

posts published

from drafts

attributed

$0.00

signups + revenue

Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/vercel-cron-setup/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when configuring Vercel Cron jobs, scheduled API routes, or deciding between Vercel Cron, Supabase pg_cron, and GitHub Actions for a scheduled task. Triggers on "Vercel Cron", "scheduled task", "cron job", "scheduled API route", "sched

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/vercel-cron-setup/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity

never used

2026-04-03today

cost model

unitincluded

capabilities

{
  "source": "global",
  "description": "Use this skill when configuring Vercel Cron jobs, scheduled API routes, or deciding between Vercel Cron, Supabase pg_cron, and GitHub Actions for a scheduled task. Triggers on \"Vercel Cron\", \"scheduled task\", \"cron job\", \"scheduled API route\", \"schedule\", or \"run every [time]\". Applies Jay's conventions for cron security, idempotency, and platform choice."
}

how it gets called

{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/vercel-cron-setup/SKILL.md"
}

This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.